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

• Each heartbeat subnet on each node must be physically routed separately to the
heartbeat subnet on another node; that is, each heartbeat path must be physically
separate:
— The heartbeats must be statically routed; static route entries must be configured
on each node to route the heartbeats through different paths.
— Failure of a single router must not affect both heartbeats at the same time.
• Deploying applications in this environment requires careful consideration; see
“Implications for Application Deployment” in Chapter 4 of the eighth edition of
Managing Serviceguard for Linux.
• cmrunnode will fail if the “hostname LAN” is down on the node in question.
(“Hostname LAN” refers to the public LAN on which the IP address that the node’s
hostname resolves to is configured).
• If a monitored_subnet is configured for PARTIAL monitored_subnet_access in a
package’s configuration file, it must be configured on at least one of the nodes on
the node_name list for that package. Conversely, if all of the subnets that are being
monitored for this package are configured for PARTIAL access, each node on the
node_name list must have at least one of these subnets configured.
— As in other configurations, a package will not start on a node unless the subnets
configured on that node, and specified in the package configuration file as
monitored subnets, are up.
• You cannot use Serviceguard Manager to configure a cross-subnet cluster or
package.
For More Information
For more information on the details of configuring the cluster and packages in a
cross-subnet context, see the following sections in the eighth edition of Managing
Serviceguard for Linux, at http://docs.hp.com -> High Availability ->
Serviceguard: “Obtaining Cross-Subnet Information” in Chapter 5, “About
Cross-Subnet Failover” in Chapter 4, and (for legacy packages only) “Configuring
Cross-Subnet Failover” in Chapter 7.
What’s in this Release 31