HP Serviceguard for Linux Version A.11.18 Release Notes, 2nd Edition, March 2009

• You can use cmmakepkg -l (letter “l”) to see a list of all available modules,
including non-Serviceguard modules such as those supplied in the HP Toolkits.
• You can use cmgetconf -P write out the configuration information for all
packages in the cluster to a specified location; for example:
mkdir /tmp/pkgconfig
cmgetconf -c clusterA -P /tmp/pkgconfig
About Cross-Subnet Configurations
As of Serviceguard A.11.18, with the patches listed on (page 11), Serviceguard allows
you to configure multiple subnets, joined by a router, both for the cluster heartbeat
and for data, with some nodes using one subnet and some another.
A cross-subnet configuration allows:
• Automatic package failover from a node on one subnet to a node on another
• A cluster heartbeat that spans subnets.
Configuration Tasks
Cluster and package configuration tasks are affected as follows:
• You must use the -w full option to cmquerycl to discover actual or potential
nodes and subnets across routers.
• For modular packages, you must configure two new parameters in the package
configuration file to allow packages to fail over across subnets:
— ip_subnet_node - to indicate which nodes the subnet is configured on
— monitored_subnet_access - to indicate whether the subnet is configured on all
nodes (FULL) or only some (PARTIAL)
(For legacy packages, see “Configuring Cross-Subnet Failover” in Chapter 7 of the
eighth edition of Managing Serviceguard for Linux.)
• You should not use the wildcard (*) for node_name in the package configuration
file, as this could allow the package to fail over across subnets when a node on the
same subnet is eligible. Instead, list the nodes in order of preference.
Restrictions
The following restrictions apply:
• All nodes in the cluster must belong to the same network domain (that is, the
domain portion of the fully-qualified domain name must be the same).
• The nodes must be fully connected at the IP level.
• A minimum of two heartbeat paths must be configured for each cluster node.
• There must be less than 200 milliseconds of latency in the heartbeat network.
30 Serviceguard for Linux Version A.11.18 Release Notes