Changing Cluster lock disk

[Spark_2]

Hi,

What all should be kept in mind while planning to change the cluster lock disk.

[Steven E. Protter]

Shalom,

No consideration at all.

The disk needs to be shared.

Edit the configuration file.

cmquerycl
cmcheckconf
cmapplycon

Done, no down time.

SEP

[Roopesh Francis_1]

Hi,
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

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

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.
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.

[Spark_2]

Thank you for your answer.
Can the cluster lock disk which doesnt have any data, be pulled out as after deactivating. Please give the steps from the start

[piyush mathiya]

If you have an HP Support Contract, you have the right to access the ITRC Knowledge Database, where you can find a document titled "Changing the Cluster Lock Physical Disk", document ID emr_na-c01028243-10

Since this document was created by HP to help customers who have support contracts, it cannot be shown in this free forum.

[Vinod Kumar Yadav · Accepted solution]

Hi,

For Changing the Cluster Lock Disk the.

General Cluster Lock Disk Procedures

The cluster must be halted

Starting on node A:
A# mkdir /dev/vglock
A# mknod /dev/vglock/group c 64 0x020000 # If minor number 0x020000 is already in use, use a free number!!
A# pvcreate -f /dev/rdsk/c6t0d1
Physical volume "/dev/rdsk/c6t0d1" has been successfully created.
A# vgcreate /dev/vglock /dev/dsk/c6t0d1
Volume group "/dev/vglock" has been successfully created.
Volume Group configuration for /dev/vglock has been saved in /etc/lvmconf/vglock.conf
A# echo "0x2008?4X" | adb /dev/dsk/c6t0d1 # Save these results for later on

ï ¬ Check Volume Group definition on A:
A# strings /etc/lvmtab

ï ¬ Export the volume group to mapfile and copy this to node B
A# vgchange -a n /dev/vglock
Volume group "/dev/vglock" has been successfully changed.
A# vgexport -v -p -m /etc/cmcluster/vglockmap vglock
Beginning the export process on Volume Group "/dev/vglock".
/dev/dsk/c6t0d1
A# scp -p /etc/cmcluster/vglockmap B:/etc/cmcluster

ï ¬ Import the volume group definition on node B and check the volume group definition
B# mkdir /dev/vglock
B# mknod /dev/vglock/group c 64 0x020000 # Note: The minor number has to be the same as on node A
B# vgimport -v -m /etc/cmcluster/vglockmap vglock
Beginning the import process on Volume Group "/dev/vglock".
Volume group "/dev/vglock" has been successfully created.
B# strings /etc/lvmtab
B# echo "0x2008?4X" | adb /dev/dsk/c6t0d1 # Compare to other system. Values must match!

â ¢ Edit the cluster configuration file

â ¢ Check the cluster configuration file
A# cmcheckconf -v -C cluster.ascii

â ¢ Create the binary configuration file and distribute the cluster configuration to all the nodes in the cluster:
A# cmapplyconf -v -C cluster.ascii

â ¢ De-activate the lock disk on the configuration node after cmapplyconf
A# vgchange -a n /dev/vglock

â ¢ Make Cluster Lock volume group sharable and cluster aware (not packages) from the cluster configuration node. This has to be done only once.
A# vgchange -S y -c y /dev/vglock

â ¢ Start the cluster from any node in the cluster
A# cmruncl -v
Or, on each node at a time
A/B# cmrunnode -v