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

• 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 on the same subnet on all nodes, and
must be an IPv4 address.
• You cannot delete a primary interface without also deleting any standby interfaces,
unless the standby is being used by another primary interface that is not being
deleted.
• 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.
• You cannot change the IP configuration of an interface 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
For more information and examples, see “Changing the Cluster Networking
Configuration while the Cluster Is Running” in chapter 7 of Managing Serviceguard for
Linux.
New -c Option in cmquerycl
You can use cmquerycl -c <cluster_name> -C <filename> to produce a text
file (filename) showing the current configuration of the cluster, with additional,
commented-out, entries for network subnets that are not currently part of the cluster
configuration, but can be configured into it.
For example, 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. You can run cmquerycl -c to get a cluster
configuration template file that includes commented out entries for interfaces on that
subnet; for example:
cmquerycl -c cluster1 -C clconfig.ascii
The networking portion of the resulting clconfig.ascii file looks something like
this:
NODE_NAME ftsys9
NETWORK_INTERFACE lan1 ]
HEARTBEAT_IP 192.3.17.18
#NETWORK_INTERFACE lan0
#STATIONARY_IP 15.13.170.18
NETWORK_INTERFACE lan3
What’s in this Release 33