about mc/serviceguard

[pang_3]

I met some problem witch mc/serviceguard.
I have a cluster named hpcluster,I have two volume groups in the cluster. It does work.
when i want to change the configure,I met problem.
I use cmcheckconf to test my new config, it appears to have some errors:

Begin checking the nodes...
Looking for other clusters ... Done
Gathering configuration information ........... Done
Warning: The disk at /dev/dsk/c3t2d0 on node smcp1 does not have an ID.
Warning: The disk at /dev/dsk/c3t2d0 on node smcp2 does not have an ID.
Warning: Disks which do not have IDs cannot be included in the topology descript
ion.
Use pvcreate(1m) to give a disk an ID.
Error: Volume group /dev/vg00 is configured differently on node smcp1 than on no
de smcp2
Error: Volume group /dev/vg00 on node smcp2 does not appear to have a physical v
olume corresponding to /dev/dsk/c1t2d0 on node smcp1 (567706527973230959).
Error: Volume group /dev/vg00 is configured differently on node smcp2 than on no
de smcp1
Error: Volume group /dev/vg00 on node smcp1 does not appear to have a physical v
olume corresponding to /dev/dsk/c1t2d0 on node smcp2 (5587065871026805893).
Warning: The volume group /dev/vg00 is activated on more than one node:
smcp1
smcp2
Warning: Volume groups should not be activated on more than one node.
Use vgchange(1m) to de-activate a volume group on a node.
Failed to gather configuration information.

But i find that my disks are ok by use "diskinfo" and "vgdisplay" command. The disk /dev/dsk/c3t2d0 is my DVD-ROM

[Julio Yamawaki]

Pang,

this message is a warning and it's normal eveytime you create or update your cluster configuration.
No worries.

[RAC_1]

You can very well ignote warning message for DVD-ROM. Check the volume groups on both nodes. Did you add any pv to any of the cluster aware vgs and did not update them on other node?

You can do this as follows.

On node where packages are active, do vgexport -spvm /tmp/vgxx.map vgxx
Reapet same for all cluster aware vgs. Put the map files onto another node. Do rm /dev/vgxx.
Then do mkdir /dev/vgxx and mknod /dev/vgxx/group c 64 0x0x0000
Then do vgimport -sv -m /tmp/vgxx.map.

Then do check cmcheckconf.

Anil

[Geoff Wild]

Sounds like you made vg00 cluster aware.

Assuming vg00 is your root disk, do a:
vgchange -c n vg00

The re-run cmcheckconf

You should NOT have any errors....

Here's mine:

cmcheckconf -v -C pcha.ascii

Checking cluster file: pcha.ascii
Checking nodes ... Done
Checking existing configuration ... Done
Gathering configuration information ... Done
Gathering configuration information ... Done
Gathering configuration information ............. Done
Cluster pcha is an existing cluster
Checking for inconsistencies .. Done
Cluster pcha is an existing cluster
Maximum configured packages parameter is 16.
Configuring 4 package(s).
12 package(s) can be added to this cluster.
Modifying configuration on node svr003
Modifying configuration on node svr004
Modifying the cluster configuration for cluster pcha.

Verification completed with no errors found.
Use the cmapplyconf command to apply the configuration.



Rgds...Geoff

[Stephen Doud]

Consider these possibilities:

1) vg00 for both systems was "cloned" from a single system. Use this on each node to determine if the VGID for each vg00 is the same:

# vgexport -ps -m mapfile vg00 2>/dev/null ; grep VGID mapfile

See this document if they were cloned: UXSGKBRC00007573

2) A disk in vg00 is listing NO_HW in ioscan output.

Use 'ioscan -fnC disk' on both nodes.
Look to see if NO_HW appears for /dev/dsk/c1t2d0 on either node.

Correct the NO_HW problem before proceeding.

3) RCEN KBRC00006460 indicates a reboot may clear the problem.

[Ashwani Kashyap]

Seems like your vg00 is a cluster aware VG and is also activated on both nodes .
Check the cluster ascii files .

Usually vg00 should not be cluster aware and should be local to each node .

[Ryan McKlveen]

make sure that the volume groups is
A) 'shareable'
B) active when you run the cmcheckconf

HTH