HP Tachyon FC card and issues...

[Coolmar]

I have an hp 11.11 system attached to an IBM Shark SAN. When I reboot the server it complains right away about the alternate path when it is activating the volume groups. However, it is able to activate them and everything is fine. I physically unplugged the primary and it failed over (after a long delay of around 1 minute) and all was still fine. However, a couple of other servers don't get the error at all on bootup. The patch levels are all the same on all systems. So the only difference seems to be the Tachyon card. The systems that work have an HP Tachyon TL/TS and the one that gives that error has an HP Tachyon XL2. The Tachyon drivers are patched up to the latest on all. What is the difference between these cards? Could this be the problem? Like I said, the systems all work fine but I just don't like this error on bootup and would prefer to find a solution so I can get rid of it. Thanks.

Error:

/sbin/bcheckrc:
Checking for LVM volume groups and Activating (if any exist)
Volume group "/dev/vg00" has been successfully changed.
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c38t0d0":
The path of the physical volume refers to a device that does not
exist, or is not configured into the kernel.
vgchange: The path of the physical volume refers to a device that does not
exist, or is not configured into the kernel.
Activated volume group
Volume group "/dev/vg01" has been successfully changed.
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c38t0d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c38t0d1":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
Resynchronized volume group /dev/vg00
vxfs fsck: sanity check: root file system OK (mounted read/write)
Resynchronized volume group /dev/vg01
Checking hfs file systems
/sbin/fsclean: /dev/vg00/lvol1 (mounted) ok
HFS file systems are OK, not running fsck
Checking vxfs file systems
/dev/vg00/lvol8 :
vxfs fsck: sanity check: /dev/vg00/lvol8 OK
/dev/vg00/lvol9 :
vxfs fsck: sanity check: /dev/vg00/lvol9 OK
/dev/vg00/lvol10 :
vxfs fsck: sanity check: /dev/vg00/lvol10 OK
/dev/vg01/lvol1 :
vxfs fsck: sanity check: /dev/vg01/lvol1 OK
/dev/vg01/lvol2 :
vxfs fsck: sanity check: /dev/vg01/lvol2 OK
/dev/vg00/lvol3 :
vxfs fsck: sanity check: root file system OK (mounted read/write)
/dev/vg00/lvol4 :
vxfs fsck: sanity check: /dev/vg00/lvol4 OK
/dev/vg00/lvol5 :
vxfs fsck: sanity check: /dev/vg00/lvol5 OK
/dev/vg00/lvol6 :
vxfs fsck: sanity check: /dev/vg00/lvol6 OK
/dev/vg00/lvol7 :
vxfs fsck: sanity check: /dev/vg00/lvol7 OK

As you can see it continues right through and seems to be fine. The paths that it is complaining about are the alternate paths.

[Sandman!]

Could you attach (not post, preferably) the output of the following:

# ioscan -funC disk
# ioscan -funC fc
# ioscan -funC fcp
# vgdisplay -v vg01

thanks

[sathish kannan]

Hello Sally,

I believe IBM Shark is Active/Active array and not active/passive array. As you said it's happening in the passive path, what's its path to Storage? Does both your Primary and alternate going through the same switch or different switch?. Along with host diagnostics also check your switch logs and any special setting for Storage relating to HP Host.


Regards
Sathish