Using Serviceguard Extension for RAC Version A.11.20 - (August 2011)

Alternate up enabled ftsys9 (current)
NODE STATUS STATE
ftsys10 up running
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 28.1 lan0
STANDBY up 32.1 lan1
Now pkg2 is running on node ftsys9. Note that it is still disabled from switching.
Status After Package Switching is Enabled
The following command changes package status back to Package Switching Enabled:
# cmmodpkg -e pkg2
The output of the cmviewcl command is now as follows:
CLUSTER STATUS
example up
NODE STATUS STATE
ftsys9 up running
PACKAGE STATUS STATE AUTO_RUN NODE
pkg1 up running enabled ftsys9
pkg2 up running enabled ftsys9
NODE STATUS STATE
ftsys10 up running
Both packages are now running on ftsys9 and pkg2 is enabled for switching. Ftsys10 is
running the daemon and no packages are running on ftsys10.
Status After Halting a Node
After halting ftsys10, with the following command:
# cmhaltnode ftsys10
the output of cmviewcl is as follows on ftsys9:
CLUSTER STATUS
example up
NODE STATUS STATE
ftsys9 up running
PACKAGE STATUS STATE AUTO_RUN NODE
pkg1 up running enabled ftsys9
pkg2 up running enabled ftsys9
NODE STATUS STATE
ftsys10 down halted
This output is seen on both ftsys9 and ftsys10.
Viewing Data on Unowned Packages
The following example shows packages that are currently unowned—not running on any configured
node. Information on monitored resources is provided for each node. This information allows you
to identify the cause of a failure and decide where to start the package up again.
UNOWNED_PACKAGES
PACKAGE STATUS STATE AUTO_RUN NODE
PKG3 down halted enabled unowned
Reviewing Cluster and Package States with the cmviewcl Command 121