cluster lock volume group /dev/vg02 belongs to another cluster

[vaibhav_1]

I am configuring a two node cluster . I created the cluster between two nodes . Now I
want to change the node names . so I halted the cluster . changed the cluster configuration
file . removed the /etc/cmcluster/cmclconfig file .

Now when I try to do cmcheckconf . I am getting the above error message .

It seems some how it assumes all the volume groups are in the previous cluster .

any clue ?

[linuxfan]

Hi Vaibhav,

Did you change the host names of the nodes?

In anycase, try
vgchange -a n /dev/vg02
vgchange -c n /dev/vg02

Now run your cmcheckconf

-Regards
Ramesh

[Santosh Nair_1]

You should be able to deactivate the VG and take it out of the cluster using the commands:

vgchange -a n /dev/vg02
vgchange -c n /dev/vg02

Then reconfigure your new cluster appropriately, i.e.

cmcheckconf -C -P -P ...

then assuming you get no errors:

cmapplyconf -C -P -P ...

-Santosh

[Christopher McCray_1]

did you do a cmdeleteconf to the old cluster:

# cmdeleteconf -c

The cluster binary file will have the old node names and the of the cluster. You nmay have to do another cmquerycl to get everything back into order, and just to start off a new. Just as a side not, you should use cmdeleteconf to remove the cluster binary and not remove it.

Hope this helps
Chris

[linuxfan]

Hi again,

Actually you may have to activate the cluster lock VG, so you should try

vgchange -a n /dev/vg02
vgchange -c n /dev/vg02
vgchange -a y /dev/vg02


-Regards
Ramesh

[Sanjay_6]

Hi,

Like the others have already told, you will have to make the VG cluster unaware if you have deleted the previous cluster configuration. This you will have to do for all the cluster aware volume groups. Since you had halted the cluster, all the cluster aware volume groups would already be deactivated. But still you can deactivate them using

vgchange -a n /dev/vg_name

Now make the VG cluster un-aware

vgchange -c n /dev/vg_name

Now modify the new cluster config, add the Vg names, Lock disk / PV / Vg info and do a cmcheckconf. If that passes do a cmapplyconf to create the new cluster binaries.

Your procedure of deleting the Cluster config file was not correct. You should have done a cmdeleteconf to remove the old cluster infomation. Then done a cmcheckconf with the new conf file and then cmapplyconf.

Hope this helps.

Thanks

[vaibhav_1]

Thanks Guys ... It worked ..

Thanks again
Vaibhav