Hi Thomas,

Just to let you know, a reboot has fixed everything.   They are online and 
ready for initialising:

# vxdisk list
FLEXLINE0_0  auto:none       -            -            online invalid
FLEXLINE0_1  auto:none       -            -            online invalid
FLEXLINE0_2  auto:none       -            -            online invalid
FLEXLINE0_3  auto:none       -            -            online invalid
FLEXLINE0_4  auto:none       -            -            online invalid

And they have 8 paths now instead of the 6, or 40, which is what I thought they 
should have had.

Thankx,

Greg.

-----Original Message-----
From: Thomas Cornely [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, 7 May 2008 3:52 PM
To: Robinson, Greg; veritas-vx@mailman.eng.auburn.edu
Subject: RE: [Veritas-vx] DMP seems confused 

Greg,

Oh boy. Can you try rebooting the host before calling support?
What may have happened is that the dmp database was screwed up when you ran 
without the ASL (the os devices <-> dmpnodes association were wrong). The 5.0 
MP1 code isn't good at untangling a messed up db, that's something we've been 
working on. So the vxdctl enable with the ASL just added to the confusion.

A reboot should allow the discovery to start from a clean slate.
If that doesn't work, your next option will indeed be support, with all my 
apologies.
Crossing my fingers...

Thomas

> -----Original Message-----
> From: Robinson, Greg [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, May 06, 2008 10:33 PM
> To: Thomas Cornely; veritas-vx@mailman.eng.auburn.edu
> Subject: RE: [Veritas-vx] DMP seems confused 
> 
> Hi Thomas,
> 
> Gidy as a school girl, I downloaded the ASL and installed it. 
>  Unfortunately, it has not solved my problem, much to my surprise:
> 
> Installation of <VRTSSTKasl> was successful.
> # vxdctl enable
> VxVM vxdctl ERROR V-5-1-1589 enable failed: Configuration 
> daemon is not accessible # # vxconfigd -k VxVM vxconfigd 
> ERROR V-5-1-0 Segmentation violation - core dumped # vxdisk 
> list VxVM vxdisk ERROR V-5-1-684 IPC failure: Configuration 
> daemon is not accessible # vxconfigd -k # # vxdisk list
> FLEXLINE0_0  auto:none       -            -            online invalid
> [Output truncated]
> #
> #
> # vxdisk list FLEXLINE0_0
> Device:    FLEXLINE0_0
> devicetag: FLEXLINE0_0
> type:      auto
> info:      format=none
> flags:     online ready private autoconfig invalid
> pubpaths:  block=/dev/vx/dmp/FLEXLINE0_0 char=/dev/vx/rdmp/FLEXLINE0_0
> guid:      -
> udid:      
> STK%5FFLEXLINE%5F600A0B80003315E800000000478FD13E%5F600A0B8000
3315E80000063B479FB8D0
> site:      -
> Multipathing information:
> numpaths:  40
> c2t202500A0B83315E8d3   state=enabled   type=secondary
> c2t202400A0B83315E8d3   state=enabled   type=primary
> c2t201400A0B83315E8d3   state=enabled   type=primary
> c2t201500A0B83315E8d3   state=enabled   type=secondary
> c4t202400A0B83315E8d3   state=enabled   type=primary
> c4t202500A0B83315E8d3   state=enabled   type=secondary
> c4t202500A0B83315E8d1   state=enabled   type=primary
> c4t202400A0B83315E8d1   state=enabled   type=secondary
> c2t201500A0B83315E8d1   state=enabled   type=primary
> c2t201400A0B83315E8d1   state=enabled   type=secondary
> c2t202400A0B83315E8d1   state=enabled   type=secondary
> c2t202500A0B83315E8d1   state=enabled   type=primary
> c4t202500A0B83315E8d2   state=enabled   type=secondary
> c4t202400A0B83315E8d2   state=enabled   type=primary
> c2t201500A0B83315E8d2   state=enabled   type=secondary
> c2t201400A0B83315E8d2   state=enabled   type=primary
> c2t202400A0B83315E8d2   state=enabled   type=primary
> c2t202500A0B83315E8d2   state=enabled   type=secondary
> c4t202400A0B83315E8d4   state=enabled   type=secondary
> c4t202500A0B83315E8d4   state=enabled   type=primary
> c2t201400A0B83315E8d4   state=enabled   type=secondary
> c2t201500A0B83315E8d4   state=enabled   type=primary
> c2t202400A0B83315E8d4   state=enabled   type=secondary
> c2t202500A0B83315E8d4   state=enabled   type=primary
> c4t202500A0B83315E8d0   state=enabled   type=primary
> c4t202400A0B83315E8d0   state=enabled   type=secondary
> c2t201500A0B83315E8d0   state=enabled   type=primary
> c2t201400A0B83315E8d0   state=enabled   type=secondary
> c2t202400A0B83315E8d0   state=enabled   type=secondary
> c2t202500A0B83315E8d0   state=enabled   type=primary
> c4t201500A0B83315E8d2   state=enabled   type=secondary
> c4t201500A0B83315E8d4   state=enabled   type=primary
> c4t201500A0B83315E8d3   state=enabled   type=secondary
> c4t201500A0B83315E8d0   state=enabled   type=primary
> c4t201500A0B83315E8d1   state=enabled   type=primary
> c4t201400A0B83315E8d4   state=enabled   type=secondary
> c4t201400A0B83315E8d0   state=enabled   type=secondary
> c4t201400A0B83315E8d1   state=enabled   type=secondary
> c4t201400A0B83315E8d2   state=enabled   type=primary
> c4t201400A0B83315E8d3   state=enabled   type=primary
> 
> 40 paths!?!?!?
> 
> # vxddladm listsupport libname=libstkasl.so
> ATTR_NAME            ATTR_VALUE                               
>                    
> ==============================================================
> =========
> LIBNAME              libstkasl.so                             
>                     
> VID                  STK                                      
>                     
> PID                  OPENstorage, BladeCtlr, FLEXLINE         
>                     
> ARRAY_TYPE           A/P-C                                    
>                     
> ARRAY_NAME           STK_ARRAY, STK_ARRAY, FLEXLINE
> 
> I think this maybe causing the issue:
> # /etc/vx/diag.d/vxdmpinq /dev/rdsk/c4t201400A0B83315E8d3
> 
> Inquiry for /dev/rdsk/c4t201400A0B83315E8d3, evpd 0x0, page code 0x0
>         Vendor id                        : STK     
>         Product id                       : FLEXLINE 380    
>         Revision                         : 0619
>         Serial Number                    :  3è  ;G¸Ð
> 
> Whereby the serial number is nonsensical.
> 
> What do you think?  Open a support case?
> 
> Thankx,
> 
> Greg.
> 
> -----Original Message-----
> From: Thomas Cornely [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 7 May 2008 1:25 PM
> To: Robinson, Greg; veritas-vx@mailman.eng.auburn.edu
> Subject: RE: [Veritas-vx] DMP seems confused
> 
> Hi Greg,
> 
> SF 5.0 does support the 6540, but you need to add the 
> applicable the array support library (ASL). From your 
> screenshots, it would appear that your system is missing the 
> ASL for the 6540. That can lead to improper device claiming. 
> As you note, in 5.0 most ASL/APMs are included in the base 
> vxvm packages. For arrays for which support was added after 
> 5.0 MP1 shipped however the ASL/APM have to be downloaded separately.
> 
> You can find the SF 5.0 Hardware Compatibility List at:
> http://seer.entsupport.symantec.com/docs/283161.htm
> 
> In there, under Solaris, Sun 6540 has a note pointing to 
> where you can download the array specific ASL:
> http://seer.entsupport.symantec.com/docs/289809.htm
> 
> This should straighten things out.
> Thanks,
> 
> Thomas
> DMP PM
> 
> 
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of 
> > Robinson, Greg
> > Sent: Tuesday, May 06, 2008 7:25 PM
> > To: veritas-vx@mailman.eng.auburn.edu
> > Subject: [Veritas-vx] DMP seems confused
> > 
> > Hi all,
> > 
> > Got a strange one here.  I have a E2900, Solaris 10, recent 
> patches, 
> > with VxVM 5.0 + mp1.
> > 
> > We have a Sun 6540 (Flexline 380) zoned to it over the SAN.  
> > There is only 1 switch in use.  4 ports on the array are zoned to 2 
> > HBA's on the server, with a 3rd dedicated to tape.
> > 
> > # vxdisk list
> > DEVICE       TYPE            DISK         GROUP        STATUS
> > Disk_0       auto:sliced     rootdg01     rootdg       online
> > Disk_1       auto:none       -            -            
> online invalid
> > Disk_2       auto:none       -            -            
> online invalid
> > Disk_2       auto:none       -            -            
> online invalid
> > Disk_4       auto:none       -            -            
> online invalid
> > Disk_5       auto:none       -            -            
> online invalid
> > Disk_6       auto:none       -            -            
> online invalid
> > Disk_7       auto:none       -            -            
> online invalid
> > Disk_8       auto:none       -            -            
> online invalid
> > Disk_9       auto:none       -            -            
> online invalid
> > Disk_10      auto:none       -            -            
> online invalid
> > 
> > The root disk is currently not mirrored, as it was upgraded from 
> > solaris 9, and the 6540 is a new array.
> > 
> > There are 6 paths to all disks, except for 9 and 10.
> > 
> > Eg:  # vxdisk list Disk_6
> > Device:    Disk_6
> > devicetag: Disk_6
> > type:      auto
> > info:      format=none
> > flags:     online ready private autoconfig invalid
> > pubpaths:  block=/dev/vx/dmp/Disk_6 char=/dev/vx/rdmp/Disk_6
> > guid:      -
> > udid:
> > STK%5FFLEXLINE%20380%5FDISKS%5F600A0B80003308A40000062D479FB9CF
> > site:      -
> > Multipathing information:
> > numpaths:   6
> > c2t202500A0B83315E8d4   state=enabled
> > c2t202400A0B83315E8d4   state=enabled
> > c2t201500A0B83315E8d4   state=enabled
> > c2t201400A0B83315E8d4   state=enabled
> > c4t202500A0B83315E8d4   state=enabled
> > c4t202400A0B83315E8d4   state=enabled
> > 
> > However, Disk 9
> > # vxdisk list Disk_9
> > Device:    Disk_9
> > devicetag: Disk_9
> > type:      auto
> > info:      format=none
> > flags:     online ready private autoconfig invalid
> > pubpaths:  block=/dev/vx/dmp/Disk_9 char=/dev/vx/rdmp/Disk_9
> > guid:      -
> > udid:
> > STK%5FFLEXLINE%20380%5FDISKS%5F600A0B80003315E80000063B479FB8D0
> > site:      -
> > Multipathing information:
> > numpaths:   5
> > c4t201400A0B83315E8d3   state=enabled
> > c4t201400A0B83315E8d2   state=enabled
> > c4t201400A0B83315E8d1   state=enabled
> > c4t201400A0B83315E8d0   state=enabled
> > c4t201400A0B83315E8d4   state=enabled
> > 
> > Looks like Disk_9 has chosen all LUNs as a path to 1 LUN, which I 
> > don't understand.
> > 
> > Can anyone shed some light on this?  Both HBA's are non sun branded 
> > qlogic HBA's but appear to be using the Sun driver.
> > 
> > It does not appear that an ASL is installed, but I thought 
> 5.0 didn't 
> > need any.  Does 5.0 support the 6540?
> > 
> > Greg.
> > 
> > 
> > IMPORTANT: This email remains the property of the 
> Australian Defence 
> > Organisation and is subject to the jurisdiction of section 
> 70 of the 
> > CRIMES ACT 1914.  If you have received this email in error, you are 
> > requested to contact the sender and delete the email.
> > 
> > 
> > 
> > _______________________________________________
> > Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu 
> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
> > 
> 

_______________________________________________
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Reply via email to