topic Re: many errors were raised, when i run cmgetconf in Operating System - HP-UX

many errors were raised, when i run cmgetconf

stelecom — Wed, 19 Oct 2005 03:08:58 GMT

Please help me to resolve this problems.

Many thanks,
Vu

Warning: The disk at /dev/dsk/c0t4d0 on node COVIS1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c3t2d5 on node COVIS1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c5t2d5 on node COVIS1 does not have an ID, or a disk label.
Warning: The disk at /dev/dsk/c0t3d0 on node COVIS2 does not have an ID, or a disk label.
Warning: Disks which do not have IDs cannot be included in the topology description.
Use pvcreate(1M) to initialize a disk for LVM or,
use vxdiskadm(1M) to initialize a disk for VxVM.
Warning: Volume group /dev/vg02 is configured differently on node COVIS1 than on node COVIS2
Error: Volume group /dev/vg02 on node COVIS2 does not appear to have a physical volume corresponding to /dev/dsk/c3t1d7 on node COVIS1 (16573993861119725528).
Error: Volume group /dev/vg02 on node COVIS2 does not appear to have a physical volume corresponding to /dev/dsk/c5t1d7 on node COVIS1 (16573993861119725528).
Warning: Volume group /dev/vg02 is configured differently on node COVIS2 than on node COVIS1
Warning: Volume group /dev/vg04 is configured differently on node COVIS1 than on node COVIS2
Error: Volume group /dev/vg04 on node COVIS2 does not appear to have a physical volume corresponding to /dev/dsk/c3t2d0 on node COVIS1 (16573993861119725606).
Error: Volume group /dev/vg04 on node COVIS2 does not appear to have a physical volume corresponding to /dev/dsk/c5t2d0 on node COVIS1 (16573993861119725606).
Warning: Volume group /dev/vg04 is configured differently on node COVIS2 than on node COVIS1
Warning: Volume group /dev/vg01 is configured differently on node COVIS1 than on node COVIS2
Warning: Volume group /dev/vg01 is configured differently on node COVIS2 than on node COVIS1
Error: Volume group /dev/vg01 on node COVIS1 does not appear to have a physical volume corresponding to /dev/dsk/c3t2d1 on node COVIS2 (16563993861119728738).
Error: Volume group /dev/vg01 on node COVIS1 does not appear to have a physical volume corresponding to /dev/dsk/c3t2d2 on node COVIS2 (16563993861119728752).
Error: Volume group /dev/vg01 on node COVIS1 does not appear to have a physical volume corresponding to /dev/dsk/c5t2d1 on node COVIS2 (16563993861119728738).
Error: Volume group /dev/vg01 on node COVIS1 does not appear to have a physical volume corresponding to /dev/dsk/c5t2d2 on node COVIS2 (16563993861119728752).
Warning: The volume group /dev/vg01 is activated on more than one node:
COVIS1
COVIS2
Warning: Volume group /dev/vg03 is configured differently on node COVIS1 than on node COVIS2
Warning: Volume group /dev/vg03 is configured differently on node COVIS2 than on node COVIS1
Error: Volume group /dev/vg03 on node COVIS1 does not appear to have a physical volume corresponding to /dev/dsk/c3t2d3 on node COVIS2 (16563993861119728768).
Error: Volume group /dev/vg03 on node COVIS1 does not appear to have a physical volume corresponding to /dev/dsk/c3t2d4 on node COVIS2 (16563993861119728781).
Error: Volume group /dev/vg03 on node COVIS1 does not appear to have a physical volume corresponding to /dev/dsk/c5t2d3 on node COVIS2 (16563993861119728768).
Error: Volume group /dev/vg03 on node COVIS1 does not appear to have a physical volume corresponding to /dev/dsk/c5t2d4 on node COVIS2 (16563993861119728781).
Warning: Volume groups should not be activated on more than one node.
Use vgchange to de-activate a volume group on a node.

Re: many errors were raised, when i run cmgetconf

melvyn burnard — Wed, 19 Oct 2005 03:13:57 GMT

As it tells you:

The volume group /dev/vg01 is activated on more than one node:
COVIS1
COVIS2

This is not allowed
==

Warning: Volume group /dev/vg01 is configured differently on node COVIS2 than on node COVIS1
Warning: Volume group /dev/vg02 is configured differently on node COVIS2 than on node COVIS1
Warning: Volume group /dev/vg04 is configured differently on node COVIS1 than on node COVIS2

They should be configured the same on both nodes if they are to be shared

===

Error: Volume group /dev/vg01 on node COVIS1 does not appear to have a physical volume corresponding to /dev/dsk/c3t2d2 on node COVIS2 (16563993861119728752).
Error: Volume group /dev/vg01 on node COVIS1 does not appear to have a physical volume corresponding to /dev/dsk/c5t2d1 on node COVIS2 (16563993861119728738).

Well it is telling you that the node cannot see discs that shoul dbelong ibn the VG.

TO summarise, make sure both nodes can see all the discs, make sure you create the VG's identically, and make sure that any shared VG is active on only one node at a time

Fix your LVM configuration

Re: many errors were raised, when i run cmgetconf

AwadheshPandey — Wed, 19 Oct 2005 03:22:57 GMT

this is the issue of lvm configuration only. lvm not configured properly on ur m/c.

Awadhesh

Re: many errors were raised, when i run cmgetconf

