Managing HP Serviceguard A.11.20.10 for Linux, December 2012

You cannot change the designation of an existing interface from HEARTBEAT_IP to
STATIONARY_IP, or vice versa, without also making the same change to all peer network
interfaces on the same subnet on all other nodes in the cluster.
Similarly, you cannot change an interface from IPv4 to IPv6 without also making the same
change to all peer network interfaces on the same subnet on all other nodes in the cluster
You cannot change the designation of an interface from STATIONARY_IP to HEARTBEAT_IP
unless the subnet is common to all nodes.
Remember that the HEARTBEAT_IP must be an IPv4 address, and must be on the same subnet
on all nodes, except in cross-subnet configurations; see “Cross-Subnet Configurations
(page 27)).
You cannot delete a subnet or IP address from a node while a package that uses it (as a
monitored_subnet, ip_subnet, or ip_address) is configured to run on that node.
Information about these parameters begins at monitored_subnet (page 175).
You cannot change the IP configuration of an interface (NIC) used by the cluster in a single
transaction (cmapplyconf).
You must first delete the NIC from the cluster configuration, then reconfigure the NIC (using
ifconfig, for example), then add the NIC back into the cluster.
Examples of when you must do this include:
moving a NIC from one subnet to another
adding an IP address to a NIC
removing an IP address from a NIC
CAUTION: Do not 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. If you configure any address other than a stationary IP address on a
Serviceguard network interface, it could collide with a relocatable package address assigned by
Serviceguard.
Some sample procedures follow.
7.6.4.3 Example: Adding a Heartbeat LAN
Suppose that a subnet 15.13.170.0 is shared by nodes ftsys9 and ftsys10 in a two-node
cluster cluster1, and you want to add it to the cluster configuration as a heartbeat subnet.
Proceed as follows.
222 Cluster and Package Maintenance