HP ServiceGuard 11.16 and Cluster lock

[njia_1]

I finished my HP service guard training course this Feb and I was told by the intrusctor that for HP SG 11.16 we can remove the cluster lock without taking the cluster down.

But I could not find this information in HP document.

Does anyone else hear the same ? anyone sees this in HP document ? Which one ? Where can I find it?

points will be assigned to all responses.

thanks
Nan

[melvyn burnard · Accepted solution]

I am sorry to say but your instructor was incorrect.
To remove a cluster lock disc from a configuration requires a re-apply of the binary using cmapplyconf with the cluster in the down state.
See Table 7.1 on page 302 of http://docs.hp.com/en/B3936-90079/B3936-90079.pdf

[vinod_25]

hi nila

hope the attachment helps u ...

Regards

Vinod K

[Stf]

It exist a tool that allow you to remove the cluster lock without taking the cluster down, it is called cminitlock if I remember well but it's not supported by HP but it works very fine !!!

Stf ;-)

[Stf]

also look at this thread :

http://forums1.itrc.hp.com/service/forums/questionanswer.do?admit=716493758+1119517431091+28353475&threadId=17401

Stf ;-)

[melvyn burnard]

the cminitlock tool will not allow you to remove the cluster lock disc.
It is only used to re-initialize the disc that is accessed by the device file listed in the cluster ascii and binary, usually when a disc has been replaced.

[Stephen Doud]

Use cmviewconf to look at the contents of the /etc/cmcluster/cmclconfig file.
This is the cluster binary file which is created using cmapplyconf with a cluster configuration file and optionally with package configuration files.
As you look at it, you will find a reference to the lock VG and PVs.

Example:
# cmviewconf | grep -e "Node name" -e lock
flags: 12 (single cluster lock)
first lock vg name: /dev/vg01
second lock vg name: (not configured)
Node name: bunker
first lock pv name: /dev/dsk/c0t2d0
first lock disk interface type: c720
Node name: buster
first lock pv name: /dev/dsk/c0t2d0
first lock disk interface type: c720

cmapplyconf is the only command that can change the /dev/dsk path of the lock device on every cmclconfig file (each node has one). Serviceguard cannot change the cluster lock VG and PV references while the cluster is running. The cluster binary file is loaded into the memory of every server in the cluster when the cluster forms. Thereafter, the file is not referenced until the next cluster formation, or until a node leaves the cluster and re-joins later.

Although cminitlock can put the cluster lock structures on a disk while the cluster is running, it does not have the ability to alter the cmclconfig file /dev/dsk pointer to the cluster lock disk.

[njia_1]

thanks for all the responses.