Jayasuntar — Wed, 19 Oct 2005 03:42:30 GMT

Hi,

I think U have assymmetric cluster config.

There is a problrm vgconfgiration itself.

Please give me lvmtab from both the system.

And give the group file details for the vg from both the system.

Regards

Jay

Re: many errors were raised, when i run cmgetconf

stelecom — Wed, 19 Oct 2005 04:22:41 GMT

This is content of 2 files lvmtab

NODE1:

^CÃ¨
/dev/vg00bÃ Ã¨Z=Â¥Ã®^P^B/dev/dsk/c1t6d0/dev/dsk/c2t6d0/dev/vg02bÃ Ã¨Z=Â§^GF^F/dev/dsk/c3t0d1/dev
/dsk/c5t0d1/dev/dsk/c3t1d2/dev/dsk/c5t1d2/dev/dsk/c3t1d7/dev/dsk/c5t1d7/dev/vglockbÃ Ã¨Z=Â§^
GÂ¢^B/dev/dsk/c3t0d0/dev/dsk/c5t0d0/dev/vg04bÃ Ã¨Z=Â§^H^L^F/dev/dsk/c3t0d2/dev/dsk/c5t0d2/dev
/dsk/c3t1d3/dev/dsk/c5t1d3/dev/dsk/c3t2d0/dev/dsk/c5t2d0/dev/vg06bÃ Ã¨Z=Â§^HY^D/dev/dsk/c3t0
d3/dev/dsk/c5t0d3/dev/dsk/c3t1d4/dev/dsk/c5t1d4/dev/vg08bÃ Ã¨Z=Â§^HÂ ^B/dev/dsk/c3t0d4/dev/ds
k/c5t0d4/dev/vg05bÂºÂ¦^Z=Â§^K5^B/dev/dsk/c3t0d7/dev/dsk/c5t0d7/dev/vg07bÂºÂ¦^Z=Â§^Kk^B/dev/dsk/
c3t1d0/dev/dsk/c5t1d0/dev/vg01bÂºÂ¦^Z=Â§
V^F/dev/dsk/c3t0d5/dev/dsk/c3t1d1/dev/dsk/c3t1d5/dev/dsk/c5t0d5/dev/dsk/c5t1d1/dev/dsk/c5
t1d5/dev/vg03bÂºÂ¦^Z=Â§
Ã ^D/dev/dsk/c3t0d6/dev/dsk/c3t1d6/dev/dsk/c5t0d6/dev/dsk/c5t1d6

NODE2:

^CÃ¨
/dev/vg00bÂºÂ¦^Z=Â¥ÃªÂ^B/dev/dsk/c1t6d0/dev/dsk/c2t6d0/dev/vg01bÂºÂ¦^Z=Â§
V
/dev/dsk/c3t0d5/dev/dsk/c5t0d5/dev/dsk/c3t1d1/dev/dsk/c5t1d1/dev/dsk/c3t1d5/dev/dsk/c5t1d5/dev/dsk/c3t2d1/dev/dsk/c3t2d2/dev/dsk/c5t
2d1/dev/dsk/c5t2d2/dev/vg03bÂºÂ¦^Z=Â§
Ã ^H/dev/dsk/c3t0d6/dev/dsk/c5t0d6/dev/dsk/c3t1d6/dev/dsk/c5t1d6/dev/dsk/c3t2d3/dev/dsk/c3t2d4/dev/dsk/c5t2d3/dev/dsk/c5t2d4/dev/vg05
bÂºÂ¦^Z=Â§^K5^B/dev/dsk/c3t0d7/dev/dsk/c5t0d7/dev/vg07bÂºÂ¦^Z=Â§^Kk^B/dev/dsk/c3t1d0/dev/dsk/c5t1d0/dev/vglockbÃ Ã¨Z=Â§^GÂ¢^B/dev/dsk/c3t0d0/d
ev/dsk/c5t0d0/dev/vg08bÃ Ã¨Z=Â§^HÂ ^B/dev/dsk/c3t0d4/dev/dsk/c5t0d4/dev/vg02bÃ Ã¨Z=Â§^GF^D/dev/dsk/c3t0d1/dev/dsk/c3t1d2/dev/dsk/c5t0d1/dev
/dsk/c5t1d2/dev/vg04bÃ Ã¨Z=Â§^H^L^D/dev/dsk/c3t0d2/dev/dsk/c3t1d3/dev/dsk/c5t0d2/dev/dsk/c5t1d3/dev/vg06bÃ Ã¨Z=Â§^HY^D/dev/dsk/c3t0d3/dev/
dsk/c3t1d4/dev/dsk/c5t0d3/dev/dsk/c5t1d4

Re: many errors were raised, when i run cmgetconf

melvyn burnard — Wed, 19 Oct 2005 04:33:19 GMT

What you have supplied is almost unreadable, I would suggest putting it in as an attachment.
I would also suggest you list what VG's SHOULD be shared, and (if any) what should NOT be shared.
Also provide output of:
ll /dev/vg*

Re: many errors were raised, when i run cmgetconf

stelecom — Wed, 19 Oct 2005 04:41:00 GMT

Please see my attachment file.

Re: many errors were raised, when i run cmgetconf

melvyn burnard — Wed, 19 Oct 2005 05:01:16 GMT

Well on node 1 you have vg01 and vg02 with the same minor numbers, as well as vg03 and vglock
You need to fix this first