Volume group configured differently on node1 than on node2

[Manju Kampli]

I have two v-class servers, and trying to configure them for MC/SG. V2500 (node01) has alternate links to the disk, where as V2600 (node02) has only one link to the disk.
As A part of MC/SG setup, I have exported the Volume group and imported on to the other system. Added the volume group to the cmclconf.ascii file. marked the volume group for SG use.
To verify the the configuration when I did cmcheckconf I received the following error.
Error: Volume group /dev/vgorasw is configured differenlty on node node01 than on node node02.

Does any one can pass some light on this !!

Is the problem due to one system has two links and other doesn't ??

Thanks

[melvyn burnard]

Yes!
You have to have the VG configured the same on all nodes sharing the VG, otherwise you will get the problem you are seeing.

[Stefan Farrelly]

We have a similar setup here, on one SG node our VG has alternate links, but on the other SG node we only have 1 SCSI cable to these disks so cant have alternate links.
The solution is to either remove the alternate links from the VG on both nodes (which we did), or add a second SCSI connection on your node without the alternate links, so that you can setup alternate links on both nodes. But yes, you must have the same VG setup on both nodes in your cluster.

[Vincente Fernandes]

Try recreating the volume group on server A from scratch and import the same on server B, if there is no data currently. I guess when you do a vgchange it has to be in exclusive mode under SG environment. Also try regenerationg SG cluster config files.

[Vince Inman]

Stefan nailed it. cmcld expects duplicate i/o configurations for machines in the
cluster. Alternative to removing the PVlinks, you can simply pull the cable off
the second interface (so as to only have one path), gen your cluster, and plug the cable back in to pick up the PVlinks.