topic Re: Separate cluster lock VG/PV? in Operating System - HP-UX

Separate cluster lock VG/PV?

Douglas D. Denney — Tue, 02 Aug 2005 12:33:39 GMT

I have a SG cluster connected to two EMC Clariion disk arrays. We are also using PowerPath. The EMC tech I spoke with recommended using a separate cluster lock VG/PV (i.e, not owned by any package).

1. Anyone have experience using ServiceGuard with a Clariion? Any thoughts you'd like to share?

2. How should I configure the lock VG/PV? Should I do a separate one, or use the devices in the first package on the system as the lock VG/PV?

3. If the lock VG/PV is not owned by a package, does it need to be active in order for the cluster to "see" it in the event of a cluster event?

Thanks!
Douglas Denney

Re: Separate cluster lock VG/PV?

Denver Osborn — Tue, 02 Aug 2005 12:38:12 GMT

nothing specific to help w/ the EMC Clarion, but I've setup a few clusters using a VA where we configured LUN0 at 10MB as a CE suggested, and used it for the lock disk. lun0 was never used for anything but the lock disk. Maybe this is what the emc tech is trying to get at.

-denver

Re: Separate cluster lock VG/PV?

melvyn burnard — Tue, 02 Aug 2005 12:39:07 GMT

1. What model array is this?

2. well a cluster lock disk has to be in a VG that is shared, but whether you set up a separate VG just for the cluster locking, or whether you use the VG for data as well is your personal choice.
Most sites I know of use the cluster lock VG(s) for data as well, as it seems a waste to have a full PV, or indeed two if you use dual cluster lock discs, just for this function.

3. No it does not, but it MUST be activated at the time of binary creation or modification.

Re: Separate cluster lock VG/PV?

Geoff Wild — Tue, 02 Aug 2005 13:08:01 GMT

I don't have any clariion's - but do use EMC DMX's...

Using PowerPath as well in a cluster with no issues.

You don't need a separate disk for the cluster lock...

Rgds...Geoff

Re: Separate cluster lock VG/PV?

Stephen Doud — Wed, 03 Aug 2005 08:27:37 GMT

SG version prior to A.11.16 don't have a problem recognizing the CLARiiON, but A.11.16 must be patched in order to allow the CLARiiON as a shared array.

The Serviceguard manufacturing lab explicitly supports (*) most HP arrays and many EMC symmetrix, but the CLARiiON is not on the "supported" list. We recommend that you seek an "allowance" as discussed in this website: http://www.hp.com/products1/serverconnectivity/mass_storage_devices

Since the CLARiiON is not "supported", I'm not certain if the lab will assist if a CLARiiON disk is used as a cluster lock VG/PV.

With a "supported" array, the cluster lock VG/PV may be one of the data disks.

There is no need to activate the cluster lock VG in order for Serviceguard to use the PV for arbitration.

* - in short, the term "supported" means that the lab has tested and warrants the particular configuration

Re: Separate cluster lock VG/PV?

Douglas D. Denney — Wed, 03 Aug 2005 21:24:53 GMT

Install patch PHSS_32740 for ServiceGuard fix my issue with Clariion arrays. MCSG is happy with them now. Thanks for your help.

Re: Separate cluster lock VG/PV?

Douglas D. Denney — Wed, 03 Aug 2005 21:27:12 GMT

Since I have access to the Clariion array, I plan to create a small LUN dedicated to acting as the cluster lock VG/PV. So far, I've been able to get the cluster to accept this configuration. Thanks for your help.