newly installed vxvm not seeing san attached disks?

[Doug O'Leary]

Hey;

I have a service call open w/symantec; however, they haven't responded yet.

I've just finished installed storage foundation ver 4.1, did the reboots, and installfs -configure w/o issues. I have 17 san attached EMC metas on the box that HP LVM can manipulate just fine yet vxvm doesn't see them at all:

# vxdctl enable
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c2t0d0 auto:LVM - - LVM
c2t1d0 auto:LVM - - LVM
[[ end ]]

Anyone have any ideas what might be causing this?

Thanks for any hints/tips/suggestions.

Doug O'Leary

[TTr]

Do you have the veritas ASL (Array Support Library) for EMC installed? Veritas needs the appropriate ASL for each disk array vendor and because it is different for each array vendor, it might not be part of the storage foundation.

[Armin Kunaschik]

First check the ASL, as described:
# vxddladm listsupport all

Use "vxdisk scandisks" not "vxdctl enable" (recommendation by Veritas).
In some rare cases it might help to restart vxconfigd.

My 2 cents,
Armin

[Doug O'Leary]

Hey;

Thanks for the responses. Unfortunately, neither of those appear to be the issue:

# vxddladm listsupport all | grep -i emc
libvxemc.sl EMC SYMMETRIX
# vxdisk scandisks
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c2t0d0 auto:LVM - - LVM
c2t1d0 auto:LVM - - LVM


Still only seeing the internal disks. This is wierd. I've installed vxvm dozens of times on HP systems; this is the only one that seems to have acted up on me. Hopefully symantec will come up with something soon.

Thanks.

Doug O'Leary

[TTr]

Do you have a separate ASL fileset installed for the EMC array?

I have all the libraries as well for all disk arrays and array manufacturers but I only have ONE a separate ASL fileset for my disk array.

Check with swlist for something like VRTSemc???

[Doug O'Leary]

Hey;

No; no separate library for the specific sym, but I don't have that anywhere else either. This box is working 100% perfectly:

$ ssh usildb24 swlist | grep -i vrts | awk '{print $1}'
PHCO_35892
PHCO_36113
PHKL_37393
VRTScpi
VRTSfsdoc
VRTSjre
VRTSperl
VRTSvcsvr
VRTSvlic
VRTSvrdoc
VRTSvrmcsg
VRTSvrpro
VRTSvrw
VRTSweb

I do seem to have a lot more vrts stuff installed on the box that's not working correctly though:

$ ssh usssap1 swlist | grep -i vrts | awk '{print $1}'
VRTSalloc
VRTSap
VRTScpi
VRTSddlpr
VRTSfsdoc
VRTSfsman
VRTSfspro
VRTSjre
VRTSperl
VRTStep
VRTSvcsvr
VRTSvmdoc
VRTSvmpro
VRTSvrdoc
VRTSvrmcsg
VRTSvrpro
VRTSvrw
VRTSvxfs
VRTSvxvm
VRTSweb

Plus those patches from the first group. I suspect a reinstall is in my near future. I'm a little concerned though, as the first time I uninstalled this, the filesystems on the san-attached lvm disk went away. Not something I'm anxious to redo.

Thanks for the info.

Doug

[TTr]

I have the "VRTSfast" specific fileset in my swlist. This is for the IBM FastT disk arrays. At this point I don't know if this add-on was needed because the ASL was not available in the core veritas software and it is the case with your library as well. What did symantec tech support say?

I also found these interesting links

ftp://exftpp.symantec.com/pub/support/products/VolumeManager_UNIX/274890.pdf

This one is for AIX but has an interesting workaround.

http://seer.entsupport.symantec.com/docs/296134.htm

Do you have the EMC powerpath installed? I have seen some documents regarding PP and DMP coexistence.

And last but not least take a look at this doc, SPECIALLY page 4
http://sfdoccentral.symantec.com/sf/4.1/hpux/pdf/vxvm_hwnotes.pdf

[Doug O'Leary]

Hey;

It looks like symantec is narrowing down on some patches that I need to install. Curious that I haven't installed these on other boxes and everything works, but, I just work here.

Thanks for the replies; I appreciate the help.

Doug O'Leary