Managing HP Serviceguard A.11.20.10 for Linux, December 2012

2.2.1 Rules and Restrictions
• A single subnet cannot be configured on different network interfaces (NICs) on the same node.
• In the case of subnets that can be used for communication between cluster nodes, the same
network interface must not be used to route more than one subnet configured on the same
node.
• For IPv4 subnets, Serviceguard does not support different subnets on the same LAN interface.
◦ For IPv6, Serviceguard supports up to two subnets per LAN interface (site-local and global).
• Serviceguard does support different subnets on the same bridged network (this applies at both
the node and the cluster level).
• Serviceguard does not support using networking tools such as ifconfig to add IP addresses
to network interfaces that are configured into the Serviceguard cluster, unless those IP addresses
themselves will be immediately configured into the cluster as stationary IP addresses.
CAUTION: If you configure any address other than a stationary IP address on a Serviceguard
network interface, it could collide with a relocatable package IP address assigned by
Serviceguard. See “Stationary and Relocatable IP Addresses and Monitored Subnets”
(page 59).
◦ Similarly, Serviceguard does not support using networking tools to move or reconfigure
any IP addresses configured into the cluster.
Doing so leads to unpredictable results because the Serviceguard view of the configuration
is different from the reality.
NOTE: If you will be using a cross-subnet configuration, see also the Restrictions (page 28) that
apply specifically to such configurations.
2.2.2 Redundant Ethernet Configuration
The use of redundant network components is shown in Figure 4, which is an Ethernet configuration.
26 Understanding Hardware Configurations for Serviceguard for Linux