topic Re: Newbie question: configuring serviceguard with LVM in Operating System - Linux

Newbie question: configuring serviceguard with LVM

Stanley Nguyen — Wed, 14 Jul 2010 05:38:25 GMT

hi,

i have configured a two node cluster using a single lock disk. I think I have set up everything correctly since cluster/nodes are started up fine. However, when I bring down node 1, my cluster's volume group is not activated on node 2 as well as the file system is not mounted on node 2. Volume group is still activated on node 1 though. Is the cluster supposed to deactivate that VG on node 1 and activate on node 2 for me? I have been trying to read up on HP Service Guard User Guide but I'm not really going anywhere. Is there a good dummy guide somewhere for newbie like me?

thanks,

-s

Re: Newbie question: configuring serviceguard with LVM

Matti_Kurkela — Wed, 14 Jul 2010 07:52:22 GMT

Serviceguard configuration has two major elements:
- the cluster configuration, which defines the overall cluster framework
- the package configuration, which defines the resources and services that can move between the cluster nodes.

The VG activation is controlled by the package configuration, yet you tell nothing at all about any packages. *Do* you have any packages configured at all yet?

Please run "cmviewcl -v" and attach the output to this thread. You can mask the IP addresses and any node/package names if you wish.

If you have problems with Serviceguard, your first troubleshooting step should always be to check the logs: both the system log and the package log.

Knowing the Serviceguard version would be important too: please run "cmversion" to find the version number.

A common mistake is forgetting to enable "AUTO_RUN" for your package after starting it up manually. The AUTO_RUN bit "arms" the package failover mechanism: if it's disabled, the package won't move away from the node it's currently running on.

If you use cmhaltpkg to halt a package, it will automatically disable AUTO_RUN for that package. But starting a package with cmrunpkg does not automatically re-enable AUTO_RUN: you must do it explicitly with "cmmodpkg -e ".

Finally, are you aware that Serviceguard for Linux is a discontinued product? HP neither develops nor sells it any more. It's still supported until the end of April 2014, but no patches will be released after April 2012.

http://h18026.www1.hp.com/solutions/enterprise/highavailability/linux/serviceguard/SGLX_Customer_Discontinuance_FAQ.pdf

MK

Re: Newbie question: configuring serviceguard with LVM

Steven E. Protter — Wed, 14 Jul 2010 18:24:26 GMT

Shalom,

The failure of Volume Group Activation should be documented in the /var/log/messages file or the service guard linux log file.

SEP

Re: Newbie question: configuring serviceguard with LVM

Stanley Nguyen — Wed, 14 Jul 2010 20:22:22 GMT

Hi guys,

Thanks for your response. I should have mentioned that I am trying to set it up on HP UX Itanium (not Linux). I think the package has not set up properly since when I tried to run it, I got this error where the VG can not be activated.

########### Node "hpita26": Starting package at Fri, Mar 12, 2010 01:03:24 PM ###########
Mar 12 01:03:24 PM - "hpita26": Activating volume group ClusterVG with non-exclusive option.
vgchange: Activation mode requested for the volume group "/dev/ClusterVG" conflicts with configured mode.
ERROR: Function activate_volume_group
ERROR: Failed to activate ClusterVG
Mar 12 01:03:24 PM - Node "hpita26": Deactivating volume group ClusterVG
vgchange: Volume group "ClusterVG" has been successfully changed.

########### Node "hpita26": Package start failed at Fri, Mar 12, 2010 01:03:24 PM ###########

Please see the requested info here. Thanks a lot for your help.

1) Version: A.11.17.01
2) cmviewcl -v:

CLUSTER STATUS
HPCluster up

NODE STATUS STATE
hpita26 up running

Cluster_Lock_LVM:
VOLUME_GROUP PHYSICAL_VOLUME STATUS
/dev/LockVG /dev/dsk/c5t0d2 up

Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 0/5/1/0 lan2
PRIMARY up 0/1/2/0 lan0

NODE STATUS STATE
hpita27 up running

Cluster_Lock_LVM:
VOLUME_GROUP PHYSICAL_VOLUME STATUS
/dev/LockVG /dev/dsk/c5t0d2 up

Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 0/5/1/0 lan2
PRIMARY up 0/1/2/0 lan0

UNOWNED_PACKAGES

PACKAGE STATUS STATE AUTO_RUN NODE
myPackage down halted disabled unowned

Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual

Script_Parameters:
ITEM STATUS NODE_NAME NAME
Subnet up hpita26 10.107.180.0
Subnet up hpita27 10.107.180.0

Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled hpita26
Alternate up enabled hpita27

Re: Newbie question: configuring serviceguard with LVM

Stanley Nguyen — Wed, 14 Jul 2010 21:04:25 GMT

Never mind. I got it working. Thanks everyone.

Re: Newbie question: configuring serviceguard with LVM

Emil Velez — Wed, 14 Jul 2010 23:06:16 GMT

Take a 1 week HP ServiceGuard course. You will become very very familiar with ServiceGuard and packages like a oracle database which you do in the course.

Re: Newbie question: configuring serviceguard with LVM

Stanley Nguyen — Thu, 22 Jul 2010 23:06:33 GMT

Need to update the control script.