Managing Serviceguard A.11.20, March 2013

NOTE: HP recommends you use Serviceguard Manager as a convenient way to observe the
status of a cluster and the properties of cluster objects: from the System Management Homepage
(SMH), select the cluster you need to troubleshoot.
Reviewing Package IP Addresses
The netstat -in command can be used to examine the LAN configuration. The command, if
executed on ftsys9 after ftsys10 has been halted, shows that the package IP addresses are
assigned to lan0 on ftsys9 along with the primary LANIP address.
ftsys9>netstat -in
IPv4:
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
ni0# 0 none none 0 0 0 0 0
ni1* 0 none none 0 0 0 0 0
lo0 4608 127 127.0.0.1 10114 0 10 0 0
lan0 1500 15.13.168 15.13.171.14 959269 0 33069 0 0
lan0:1 1500 15.13.168 15.13.171.23 959269 0 33069 0 0
lan0:2 1500 15.13.168 15.13.171.20 959269 0 33069 0 0
lan1* 1500 none none 418623 0 55822 0 0
IPv6:
Name Mtu Address/Prefix Ipkts Opkts
lan1* 1500 none 0 0
lo0 4136 ::1/128 10690 10690
Reviewing the System Log File
Messages from the Cluster Manager and Package Manager are written to the system log file. The
default location of the log file is /var/adm/syslog/syslog.log. Also, package-related
messages are logged into the package log file. The package log file is located in the package
directory, by default. You can use a text editor, such as vi, or the more command to view the log
file for historical information on your cluster.
It is always a good idea to review the syslog.log file on each of the nodes in the cluster when
troubleshooting cluster problems.
This log provides information on the following:
• Commands executed and their outcome.
• Major cluster events which may, or may not, be errors.
• Cluster status information.
NOTE: Many other products running on HP-UX in addition to Serviceguard use the syslog.log
file to save messages. The HP-UX System Administrator’s Guide provides additional information
on using the system log.
Sample System Log Entries
The following entries from the file /var/adm/syslog/syslog.log show a package that failed
to run due to a problem in the pkg5_run script. You would look at the pkg5_run.log for details.
Dec 14 14:33:48 star04 cmcld[2048]: Starting cluster management protocols.
Dec 14 14:33:48 star04 cmcld[2048]: Attempting to form a new cluster
Dec 14 14:33:53 star04 cmcld[2048]: 3 nodes have formed a new cluster
Dec 14 14:33:53 star04 cmcld[2048]: The new active cluster membership is:
star04(id=1) , star05(id=2), star06(id=3)
Dec 14 17:33:53 star04 cmlvmd[2049]: Clvmd initialized successfully.
Dec 14 14:34:44 star04 CM-CMD[2054]: cmrunpkg -v pkg5
Dec 14 14:34:44 star04 cmcld[2048]: Request from node star04 to start
package pkg5 on node star04.
Dec 14 14:34:44 star04 cmcld[2048]: Executing '/etc/cmcluster/pkg5/pkg5_run
start' for package pkg5.
Dec 14 14:34:45 star04 LVM[2066]: vgchange -a n /dev/vg02
Dec 14 14:34:45 star04 cmcld[2048]: Package pkg5 run script exited with
336 Troubleshooting Your Cluster