HP Serviceguard Cmquerycl -C clconfig.ascii -c cluster1 -n ftsys8 -n ftsys9, What You Can Do

there are packages that depend on the unreachable node, halt the cluster or use Serviceguard commands as described in the next section.

Use the following procedure to delete a node with HP-UX commands. In this example, nodes ftsys8, ftsys9 and ftsys10 are already configured in a running cluster named cluster1, and you are deleting node ftsys10.

NOTE: If you want to remove a node from the cluster, run the cmapplyconf command from another node in the same cluster. If you try to issue the command on the node you want removed, you will get an error message.

1.Use the following command to store a current copy of the existing cluster configuration in a temporary file:

cmgetconf -c cluster1 temp.ascii

2.Specify the new set of nodes to be configured (omitting ftsys10) and generate a template of the new configuration:

cmquerycl -C clconfig.ascii -c cluster1 -n ftsys8 -n ftsys9

3.Edit the file clconfig.ascii to check the information about the nodes that remain in the cluster.

4.Halt the node you are going to remove (ftsys10 in this example): cmhaltnode -f-v ftsys10

5.Verify the new configuration: cmcheckconf -C clconfig.ascii

6.From ftsys8 or ftsys9, apply the changes to the configuration and distribute the new binary configuration file to all cluster nodes:

cmapplyconf -C clconfig.ascii

NOTE: If you are trying to remove an unreachable node on which many packages are configured to run (especially if the packages use a large number of EMS resources) you may see the following message:

The configuration change is too large to process while the cluster is running.

Split the configuration change into multiple requests or halt the cluster.

In this situation, you must halt the cluster to remove the node.

Changing the Cluster 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 a HEARTBEAT_IP or STATIONARY_IP interface from IPv4 to IPv6, or vice versa.

•Change the designation of an existing interface from HEARTBEAT_IP to STATIONARY_IP, or vice versa.

•Change the NETWORK_POLLING_INTERVAL.

•Change the NETWORK_FAILURE_DETECTION parameter.

•Change the NETWORK_AUTO_FAILBACK parameter.

Reconfiguring a Cluster 297