Create cluster lock VG

[rohit kumar gupta]

i am creating 2 node cluster and i want to create cluster lock VG .
i created VG
then i did vgchage -a n
vgchange -C y /dev/vgname
then i did vgexport and then i imported on 2nd node.

then i activated vg by vgchange -a e

but when i am doing cmcheckconf then i am getting below error

First cluster lock volume group /dev/vg_cluster needs to be designated as a cluster aware volume group.
cmcheckconf: Unable to verify cluster file: new.conf.


please suggest .

[Michal Kapalka (mikap)]

hi,

check this threads :

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1036164

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1072708

mikap

[Vishu]

Hi Rohit,

you must have that VG configured as the cluster lock VG in the ASCII file you are using for cmapplyconf.

Also, no need to specify the following command

# vgchange -c y

just make that VG active on the server where you are giving the cmapplyconf command as

# vgchange -a y

and that is all. cmapplyconf will do the rest for you.

[Viktor Balogh]

>vgchange -C y /dev/vgname

The c must be lowercase. At least on my systems (11.11) there isn't any reference to '-C'. What OS version do you have?

[likid0]

Also remember that you need to have you lock vg /dev/vgname listed in the .ascii file in 2 places:

FIRST_CLUSTER_LOCK_VG /dev/vgname
VOLUME_GROUP /dev/vgname

[AVV]

Hi,

AM not sure but still I have a doubt on...correct me if I am wrong here..

Do we need to do anything line vgchange -C y vgname or vgchange -a e for cmapplyconf ??

I think(??) just create the VGs in first system and import the VGs to the second, activate, take a backup using vgcfgbackup and deactivate. Activate the VGs in first node again. Edit the ascii file and point the VGs including LOCK VG as required. DO the comcheck then...

[Stephen Doud]

My FIRST recommendation is to point you to the Managing Serviceguard manual. It is written to answer just such questions! It also illuminates one's understanding of how Serviceguard works and what to expect.
The manual is located here:
http://docs.hp.com/en/ha.html#Serviceguard

There is no need to perform 'vgchange -c y' and 'vgchange -a e' on the intended cluster lock VG.
To identify a cluster lock VG, select one that is already shared between servers, ie, loaded in /etc/lvmtab on each node.
Then add parameter references in the form of FIRST_CLUSTER_LOCK_VG and FIRST_CLUSTER_LOCK_PV and VOLUME_GROUP, identifying each properly in the cluster ASCII file. (see the manual for examples)
Then cmapplyconf the file.