HP-UX HB v13.00 Ch-15 - Serviceguard

HP-UX Handbook – Rev 13.00 Page 31 (of 108)

Chapter 15 Serviceguard

October 29, 2013

The following section is declared for each node:

NODE_NAME <hostname>

NETWORK_INTERFACE lan3

HEARTBEAT_IP <IP>

NETWORK_INTERFACE lan1

Optional parameters:

FIRST_CLUSTER_LOCK_VG

CLUSTER_LOCK_LUN /dev/dsk/c1t2d3s1 (identified per node)

QS_HOST <qs_host>

QS_ADDR <qs_addr>

QS_POLLING_INTERVAL 120000000 <- default value if used

QS_TIMEOUT_EXTENSION 2000000 <- default value if used

The following 2 parameters are specified in each node section:

CAPACITY_NAME specifies a name for the capacity.

CAPACITY_VALUE specifies a value for the CAPACITY_NAME that precedes

Multiple declarations of the following 3 parameters is legal:

SUBNET <IP>

IP_MONITOR ON

POLLING_TARGET <IP> <- default IP is gateway

WEIGHT parameters are associated with packages, and are partnered with node CAPACITY

parameters. A maximum of 4 weights may be defined.

WEIGHT_NAME -

WEIGHT_DEFAULT - specifies a default weight for this WEIGHT_NAME.

USER_NAME <ANY_USER | <actual_user> (never root)

USER_HOST ANY_SERVICEGUARD_NODE | CLUSTER_MEMBER_NODE | <hostname>

USER_ROLE <FULL_ADMIN | MONITOR | PACKAGE_ADMIN >

Any number of the VOLUME_GROUP parameter may be declared (up to kernel limits)

At a minimum, customize the CLUSTER_NAME parameter in the file.

Validating a Cluster Configuration - cmcheckconf

NOTE: cmapplyconf performs cmcheckconf. If you plan on distributing the cluster binary file

now, skip cmcheckconf and run cmapplyconf.

Use the cmcheckconf command to check a high availability cluster configuration and/or package

configuration files and determine whether cmapplyconf will be successful. This validates the

cluster configuration as specified by the cluster ASCII file and/or the package configuration files

specified by each package ASCII file in the command and identifies whether the cmapplyconf

can be performed (if the cluster is currently running).