Replace cluster lock disk in running cluster

[Ganesh Balraman]

Hi All!

I have running cluster system with mirrored vg dedicated for cluster lock.

One of the disk failed in cluster vg.

What is the procedure to replace cluster lock failed disk in running cluster?

Thanks,

[P Arumugavel]

You can replace an unusable lock disk while the cluster is running, provided you do not change the devicefile name (DSF).

Replace a failed LVM lock disk in the same way as you replace a data disk. If you are using a dedicated lock disk (one with no user data on it), then you need to use only one LVM command, for example:

# vgcfgrestore -n /dev/vg_lock /dev/dsk/cXtXdX

Serviceguard checks the lock disk every specified seconds. After using the vgcfgrestore command, review the syslog file of an active cluster node for not more than specified period. By this time you should see a message showing that the lock disk is healthy again.

http://docstore.mik.ua/manuals/hp-ux/en/B3936-90122/ch08s03.html#cegjbiej


Rgds...

[Emil Velez]

you would use the same procedure to fix the lock disk in a cluster as you would for a non lock disk. THe cluster will see it after the volume group is reactivated to recognize the replaced disk.

with SG 11.19 you could define a different lock disk but of course you are planning on replacing the failed disk before another cluster event happens right ?

[nijokj]

If you need to replace a disk under the HP-UX 11i v3 agile addressing scheme you may need to use the io_redirect_dsfcommand to reassign the existing DSF to the new device.

Important note: If, for any reason, you are not able to use the existing DSF for the new device, you must halt the cluster and change the name of the DSF in the cluster configuration file

Updating the Cluster Lock Disk Configuration Online

You can change the device file names (DSFs) of the cluster lock physical volumes (that is, the values of the FIRST_CLUSTER_LOCK_PV and SECOND_CLUSTER_LOCK_PV parameters in the cluster configuration file) without bringing down the cluster, under the following conditions:

You are not changing the physical disks themselves

You are changing values that already exist in the cluster configuration file, not adding or deleting them

The node on which you are making the change is not running in the cluster (that is, you have halted it by means of cmhaltnode, or by selecting Halt Node in Serviceguard Manager)

The cluster nodes are running Serviceguard 11.17.01 or later

To update the values of the FIRST_CLUSTER_LOCK_PV and SECOND_CLUSTER_LOCK_PV parameters without bringing down the cluster, proceed as follows:

Halt the node (cmhaltnode) on which you want to make the changes.

In the cluster configuration file, modify the values of FIRST_CLUSTER_LOCK_PV and SECOND_CLUSTER_LOCK_PV for this node.

Run cmcheckconf to check the configuration.

Run cmapplyconf to apply the configuration.

Restart the node (cmrunnode).

Repeat this procedure on each node on which you want to make the changes.




Updating the Cluster Lock Disk Configuration Offline


If you cannot meet the conditions spelled out above for updating the configuration online, or you prefer to make the changes while the cluster is down, proceed as follows:

Halt the cluster.

In the cluster configuration file, modify the values of FIRST_CLUSTER_LOCK_PV and SECOND_CLUSTER_LOCK_PV for each node.

Run cmcheckconf to check the configuration.

Run cmapplyconf to apply the configuration.