Managing Serviceguard Eighteenth Edition, September 2010

NOTE: If you plan to use cmpreparecl (1m) (or cmpdeploycl (1m), which calls
cmpreparecl), the /etc/hosts and /etc/nsswitch.conf configuration described
in this subsection will be done automatically, but you should still read the entire
subsection and make sure you understand the issues.
In particular, you still need to make sure that aliases are properly represented in /etc/
hosts, as described below.
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” (page 220) 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 requirements and restrictions that apply to IPv6–only clusters and mixed-mode
clusters, see “Rules and Restrictions for IPv6-Only Mode” (page 140) and “Rules and
Restrictions for Mixed Mode” (page 142), respectively, and the latest version of the
Serviceguard release notes.
Keep the following rules in mind when creating entries in a Serviceguard node's/etc/
hosts:
• NODE_NAME in the cluster configuration file must be identical to the hostname
which is normally the first element of a fully qualified domain name (a name
with four elements separated by periods). This hostname is what is normally
returned by the HP-UX hostname (1) command.
For example, if the node's fully-qualified domain name is gryf.uksr.hp.com,
the NODE_NAME must be gryf. For more information, see the NODE_NAME
entry under “Cluster Configuration Parameters ” (page 143).
NOTE: Since Serviceguard recognizes only the hostname, gryf.uksr.hp.com
and gryf.cup.hp.com cannot be nodes in the same cluster, as Serviceguard
would see them as the same host gryf.
• Each stationary and heartbeat IP address must map to an entry in which the
NODE_NAME is either:
— the official hostname, as defined by hosts (4), for example
Preparing Your Systems 219