Operating System - HP-UX
1832617 Members
2840 Online
110043 Solutions
New Discussion

Re: MSCG configuration problem

 
Raje
Occasional Contributor

MSCG configuration problem

Hi,
We have two N-4000/HP-UX 11.00/FC60 Server configured in MCSG.
We are getting a message in syslog and console :
"Mar 14 06:22:47 isbscs cmcld: WARNING: Cluster lock on disk /dev/dsk/c3t0d0 is missing!
Mar 14 06:22:47 isbscs cmcld: Until it is fixed, a single failure could
Mar 14 06:22:47 isbscs cmcld: cause all nodes in the cluster to crash
Mar 14 07:24:02 isbscs cmcld: WARNING: Cluster lock on disk /dev/dsk/c3t0d0 is missing!
Mar 14 07:24:02 isbscs cmcld: Until it is fixed, a single failure could
Mar 14 07:24:02 isbscs cmcld: cause all nodes in the cluster to crash"

In /etc/cmcluster/cmclconf.ascii the following information is available :
FIRST_CLUSTER_LOCK_PV /dev/dsk/c3t0d0

Pls. help me to resolve this.
Change is inevitable
3 REPLIES 3
Steven Sim Kok Leong
Honored Contributor

Re: MSCG configuration problem

Hi,

For ease of resolution, I would suggest that you make use of "Cluster Management" under SAM to stop and start the cluster and subsequently your packages.

Hope this helps. Regards.

Steven Sim Kok Leong
Brainbench MVP for Unix Admin
http://www.brainbench.com
melvyn burnard
Honored Contributor

Re: MSCG configuration problem

You have either replaced the cluster lock dosc, or it was never written to correctly at the time of cluster creation.
I suggest you halt the cluster, activate the cluster lock disc vg on the node you are working from, then re-apply the cluster binary to ensure that the cluster lock info gets written to the disc.
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
James R. Ferguson
Acclaimed Contributor

Re: MSCG configuration problem

Hi:

Document #UXSGKBAN00000022 (Replacing a clusterlock disk) describes the procedure you need to replace the cluster lock:

/begin_quote/

When the cluster-lock disk is replaced, or the clusterlock ID is missing on a disk, the cluster lock structure must be recreated to allow MC/ServiceGuard to use it.

If a vgcfgbackup was performed after the clusterlock disk was configured into the cluster, a simple vgcfgrestore command of this form would suffice:

# vgcfgrestore -n vg07 /dev/rdsk/c4t5d3

If the vgcfgbackup was not performed after the cmapplyconf, another cmapplyconf must be performed with the cluster halted to reestablish the disk listed in the cluster ASCII file as the clusterlock disk. The
command would be in the form:

# cmapplyconf -C cluster_ASCII -P pkg1/pkg1.conf ...

The ServiceGuard cluster checks the clusterlock disk every hour. If successful, the warnings that the clusterlock disk is missing should end.

/end_quote/

...JRF...