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

HP-UX Handbook – Rev 13.00 Page 50 (of 108)
Chapter 15 Serviceguard
October 29, 2013
General Troubleshooting Commands
cmcheckconf
cmcheckconf can be used to troubleshoot your cluster just as it was used to verify the
configuration. The following example shows the commands used to verify the existing cluster
configuration on Node1 and Node2:
# cmquerycl -v -C /etc/cmcluster/verify.ascii -n Node1 –n Node2
# cmcheckconf -v -C /etc/cmcluster/verify.ascii
The cmcheckconf command checks:
 The network addresses and connections.
 The cluster lock disk connectivity.
 The validity of configuration parameters of the cluster and packages for: The
uniqueness of names; the existence and permission of scripts.
 It does not check: The correct setup of the power circuits; the correctness of the package
configuration script.
cmscancl
cmscancl is a diagnostic script that saves it’s output file in /tmp/scancl.out. It displays
information about all the nodes in a cluster in a structured report that allows you to compare such
items as IP addresses or subnets, physical volume names for disks, and other node-specific items
for all nodes in the cluster.
cmscancl needs a root-enabled .rhosts file on all nodes to scan all nodes successfully. Without it,
the command can only collect information on the local node.
The following are the types of configuration data that cmscancl displays for each node:
Table: Data Displayed by the cmscancl Command
Description
Source of Data
LAN device configuration and status
lanscan command
network status and interfaces
netstat command
file systems
mount command
LVM configuration
/etc/lvmtab file
LVM physical volume group data
/etc/lvmpvg file
link level connectivity for all links
linkloop command
binary configuration file
cmviewconf command
cmviewconf/cmviewcl –v –f line
cmviewconf (preA.11.18) and cmviewcl –v –f line (A.11.18 and newer) allows you to
examine the cluster binary file, even when the cluster is not running.