Changing cluster lock disk in service guard ver 11.15, HPUX11.11

[Dominic Saul]

I have a project where SAN team moving from EMC to HDS disks. I have Service guard disk on EMC disks so i need to have know how we change cluster lock disk when cluster lock group is volume group used for oracle data in cluster,

extract from cluster ascii file

FIRST_CLUSTER_LOCK_VG /dev/vg_atlas_oracle

margay:/etc/cmcluster# vgdisplay -v /dev/vg_atlas_oracle
--- Volume groups ---
VG Name /dev/vg_atlas_oracle
VG Write Access read/write
VG Status available, exclusive
Max LV 255
Cur LV 5
Open LV 5
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 23017
VGDA 2
PE Size (Mbytes) 4
Total PE 23013
Alloc PE 20532
Free PE 2481
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg_atlas_oracle/oracle
LV Status available/syncd
LV Size (Mbytes) 8192
Current LE 2048
Allocated PE 2048
Used PV 1

LV Name /dev/vg_atlas_oracle/archive
LV Status available/syncd
LV Size (Mbytes) 40960
Current LE 10240
Allocated PE 10240
Used PV 1

LV Name /dev/vg_atlas_oracle/export
LV Status available/syncd
LV Size (Mbytes) 31440
Current LE 7860
Allocated PE 7860
Used PV 1

LV Name /dev/vg_atlas_oracle/redo_01
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 256
Allocated PE 256
Used PV 1

LV Name /dev/vg_atlas_oracle/Tivoli
LV Status available/syncd
LV Size (Mbytes) 512
Current LE 128
Allocated PE 128
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c19t4d2
PV Name /dev/dsk/c15t4d2 Alternate Link
PV Status available
Total PE 23013
Free PE 2481
Autoswitch On

[Stephen Doud]

The cluster lock disk must be in an LVM VG that is seen by both nodes in the cluster (in /etc/lvmtab). As long as the VG is associated with the cluster, it is a legitimate cluster lock VG (and PV, since it owns LUNs). To change the cluster lock VG and PV designations in the cluster binary file, do the following:
1) cd /etc/cmcluster
2) cmgetconf CLS.ASC
3) edit CLS.ASC and locate:
FIRST_CLUSTER_LOCK_VG
and in each node section:
FIRST_CLUSTER_LOCK_PV
4) identify a new VG that will remain under cluster control after the SAN migration has completed
5) identify a PV in that VG (in /etc/lvmtab)
6) edit the CLS.ASC file, with the new lock VG reference and for each node, lock PV reference.
7) cmcheckconf -C CLS.ASC
8) If step 7 succeeds, halt the cluster and apply the configuration change
9) cmapplyconf -C CLS.ASC

[wci]

Hi Stephen

one question
will cmcheckconf succeed if the cluster has an existing cluster lock configured and if the cluster is up?
I was doing the same thing on A11.14 version of MCSG but it was unable to verify the config.

regs

WCI

[Stephen Doud]

I believe cmcheckconf will complete (succeed) but will indicate that the cluster lock VG/PV cannot be changed online - meaning the cluster must be halted before cmapplyconf will succeed.

[Emil Velez]

Must halt the cluster to change lock configuration.

halt cluster
edit cluster config file
apply cluster config file
start cluster