HP Serviceguard manual Replacing a Failed Quorum Server System, After Replacing the Card

NOTE: After replacing a Fibre Channel I/O card, it may necessary to reconfigure the SAN to use the World Wide Name (WWN) of the new Fibre Channel card if Fabric Zoning or other SAN security requiring WWN is used.

After Replacing the Card

After the online or offline replacement of LAN cards has been done, Serviceguard will detect that the MAC address (LLA) of the card has changed from the value stored in the cluster binary configuration file, and it will notify the other nodes in the cluster of the new MAC address. The cluster will operate normally after this.

It is also recommended that you update the new MAC address in the cluster binary configuration file by re-applying the cluster configuration. Use the following steps for on-line reconfiguration:

1.Use the cmgetconf command to obtain a fresh ASCII configuration file, as follows: cmgetconf -c clustername config.ascii

2.Use the cmapplyconf command to apply the configuration and copy the new binary file to all cluster nodes:

cmapplyconf -C config.ascii

This procedure updates the binary file with the new MAC address and thus avoids data inconsistency between the outputs of the cmviewconf and lanscan commands.

Replacing a Failed Quorum Server System

When a Quorum Server (QS) fails or becomes unavailable to the clusters it is providing quorum services for, this will not cause a failure on any cluster. However, the loss of the quorum server does increase the vulnerability of the clusters in case there is an additional failure. Use the following procedure to replace a defective quorum server system. If you use this procedure, you do not need to change the configuration of any cluster nodes.

1.Remove the old Quorum Server system from the network.

2.Set up the new system and configure it with the old quorum server’s IP address and hostname.

3.Install and configure the Quorum Server software on the new system. Be sure to include in the new QS authorization file (/etc/cmcluster/qs_authfile) all of the nodes that were configured for the old quorum server. Refer to the qs(1) manpage for details about configuring the QS authorization file.

4.Start the Quorum Server as follows:

•Edit the /etc/inittab file to add the Quorum Server entries.

•Use the init q command to run the Quorum Server.

See the qs(1) manpage for more details.

5.All nodes in all clusters that were using the old Quorum Server will connect to the new quorum server. Use the cmviewcl -vcommand from any cluster that is using the quorum server to verify that the nodes in that cluster have connected to the QS.

6.The Quorum Server log file on the new quorum server will show a log message like the following for each cluster that uses the Quorum Server:

Request for lock /sg/<ClusterName> succeeded. New lock owners: N1, N2

7.To check that the Quorum Server has been correctly configured and to verify the connectivity of a node to the quorum server, you can execute the following command from your cluster nodes as follows:

cmquerycl -qQSHostName -nNode1 -nNode2 ...

The command will output an error message if the specified nodes cannot communicate with the quorum server.

328 Troubleshooting Your Cluster