Error visible in diskgroup in VEA but not on commandline.
Goodmorning,
I have a strange error/issue within VEA. Customer is running solaris 10 upd 3 and storage foundation 5.0 mp1. Solaris machines (v490's) are clustered with symantec. (not sun cluster).
Customer has luns mapped from an EVA machine and also had some luns from a Netapp machine. The latter was not supported yet so they unmapped these netapp luns. Now it seems that something is left over and I cannot see how to get rid of it. The output from vxprint -ht is correct however, in the GUI, the diskgroup shows up with an exclamation (!) mark and an errorcross.
A subdisk was relocated but I don't understand why it is showing this as an error.
Output from vxprint:
root@lwsi131 # vxprint -htv
Disk group: ngio_dg
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE
SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCO
EX NAME ASSOC VC PERMS MODE STATE
v baskets_vol - ENABLED ACTIVE 31354880 SELECT - fsgen
pl baskets_vol-01 baskets_vol ENABLED ACTIVE 31354880 CONCAT - RW
sd ngio_dg02-05 baskets_vol-01 ngio_dg02 73400320 31354880 0 fabric_2 ENA
pl baskets_vol-02 baskets_vol ENABLED ACTIVE 31354880 CONCAT - RW
sd ngio_dg03-01 baskets_vol-02 ngio_dg03 0 31354880 0 fabric_11 ENA
pl baskets_vol-03 baskets_vol ENABLED ACTIVE 31354880 CONCAT - RW
sd ngio_dg01-05 baskets_vol-03 ngio_dg01 73400320 31354880 0 fabric_4 ENA
pl baskets_vol-05 baskets_vol ENABLED ACTIVE LOGONLY CONCAT - RW
sd ngio_dg01-06 baskets_vol-05 ngio_dg01 104755200 528 LOG fabric_4 ENA
The ngio_dg01-06 was connected to fabric_17 however, fabric17 was removed. See pictures:
Please advise,
Regards
Remco
Your screenshots are too small to see properly.
Early versions of SF 5.0 had various VEA bugs.I remember looging a call with Symantec about 4 years ago about descrepancies between cmd and VEA. It was resolved in a newly released patch (4 years ago).
Just checked - it was SF5.0 MP3 RP2.Please upgrade to 5.0 MP3 followed by RP5.
Best to upgrade to version 6.0 - EOSL for version 5.0 is less than a year away: https://sort.symantec.com/eosl/show_matrix