Volume groups in ServiceGuard

[Arne Wattman]

Hello !
In my cmclconf.ascii I have the following lines
regarding Volume Groups :

VOLUME_GROUP /dev/vg01
VOLUME_GROUP /dev/vg05

When I start up one of the package running in the cluster it does a vgchange -a e -q n on
/dev/vg01 and on /dev/vg02.
The package needs both volume groups to work, and it does. Now my question, why does this work ? Shouldn't /dev/vg02 be configured in cmclconf.ascii file in order to be activated ?

I'm running SG A.11.05 and HP-UX 11.0

Thanks
Arne

[Marco Santerre]

vg02 should definitely be part of your cmclconf.ascii file. The only thing that comes to mind at this point would be to check the date of your cmclconf.ascii and your cmclconfig to see if it hasn't been changed since the last cmapplyconf. Maybe someone has made some modifications to it and never cmapplyconf

[Rita C Workman]

As was mentioned something more than likely has been changed.

I might first do a man on cmcheckconf and run this command to find any problems.

Make sure what you have is good before your apply it with the cmapplyconf command.
Then when all is said and done if you want a new ascii file then run your cmgetconf and save it to a new fresh clean file.

Just my thoughts,
Rita

[Arne Wattman]

I did a strings cmclconfig|grep vg and it showed only /dev/vg01.

[James R. Ferguson]

Hi Arne:

Make sure that you aren't activating the volume group in 'etc/lvmrc'.

Regards!

...JRF...

[John Poff]

Hi,

The volume group entries in your cluster config file are there so that MC/SG can monitor them with the cmlvmd daemon to make sure that they don't get activated on two different nodes at the same time. When you [or your package] activates one of these VGs, the cmlvmd broadcasts a request to the cmlvmd daemons running on the other nodes to make sure that the VGs aren't activated on any other nodes.

You don't need your VGs in there for them to work, but it makes your cluster configuration much safer if they are. As the others have suggested you should make the change when you get the chance.

JP

[Marco Santerre]

As Rita mentionned, it would be interesting to find the output of cmcheckconf -v

[Arne Wattman]

And here is the result of cmcheckconf :

..
..
..
Verification completed with no errors found.

It's really not a problem since the package run's alright but......I wonder why !

/Arne

[Duncan Edmonstone]

Arne,

Find out whats *really* in your cluster binary file (rather than in its ascii equivalent) using cmgetconf :

cmgetconf /tmp/real_contents


HTH

Duncan

[Pramod_4]

Ame,

To answer your questions:

It is not necessary that your vg02 needs to be present in your cluster ascii config file. Cluster ascii config file is referred only when you invoke cmapplyconf command. Once the cmmapply command is run it keeps the entire cluster related config information in /etc/cmcluster/cmclconfig (binary) file.
Any cluster operation will refer the said binary file for any cluster-related information.

All the VGs configured in a cluster must be cluster aware VGs. You can make VGs cluster aware by putting them in your cluster ascii file and then by running "cmapplyconf" command or by using "vgchange -c y ".

Cluster aware VGs can only be activated by using "vgchange -a e "

To verify whether the activated VG is a cluster aware VG, do the following:

vgdisplay and look for VG status "available,exclussive" or do ???cmgetconf??? and look whether your VG is listed in the output.

Thanks,

Pramod

[Arne Wattman]

Hello again after a good night sleep !

I ran cmgetconf -c cluster_name filename

and in the output file volume group /dev/vg02
occurred !
So I'll take that file and make it my cmclconfig.ascii file.

Thanks everyone for help and hints !

Regards Arne Wattman

[Rajesh G. Ghone]

Hi Arne,
vg02 entry is not required in cmclconf.ascii u can specify in ur package.cntl file whatever VG u require for that particular package you can specify in package.cntl file.Once you specify in cntl file then those VG's will get activated.I hope this will solve your problem.

Regards,
Rajesh G.