Managing HP Serviceguard for Linux Ninth Edition, April 2009

5. Power up the system.
6. As the system comes up, the kudzu program on Red Hat systems will detect and
report the hardware changes. Accept the changes and add any information needed
for the new LAN card. On SUSE systems, run YAST2 after the system boots and
make adjustments to the NIC setting of the new LAN card. If the old LAN card
was part of a “bond”, the new LAN card needs to be made part of the bond. See
“Implementing Channel Bonding (Red Hat)” (page 153) or “Implementing Channel
Bonding (SUSE)” (page 156).
7. If necessary, add the node back into the cluster using the cmrunnode command.
(You can omit this step if the node is configured to join the cluster automatically.)
Now 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.
HP recommends that you update the new MAC address in the cluster binary
configuration file by re-applying the cluster configuration. Use the following steps for
online reconfiguration:
1. Use the cmgetconf command to obtain a fresh ASCII configuration file, as follows:
cmgetconf config.conf
2. Use the cmapplyconf command to apply the configuration and copy the new
binary file to all cluster nodes:
cmapplyconf -C config.conf
This procedure updates the binary file with the new MAC address and thus avoids
data inconsistency between the outputs of the cmviewconf and ifconfig commands.
Replacing a Failed Quorum Server System
When a quorum server 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.
276 Troubleshooting Your Cluster