HP Serviceguard for Linux Version A.11.19 Release Notes, July 2009

IMPORTANT: If you use DM-MPIO for the lock LUN on one node in a cluster, it must
be used on all nodes. The device names should be in the form
/dev/mapper/mpath<x>p<y>.
<x> can be different on different nodes, but <y> must be the same; for example:
• On node1: /dev/mapper/mpath0p1
• On node2: /dev/mapper/mpath1p1
For the latest information on supported configurations, see the Serviceguard for Linux
Certification Matrix at the address given under “Documents for This Version ” (page 36).
About Cross-Subnet Configurations
As of Serviceguard A.11.18, 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 of 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
ninth 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.
Features Introduced Before A.11.19 29