Managing Serviceguard Eighteenth Edition, September 2010

TIP: Some commands take longer to complete in large configurations. In particular,
you can expect Serviceguard’s CPU usage to increase during cmviewcl -v as the
number of packages and services increases.
You can also specify that the output should be formatted as it was in a specific earlier
release by using the -r option to specify the release format you want, for example:
cmviewcl -r A.11.16
(See the cmviewcl(1m) manpage for the supported release formats.) The formatting
options let you choose a style: the tabulated format is designed for viewing; the line
format is designed for scripting, and is easily parsed.
See the manpage for a detailed description of other cmviewcl options.
Viewing Dependencies
The cmviewcl -v command output lists dependencies throughout the cluster. For a
specific package’s dependencies, use the -p <pkgname> option.
Viewing CFS Multi-Node Information
If you are running Veritas Cluster File System (CFS) cluster, you can use cfs commands
to see multi-node package configuration information, status, and dependencies; for
example:
cfsdgadm show_package <diskgroup>
cfsmntadm show_package <mountpoint>
getconf -p <mnpkg> | grep dependency
Types of Cluster and Package States
A cluster or its component nodes may be in several different states at different points
in time. The following sections describe many of the common conditions the cluster or
package may be in.
Cluster Status
The status of a cluster, as shown by cmviewcl, can be one of the following:
• up — At least one node has a running cluster daemon, and reconfiguration is not
taking place.
• down — No cluster daemons are running on any cluster node.
• starting — The cluster is in the process of determining its active membership.
At least one cluster daemon is running.
• unknown — The node on which the cmviewcl command is issued cannot
communicate with other nodes in the cluster.
322 Cluster and Package Maintenance