Managing Serviceguard Eighteenth Edition, September 2010

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.
410 Troubleshooting Your Cluster