Managing Serviceguard Eighteenth Edition, September 2010

addresses of all the cluster nodes. If the name service is not available, the command
could hang or return an unexpected networking error message.
NOTE: If such a hang or error occurs, Serviceguard and all protected applications
will continue working even though the command you issued does not. That is, only
the Serviceguard configuration commands (and corresponding Serviceguard Manager
functions) are affected, not the cluster daemon or package services.
The procedure that follows shows how to create a robust name-resolution configuration
that will allow cluster nodes to continue communicating with one another if a name
service fails. If a standby LAN is configured, this approach also allows the cluster to
continue to function fully (including commands such as cmrunnode and cmruncl)
after the primary LAN has failed.
NOTE: If a NIC fails, the affected node will be able to fail over to a standby LAN so
long as the node is running in the cluster. But if a NIC that is used by Serviceguard
fails when the affected node is not running in the cluster, Serviceguard will not be able
to restart the node. (For instructions on replacing a failed NIC, see “Replacing LAN or
Fibre Channel Cards” (page 407).)
NOTE: If you plan to use cmpreparecl (1m) (orcmpdeploycl (1m), which calls
cmpreparecl), the /etc/hosts and /etc/nsswitch.confconfiguration described
the procedure that follows will be done automatically, but you should still read the
entire subsection and make sure you understand the issues.
1. Edit the /etc/hosts file on all nodes in the cluster. Add name resolution for all
heartbeat IP addresses, and other IP addresses from all the cluster nodes; see
“Configuring Name Resolution” (page 218) for discussion and examples.
NOTE: For each cluster node, the public-network IP address must be the first
address listed. This enables other applications to talk to other nodes on public
networks.
2. If you are using DNS, make sure your name servers are configured in /etc/
resolv.conf, for example:
domain cup.hp.com
search cup.hp.com hp.com
nameserver 15.243.128.51
nameserver 15.243.160.51
Preparing Your Systems 221