Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Building an HA Cluster Configuration
Preparing Your Systems
Chapter 5146
Configuring Name Resolution
Serviceguard uses the name resolution services built into Linux.
Serviceguard nodes can communicate over any of the cluster’s shared
networks, so the network resolution service you are using (such as DNS,
NIS, or LDAP) must be able to resolve each of their primary addresses on
each of those networks to the primary hostname of the node in question.
In addition, HP recommends that you define name resolution in each
node’s /etc/hosts file, rather than rely solely on a service such as DNS.
Configure the name service switch to consult the /etc/hosts file before
other services. See “Safeguarding against Loss of Name Resolution
Services” on page 147 for instructions.
NOTE If you are using private IP addresses for communication within the
cluster, and these addresses are not known to DNS (or the name
resolution service you use) these addresses must be listed in
/etc/hosts.
For example, consider a two node cluster (gryf and sly) with two private
subnets and a public subnet. These nodes will be granting access by a
non-cluster node (bit) which does not share the private subnets. The
/etc/hosts file on both cluster nodes should contain:
15.145.162.131 gryf.uksr.hp.com gryf
10.8.0.131 gryf.uksr.hp.com gryf
10.8.1.131 gryf.uksr.hp.com gryf
15.145.162.132 sly.uksr.hp.com sly
10.8.0.132 sly.uksr.hp.com sly
10.8.1.132 sly.uksr.hp.com sly
15.145.162.150 bit.uksr.hp.com bit