Managing Serviceguard 13th Edition, February 2007

Building an HA Cluster Configuration
Preparing Your Systems
Chapter 5190
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
NOTE Configure the name service switch to consult the /etc/hosts file before
other services such as DNS, NIS, or LDAP. See “Defining Name
Resolution Services” on page 197 for instructions.
Username Validation
Serviceguard relies on the identd daemon (usually started by inetd
from /etc/inetd.conf) to verify the username of the incoming network
connection. If the Serviceguard daemon is unable to connect to the
identd daemon, permission will be denied.
For Serviceguard to consider a remote user as the root user on that
remote node, identd must return the username “root”. Because identd
returns the username for the first match on UID 0, this means the entry
for the root user in /etc/passwd on each node must come before any
other entry with a UID of 0.