MC/ServiceGuard cluster lock disk

[Chuck Coar]

when configuring a new vglock disk....disk is on an EMC array.
vg lock disk (vglock), has no filesystem on it.
nodea - vglock is not cluster aware and is active outside of the cluster (vgchange -a n vglock, vgchange -c n vglock, vgchange -a y vglock)
nodeb - vglock is not cluster aware and not active
cluster services: down
check: fails with error saying that vglock has to be cluster aware
apply: fails with error saying that vglock has to be cluster aware
no errors in the syslog

We are unable to make the vglock cluster aware, since that would mean having to have the cluster services up when we check and apply...however, we did make the vglock cluster aware just to test, and it gave us the error..cluster services have to be down to apply. we seem to be going around in circles...any help would be appreciated.

[MARTINACHE]

Here is a my method when I create a cluster.

NODE1 :
- create the vglock on node1
- vgchange -a y vglock
- vgexport -v -p -s -m /tmp/vglock.map vglock
- vgchange -a n vglock

NODE2:
- copy /tmp/vglock.map on node2
- mkdir /dev/vglock
- mknod /dev/vglock/group c 64 0x......
- vgimport -v -s -m /tmp/vglock.map
- vgchange -a y /dev/vglock (check thas it's OK)
- vgchange -a n

NODE1:
- start the cluster only on this node whitout any package.
- vgchange -c y /dev/vglock

try to make a "vgchange -a e /dev/vglock".

stop the cluster
start the cluster on all nodes

Patrice.

[Byron Myers]

Jason,
Make a one node cluster. This should NOT require a lock VG, so comment it out of the cluster configuration file. You should then be able to do your cmapplyconf, bring up the one node cluster, and do your "vgchange -c y" on your VG's. Then bring the one node cluster down, and add in the second node, with the "cluster aware" VG for the lock VG.

[John Palmer]

Hi Jason,

This is an unusual problem, there should be no need to have the cluster up to configure the cluster lock disk, cmapplyconf should do it for you.

What have you got defined in the cluster configuration file? You should have something like:-

FIRST_CLUSTER_LOCK_VG /dev/vg01
...
NODE_NAME
...
FIRST_CLUSTER_LOCK_PV /dev/dsk/c5t0d0
...
NODE_NAME
...
FIRST_CLUSTER_LOCK_PV /dev/dsk/c5t0d0
...
VOLUME_GROUP /dev/vg01

Note that your cluster lock volume group should be in the list of cluster aware volume groups.

Regards,
John

[melvyn burnard]

Jason, from what I can gather you are trying to change your Cluster Lock disc to a new device?
If so, this has to be done with teh cluster down, and the lock disc vg enabled in non-cluster aware mode on the node you are working on. You then need to reapply your binary configuration to set the cluster lock information.
Changing the cl disc cannot be done on-line.