HP-UX HB v13.00 Ch-15 - Serviceguard

HP-UX Handbook – Rev 13.00 Page 60 (of 108)
Chapter 15 Serviceguard
October 29, 2013
 Cluster Lock initialization
Serviceguard Command hangs
Serviceguard uses network messages to other nodes when SG commands involve other nodes.
Many Serviceguard commands, including cmviewcl, depend on name resolution services to
match the IP of the SG network message to a valid nodename. Nsswitch.conf should use
/etc/nsswitch.files as a basis, and point hosts: to files (/etc/hosts) before DNS, to avoid a
possible inability to contact the DNS server, which may produce a command hang. All
permanent IPs on each node must be listed in /etc/hosts and must be aliased to the nodename
(See Managing Serviceguard: Configuring Name Resolution).
Use nslookup to learn how nodenames are resolved. Example:
# nslookup Node1
Name Server: server1.cup.hp.com <- DNS is searched first! 
Address: 15.13.168.63
Name: Node1.cup.hp.com
Address: 15.13.172.229
What you should see:
# nslookup d7
Using /etc/hosts on: rxg16u09 <-- Good!
looking up FILES <-- Good!
Name: rxg16u07.aqn.gsc.mvlabs.corp.hp.com
Address: 10.226.72.13
Aliases: rxg16u07, d7, dump7
If the output of either command does not include the correct IP address of the node, then check
your name resolution services further.
For common Serviceguard Command Problems please refer also to the Section: Common Issues
Cluster Re-formations
Cluster re-formations is logged in syslog.log. Examples:
Apr 24 14:07:11 etldts01 cmcld[4966]: 3 nodes have formed a new cluster, sequence #1
Feb 12 23:49:41 tcenh254 cmcld[2436]: 2 nodes have formed a new cluster, sequence #5
Sep 24 18:23:56 sdhn5452 cmcld[4122]: 1 nodes have formed a new cluster, sequence #22
Re-formation may occur for the following reasons:
 A node has left or joined the cluster. Serviceguard operates a periodic heartbeat between
current members of the cluster, to insure all packages have owners. When nodes leave or
join the cluster, heartbeat targeting must be updated, by way of a cluster reformation.