Managing HP Serviceguard A.11.20.10 for Linux, December 2012

7 Cluster and Package Maintenance
This chapter describes the cmviewcl command, then shows how to start and halt a cluster or an
individual node, how to perform permanent reconfiguration, and how to start, halt, move, and
modify packages during routine maintenance of the cluster. Topics are as follows:
• Reviewing Cluster and Package Status
• Managing the Cluster and Nodes (page 203)
• Managing Packages and Services (page 209)
• Reconfiguring a Cluster (page 216)
• Configuring a Legacy Package (page 225)
• Reconfiguring a Package (page 232)
• Responding to Cluster Events (page 238)
• Single-Node Operation (page 239)
• Removing Serviceguard from a System (page 239)
7.1 Reviewing Cluster and Package Status
You can check the status using Serviceguard Manager, or from a cluster node’s command line.
7.1.1 Reviewing Cluster and Package Status with the cmviewcl Command
Information about cluster status is stored in the status database, which is maintained on each
individual node in the cluster. You can display information contained in this database by means
of the cmviewcl command:
cmviewcl -v
You can use the cmviewcl command without root access; in clusters running Serviceguard version
A.11.16 or later, grant access by assigning the Monitor role to the users in question. In earlier
versions, allow access by adding <nodename> <nonrootuser> to the cmclnodelist file.
cmviewcl -v displays information about all the nodes and packages in a running cluster, together
with the settings of parameters that determine failover behavior.
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.
See the manpage for a detailed description of other cmviewcl options.
7.1.2 Viewing Package Dependencies
The cmviewcl -v command output lists dependencies throughout the cluster. For a specific
package’s dependencies, use the -p<pkgname> option.
7.1.3 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.
7.1 Reviewing Cluster and Package Status 193