Managing Serviceguard 14th Edition, June 2007

Building an HA Cluster Configuration
Preparing Your Systems
Chapter 5202
Configuring IP Address Resolution
Serviceguard uses the name resolution services built in to HP-UX. HP
recommends that you define name resolutions in each node’s /etc/hosts
file first, rather than rely solely on DNS or NIS services.
For example, consider a two node cluster (gryf and sly) with two private
subnets and a public subnet. These nodes will be granting permission to
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
NOTE Serviceguard recognizes only the hostname (the first element) in a fully
qualified domain name (a name with four elements separated by
periods, like those in the example above). This means, for example, that
gryf.uksr.hp.com and gryf.cup.hp.com cannot be nodes in the same
cluster, as they would both be treated as the same host gryf.
If applications require the use of hostname aliases, the Serviceguard
hostname must be one of the aliases. For example:
15.145.162.131 gryf.uksr.hp.com gryf node1
10.8.0.131 gryf2.uksr.hp.com gryf
10.8.1.131 gryf3.uksr.hp.com gryf
15.145.162.132 sly.uksr.hp.com sly node2
10.8.0.132 sly2.uksr.hp.com sly
10.8.1.132 sly3.uksr.hp.com sly