changing lock device

[kgraff]

Hi

This is probably an easy one. I have switched from a SAN to a NAS, and now I need to change lock device from the old VG to one of the new.

I shut down the cluster with cmhaltcl -f and then I try to cmapplyconf, but the VG is not cluster aware. I can't make it cluster aware because "Cluster Services not available".

What part am I missing? If anyone could give me the steps I need to take to perform this task, I 'd be greatful.

Thanks ,
Kenneth

[Duncan Edmonstone]

Kenneth,

If cluster services are halted...

vgchange -c n vgNN
vgchange -a y vgNN
cmapplyconf -C ...
vgchange -a n vgNN
cmruncl
vgchange -c y vgNN

cmrunpkg ...

HTH

Duncan

[kgraff]

Hm, I thought I did just that.

Does it matter from wich node I do this? I read something about only activating the VG on one node.

I noticed one strange thing when trying to use SAM. When listing VGs available as lock devices, only the old, now unused VGs showed up, none of the new actually in use ones. Earlier I have move all of the packages to new disks, and have been running the packasges without problem since then, but it seems as the cluster is unaware of them.

Kenneth
(sorry for not awarding any points yet, I have to wait for next service window before trying the suggested)

[Duncan Edmonstone]

wow, what version of Serviceguard are you using? I didn't think SAM has worked for cluster admin for a long time...


if you run vgdisplay on your clustered volume groups, as long as they show:

VG Status available, exclusive

then the cluster knows about them... really they should also be listed in the cluster configuration as well

HTH

Duncan

[Basheer_2]

What does it show in the /etc/cmcluster/cmclconfig.ascii

does it refer to old one or the new one.

did you also do
cmcheckconf -v -C /etc/cmcluster/cmclconfig.ascii

cmapplyconf -v -C ...

[Stephen Doud]

I checked the Serviceguard divisions' website this morning and verified that NAS devices are not supported with Serviceguard. I then checked this site http://www.hp.com/products1/serverconnectivity/mass_storage_devices#Network_Appliance and see agreement as well.

Now let's assume you are not using a NAS, but a SAN array. Others have given the procedure to manually apply a cluster ID to the VG, and indicated that a lock disk must be referenced in the cluster ASCII file and activated and cmapplyconf performed.

The Managing Serviceguard manual @ http://docs.hp.com/en/B3936-90135/B3936-90135.pdf is the definitive resource:

Page 361+ addresses how to modify the cluster lock disk configuration.