Cluster Monitor Reference

The HA Cluster Monitor is useful in environments not running HP OpenView ClusterView. The HA Cluster Monitor reports information on the status of the cluster to which the local node belongs.

The resources monitored are:

/cluster/status/clustername, a summary of the state of all nodes in the cluster clustername
/cluster/localNode/status/clustername, the status of a given node in a cluster. A node can only be a member of one cluster
/cluster/package/package_status/packageName, the status of a ServiceGuard package in a cluster
/cluster/package/service_status/packageName/serviceName, the status of a ServiceGuard service in a cluster package

The HA Cluster Monitor is part of the MIB Monitors package. Table 6-1 “HA Cluster Monitor Names and Resources” lists the HA Cluster Monitors.

Table 6-1 HA Cluster Monitor Names and Resources

Monitor	Resource Type	Resource
clustermond	Cluster	`/cluster/status/<clusterName>`
	Local Node	`/cluster/localNode/status/ <clusterName>`
pkgmond	Package	`/cluster/package/ package_status/<packageName>`
svcmond	Service	`/cluster/package/ service_status/<packageName>/<serviceName>`

To fix any problems detected by the cluster monitor, refer to Managing MC/ServiceGuard (HP Part Number B3936-90026).

Figure 6-1 “Cluster Monitor Resource Class Hierarchy ” shows the cluster monitor class hierarchy.

Figure 6-1 Cluster Monitor Resource Class Hierarchy

Items in boxes are resource instances that can be monitored. Variables in italics change depending on the names of the clusters and packages on the system.

Cluster Status

The cluster status is the status of the MC/ServiceGuard cluster to which this node belongs.The status is from the perspective of the node for which the request was created.

The hp-mcCluster MIB variable, hpmcClusterState, provides the cluster status information to the monitor.

The cmviewcl -v command displays detailed information about the current status of the cluster and packages on the cluster.

Table 6-2 Interpreting Cluster Status

Resource Name: /cluster/status/`clusterName`
Condition	Value	Interpretation
`UP`	1	The node can access the cluster.
`UNKNOWN`	2	The node may be separated from other active cluster elements (for example the heartbeat LAN) and has insufficient information to tell if the cluster is accessible.
`DOWN`	3	The node cannot access the cluster.

You might request to be notified when the cluster is not up. You could then verify whether the cluster was shut down intentionally.

The minimum polling interval for cluster status is 30 seconds. You may want a longer interval, especially if system performance is affected.

Node Status

The node status is the current status of a node relative to a particular cluster.

The hp-mcCluster MIB variable, hpmcNodeStatus, provides the node status information to the monitor.

The cmviewcl -v command displays detailed information about the current status of the cluster and packages on the cluster.

Table 6-3 Interpreting Node Status

Resource Name: /cluster/localNode/status/`clusterName`
Condition	Value	Interpretation
`RUNNING`	1	Node is accessible and operating normally.
`INITIALIZING`	2	Node's cluster daemon has started, but is not ready to communicate with other nodes' daemons.
`RECONFIGURING`	3	Node is running protocols to make sure all other nodes agree to the new membership in the cluster.
`INVALID`	4	The cluster status may be DOWN.
`HALTED`	5	Node has been removed from the cluster, with the cmhaltnode command, for example.
`FAILED`	6	Node is no longer a member of an active cluster.

You might want to create a request that notifies you when the local node is not running. You can then verify whether the node or MC/ServiceGuard was stopped intentionally.

The minimum polling interval for node status is 30 seconds. You may want a longer interval, especially if system performance is affected.

Package Status

The package status is the status of each package running on this node.

The hp-MCCluster MIB variable, hpmcSGPkgStatus, provides the package status information to the monitor.

The cmviewcl -v command displays detailed information about the current status of the cluster and packages on the cluster.

Table 6-4 Interpreting Package Status

Resource Name: /cluster/package/package_status/`packageName`
Condition	Value	Interpretation
`UP`	1	The package is running on the local node.
`UNKNOWN`	2	The package is not running on the local node, but may be running on another node in the cluster.
`DOWN`	3	The package is not running on any node in the cluster.

You might want to be notified when the value of any of the packages changes to UNKNOWN or DOWN, so you can verify that MC/ServiceGuard successfully migrated the package to another system.

You may see many packages with UNKNOWN status. This is because only the node running a package has complete status for a package. Other nodes often have inactive volume groups that make it impossible to have complete knowledge of package status. If a package is running on another node in the cluster, the current node may not have complete status on that package, and reports the condition UNKNOWN.

The minimum polling interval for package status is 30 seconds. You may want a longer interval, especially if system performance is affected.

Service Status

A service is part of a package. The service status is the status of each service running on this node.

The hp-MCCluster MIB variable, hpmcSGPkgSvcStatus, provides the service status information to the monitor.

The cmviewcl -v command displays detailed information about the current status of the cluster and services on the cluster.

Table 6-5 Interpreting Service Status

Resource Name: /cluster/package/service_status/`packageName/serviceName`
Condition	Value	Interpretation
`UP`	1	The service is running on the local node.
`UNKNOWN`	2	The service is not running on the local node, but may be running on another node in the cluster.
`DOWN`	3	The service is not running on any node in the cluster.

You might want to be notified when the value of any of the services changes to UNKNOWN or DOWN, so you can verify that MC/ServiceGuard successfully migrated the package and its services to another system.

You may see many services with UNKNOWN status. This is because only the node running a package with a service has complete status for a service. Other nodes often have inactive volume groups that make it impossible to have complete knowledge of service status. If a service is running on another node in the cluster, the current node may not have complete status on that service, and reports the condition UNKNOWN.

The minimum polling interval for service status is 30 seconds. You may want a longer interval, especially if system performance is affected.

Cluster Monitor Reference

Technical documentation

» Table of Contents

» Glossary

» Index

Cluster Status

Node Status

Package Status

Service Status