HP Serviceguard Extension for RAC (SGeRAC) Examples of Cluster and Package States, Network Status

Network Status

The network interfaces have only status, as follows:

•Up.

•Down.

•Unknown—Whether the interface is up or down cannot be determined. This can happen when the cluster is down. A standby interface has this status.

NOTE: Serial Line Status has been de-supported as of Serviceguard A.11.18.

Failover and Failback Policies

Packages can be configured with one of two values for the FAILOVER_POLICY parameter:

•CONFIGURED_NODE—the package fails over to the next node in the node list in the package configuration file.

•MIN_PACKAGE_NODE—the package fails over to the node in the cluster with the fewest running packages on it.

Packages can also be configured with one of two values for the FAILBACK_POLICY parameter:

•AUTOMATIC—a package following a failover returns to its primary node when the primary node becomes available again.

•MANUAL—a package following a failover must be moved back to its original node by a system administrator.

Failover and failback policies are displayed in the output of the cmviewcl -vcommand.

Examples of Cluster and Package States

The following sample output from the cmviewcl -vcommand shows status for the cluster in the sample configuration.

Normal Running Status

Everything is running normally—both nodes in a two-node cluster are running, and each Oracle RAC instance package is running as well. The only packages running are Oracle RAC instance packages.

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
ops_pkg1	up	running	disabled	ftsys9

Policy_Parameters:

POLICY_NAME CONFIGURED_VALUE

Start configured_node

Failback manual

Node_Switching_Parameters:
NODE_TYPE	STATUS	SWITCHING	NAME
Primary	up	enabled	ftsys9	(current)
NODE	STATUS	STATE

118 Maintenance