Operating System - HP-UX
1834827 Members
2472 Online
110070 Solutions
New Discussion

Re: cmcheckconf, missing volumes

 
SOLVED
Go to solution
brian nelson_1
Occasional Contributor

cmcheckconf, missing volumes

I am trying to rebuild a 2 node cluster for MCSG. I ran "cmcheckconf -C cluster.asc", and
received the following errors;
Error: The physical volume with name /dev/dsk/c7t0d4 on node earth cannot be found on node mars
Error: The physical volume with name /dev/dsk/c8t1d4 on node earth cannot be found on node mars

I ran "vgexport" from the "earth" node and tried to do a "vgimport" on the "mars" node,
however i received the message volume group already exists on "mars". I believe a couple of new file systems were created on "earth" and that is why i'm getting the errors Any help with this issue would be greatly appreciated.
4 REPLIES 4
linuxfan
Honored Contributor
Solution

Re: cmcheckconf, missing volumes

Hi Brian,

Did you add the two disks /dev/dsk/c7t0d4 and /dev/dsk/c8t1d4 on earth after the VGs were defined on both earth and mars, if that is the case, one of the things you can do is

On Earth
vgexport -v -s -p -m /tmp/vg??.map /dev/vg??

rcp /tmp/vg??.map mars:/tmp/vg??.map

On Mars
ll /dev/vg??/group
(get the minor number , you can use this later)
vgchange -a n /dev/vg??
vgexport /dev/vg??.map
mkdir /dev/vg??
mknod /dev/vg??/group c 64
[ where is the 0x0??000 number you obtained early on]

vgimport -v -s -m /tmp/vg??.map /dev/vg??

What this would do is import the VG /dev/vg?? on mars.

-HTH
Ramesh
They think they know but don't. At least I know I don't know - Socrates
Sanjay_6
Honored Contributor

Re: cmcheckconf, missing volumes

Hi,

What it looks like to me is that the two disks referred are not being seen on Server mars. Can you see those two disks as c7t0d4 and c8t1d4 in ioscan.

Thanks
Sanjay
linuxfan
Honored Contributor

Re: cmcheckconf, missing volumes

Hey Brian,

One more thing, for MC-SG the disks need to be shared between the machines. I hope the disks you added to the VGs on earth later on were also being seen by mars(even though the actual device file may be different).

An excellent tool to see common disks is inq (from EMC)
ftp://ftp.emc.com/pub/symm3000/inquiry/v4.3.1.0

-HTH
Ramesh
They think they know but don't. At least I know I don't know - Socrates
brian nelson_1
Occasional Contributor

Re: cmcheckconf, missing volumes

Thanks Ramesh. Your solution for the missing disk issue worked perfectly. I now have a couple of new errors when i run cmcheckconf.
First error is as follows;
Warning: Network interface lan6 on node earth couldn't talk to itself.
Error: No bridged net specified for NM_ID 6 at earth
Second set of errors has to do with the Oracle packages i had previously defined with the cluster. Each node (earth & mars) has one oracle database defined as a package. Since the last time we had the cluster up and running, we have re-IPed and re-subnetted our network. I have change the ascii file for each of the oracle packages to reflect this change, so i'm confused as to where the old 132.10.0.0 subnet is defined. The error messages regarding the packages are as follows;
Error: Invalid subnet 132.10.0.0 in package ORACLE_lear
Error: Invalid subnet 132.10.0.0 in package ORACLE_lear

Our new subnet is 172.16.0.0 and as i said i have changed this in the config files.
Any suggestions on how to remedy these errors?