Managing HP Serviceguard A.11.20.20 for Linux, March 2014

7.1.11.7 Viewing Information about Unowned Packages
The following example shows packages that are currently unowned, that is, not running on any
configured node.
UNOWNED_PACKAGES
PACKAGE STATUS STATE AUTO_RUN NODE
PKG3 down halted enabled unowned
Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover min_package_node
Failback automatic
Script_Parameters:
ITEM STATUS NODE_NAME NAME
Subnet up manx 192.8.15.0
Generic Resource unknown manx sfm_disk
Subnet up burmese 192.8.15.0
Generic Resource unknown burmese sfm_disk
Subnet up tabby 192.8.15.0
Generic Resource unknown tabby sfm_disk
Subnet up persian 192.8.15.0
Generic Resource unknown persian sfm_disk
Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled manx
Alternate up enabled burmese
Alternate up enabled tabby
Alternate up enabled persian
7.1.12 Checking the Cluster Configuration and Components
Serviceguard provides tools that allow you to verify the cluster configuration and the state of its
components. In earlier releases, thecmcheckconf command was used to verify the cluster or
package configuration. For more information, see “Verifying the Cluster Configuration ” (page 163)
and “Verifying the Package Configuration” (page 238).
Starting Serviceguard A.11.20.20, the cmcheckconf command can be used at any time with
–v or –v 2 options to verify the state of the cluster and package components that are already
applied. For more information, see “Verifying Cluster and Package Components” (page 208) and
the cmcheckconf (1m) manpage.
7.1 Reviewing Cluster and Package Status 207