Managing Serviceguard A.11.20, March 2013

PRIMARY up 28.1 lan0
STANDBY up 32.1 lan1
UNOWNED PACKAGES
PACKAGE STATUS STATE AUTO_RUN NODE
pkg2 down halted disabled unowned
Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual
Script_Parameters:
ITEM STATUS NODE_NAME NAME
Resource up ftsys9 /example/float
Subnet up ftsys9 15.13.168.0
Generic Resource up ftsys9 sfm_disk1
Resource down ftsys10 /example/float
Subnet up ftsys10 15.13.168.0
Generic Resource up ftsys10 sfm_disk1
Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled ftsys10
Alternate up enabled ftsys9
pkg2 now has the status down, and it is shown as unowned, with package switching disabled.
Resource /example/float, which is configured as a dependency of pkg2, is down on one
node. Note that switching is enabled for both nodes, however. This means that once global
switching is re-enabled for the package, it will attempt to start up on the primary node.
NOTE: If you halt pkg2 with the cmhaltpkg -a command, and the package contains
non-Serviceguard modules that failed during the normal halt process, then the package is moved
to the partially_down status and halt_aborted state. The command exits at this point. For
more information, see “Handling Failures During Package Halt” (page 290).
Status After Moving the Package to Another Node
If we use the following command
cmrunpkg -n ftsys9 pkg2
and then run cmviewcl -v, we’ll see:
CLUSTER STATUS
example up
NODE STATUS STATE
ftsys9 up running
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 56/36.1 lan0
STANDBY up 60/6 lan1
PACKAGE STATUS STATE AUTO_RUN NODE
pkg1 up running enabled ftsys9
Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual
Script_Parameters:
ITEM STATUS MAX_RESTARTS RESTARTS NAME
Service up 0 0 service1
272 Cluster and Package Maintenance