lock vg not activated

[himacs]

Hi Admins,

B.11.23

I have a 2 node cluster in which cluster clock is configured and included in ascii file.

But vglock is not activated in active mode.

vgdisplay vglock
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "vglock".


Please suggest,

Thanks is advance
himacs

[Ismail Azad]

Hi,

Seems like your volume group is not activated on both nodes. Hence if the vglock is marked as "cluster aware", then this command on any of the nodes could solve your problem.

vgchange -a e vglock

Regards
Ismail Azad

[Matti_Kurkela]

Sort of like the boot LIF on a system disk, the cluster lock is not inside any LV. The cluster lock is so small it fits inside the PV header. Every disk that's been pvcreate'd for the use with HP-UX LVM includes space for the cluster lock, even if it's never used for that purpose.

The PV header access is not controlled by VG activation, so it does not matter if the VG that contains the cluster lock is activated or not. What matters is that the disk device that contains up the cluster lock VG is accessible to all cluster nodes and properly identified in the cluster configuration file.

In fact, it's possible to use the VG that contains the lock as one of the cluster package VGs.

MK

[Manix]

But when are you getting this error ..are you
trying to view a cluster volume group which
activates when it`s called by a package as
defined in the package.cntrl script.

Yes if it`s a cluster VG & its not called by any package yet this command will throw the
error as expected one.

Thanks
Manix

[INH]

Is there any specific error.. can you provide more detailed & specific inputs to this problem

Regards,
INH

[himacs]

Hi Admins,

Thanks for your responses.

The VG is used only for cluster lock.

My concern was how inactive VG will be accessed by nodes ,during tie breaker.

<if the VG that contains the cluster lock is activated or not.>>

Matti cleared my doubt. So cluster lock VG need not to be activated.

INH, no specific errors and lock disks are fine.Shows output with diskinfo

Manix,
I will check the pkg script and update you.

Regards
himacs

[Manix]

>>The VG is used only for cluster lock.

So this means this VG may not be in any package.cnrl script( of course it`s possible
to do so & use it as data VG),yes should come into picture when there is a split - brain syndrome.

For two node cluster this is a mandatory requirement.

[John Bigg · Accepted solution]

Serviceguard does not access the cluster lock in the same way as normal volume groups are accessed. It accesses the physical volume direct with it's own kernel calls (ioctls). It does not require the volume group to be active since it accesses it at a lower level.

If the vglock volume group is used only for cluster lock, then there is no need for it to be active. What you show is perfectly fine.

Check the output of cmviewcl -v and it will show you the status of the lock disk from each node and if there is any problem. This will demonstrate access to the lock disk is fine irrespective of activation. The lock disk health is checked periodically by Serviceguard. The frequency depends on the version of Serviceguard.

[himacs]

Hi

Thread is very informative.Thanks to all who replied.Points assigned.

Closing the thread

himacs