HP Serviceguard Version A.11.18 Release Notes, September 2008

IMPORTANT: Although cross-subnet topology can be implemented on a single site,
it is most commonly used by extended-distance clusters, and specifically site-aware
disaster-tolerant clusters, which require HP add-on software.
Design and configuration of such clusters are covered in the disaster-tolerant
documentation delivered with Serviceguard. For more information, see the following
documents at http://www.docs.hp.com -> High Availability:
• Understanding and Designing Serviceguard Disaster Tolerant Architectures
• Designing Disaster Tolerant HA Clusters Using Metrocluster and Continentalclusters
• Using Serviceguard Extension for RAC
• The white paper Configuration and Administration of Oracle 10g R2 RAC Database in
HP Metrocluster
New Online Networking-Configuration Capabilities
You can now make significant changes to the cluster’s networking configuration while
the cluster is running.
What You Can Do
Online operations you can perform include:
• Add a network interface with its HEARTBEAT_IP or STATIONARY_IP.
• Add a standby interface.
• Delete a network interface with its HEARTBEAT_IP or STATIONARY_IP.
• Delete a standby interface.
• Change the designation of an existing interface from HEARTBEAT_IP to
STATIONARY_IP, or vice versa.
• Change the NETWORK_POLLING_INTERVAL and
NETWORK_FAILURE_DETECTIONparameters.
• A combination of any of these in one transaction (cmapplyconf), given the
restrictions below.
What You Must Keep in Mind
The following restrictions apply:
• You must not change the configuration of all heartbeats at one time, or change or
delete the only configured heartbeat.
At least one working heartbeat, preferably with a standby, must remain unchanged.
• In a CVM configuration, you can add and delete only data LANs and IP addresses.
You cannot change the heartbeat configuration while a cluster that uses CVM is
running.
What’s in this Release 43