HP Serviceguard Version A.11.19 Release Notes, July 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.
• Because Veritas Cluster File System from Symantec (CFS) requires link-level traffic
communication (LLT) among the nodes, Serviceguard cannot be configured in
cross-subnet configurations with CFS alone.
But CFS is supported in specific cross-subnet configurations with Serviceguard
and HP add-on products such as Serviceguard Extension for Oracle RAC
(SGeRAC); see the documentation listed below.
• Each package subnet must be configured with a standby interface on the local
bridged net. The standby interface can be shared between subnets.
• Deploying applications in this environment requires careful consideration; see
“Implications for Application Deployment” in Chapter 4 of the latest edition of
Managing Serviceguard.
• 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.
• Cross-subnet configurations are not supported in IPv6-only or mixed mode clusters
(see “New Support for IPv6” (page 24) for information about these modes).
• Cross-subnet configurations are not supported by the HA NFS Toolkit or SGeSAP
Toolkit.
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 latest edition of Managing
Serviceguard, at the address given under “Documents for This Version ” (page 47):
“Obtaining Cross-Subnet Information” in Chapter 5, “About Cross-Subnet Failover”
38 Serviceguard Version A.11.19 Release Notes