Managing Serviceguard Eighteenth Edition, September 2010

NODE STATUS STATE
ftsys10 up running
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 28.1 lan0
STANDBY up 32.1 lan1
PACKAGE STATUS STATE AUTO_RUN NODE
pkg2 up running enabled ftsys10
Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual
Script_Parameters:
ITEM STATUS MAX_RESTARTS RESTARTS NAME
Service up 0 0 service2
Subnet up 0 0 15.13.168.0
Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled ftsys10 (current)
Alternate up enabled ftsys9
NOTE: The Script_Parameters section of the PACKAGE output of cmviewcl
shows the Subnet status only for the node that the package is running on. In a
cross-subnet configuration, in which the package may be able to fail over to a node on
another subnet, that other subnet is not shown; see “Cross-Subnet Configurations”
(page 41).
Quorum Server Status
If the cluster is using a Quorum Server for tie-breaking services, the display shows the
server name, state and status following the entry for each node, as in the following
excerpt from the output of cmviewcl -v:
CLUSTER STATUS
example up
NODE STATUS STATE
ftsys9 up running
Quorum Server Status:
NAME STATUS STATE
lp-qs up running
...
NODE STATUS STATE
ftsys10 up running
Reviewing Cluster and Package Status 327