Managing Serviceguard Seventeenth Edition, First Reprint December 2009

• linkloop verifies the communication between LAN cards at MAC address levels.
For example, if you enter
linkloop -i4 0x08000993AB72
you should see displayed the following message:
Link Connectivity to LAN station: 0x08000993AB72 OK
• cmscancl can be used to verify that primary and standby LANs are on the same
bridged net.
• cmviewcl -v shows the status of primary and standby LANs.
Use these commands on all nodes.
Solving Problems
Problems with Serviceguard may be of several types. The following is a list of common
categories of problem:
• Serviceguard command hangs
• Networking and security configuration errors
• Cluster re-formations
• System administration errors
• Package control script hangs
• Problems with VxVM disk groups
• Package movement errors
• Node and network failures
• Quorum Server problems
The first two categories of problems occur with the incorrect configuration of
Serviceguard. The last category contains “normal” failures to which Serviceguard is
designed to react and ensure the availability of your applications.
Serviceguard Command Hangs
If you are having trouble starting Serviceguard, it is possible that someone has
accidentally deleted, modified, or placed files in, the directory that is reserved for
Serviceguard use only: $SGCONF/rc, by default /etc/cmcluster/rc on an HP-UX
system.
Networking and Security Configuration Errors
Many Serviceguard commands, including cmviewcl, depend on name resolution
services to look up the addresses of cluster nodes. When name services are not available
(for example, if a name server is down), Serviceguard commands may hang, or may
return a network-related error message. If this happens, use the nslookup command
on each cluster node to see whether name resolution is correct. For example:
nslookup ftsys9
Solving Problems 379