Login or Register to Ask a Question and Join Our Community


Solaris

luxadm probe and vxdisk list don't matchup

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Solaris luxadm probe and vxdisk list don't matchup
# 1  
Old 08-11-2009
luxadm probe and vxdisk list don't matchup
I have a new SAN (Fujitsu Eternus 2000) and am trying to setup a veritas cluster on it, however veritas does not see all of the vluns I have exposed to the box. The OS does see them though. I have seen a lot of post about this, but it seems they are about people having just the opposite problem (seeing multiple disks). I only see two of the disks in vx but I see all nine in solaris.

I have nine volumes in a RAID1+0 group on the SAN.
There are two HBA ports, running to two different switches, that hit two interfaces on the SAN.

Im running Solaris10 and VCS5.0

Any idea what I am doing wrong ?

Code:
 luxadm probe
No Network Array enclosures found in /dev/es

Found Fibre Channel device(s):
  Node WWN:500000e0d0147b00  Device Type:Disk device
    Logical Path:/dev/rdsk/c2t500000E0D0147B86d0s2
    Logical Path:/dev/rdsk/c3t500000E0D0147B06d0s2
  Node WWN:500000e0d0147b00  Device Type:Disk device
    Logical Path:/dev/rdsk/c2t500000E0D0147B86d1s2
    Logical Path:/dev/rdsk/c3t500000E0D0147B06d1s2
  Node WWN:500000e0d0147b00  Device Type:Disk device
    Logical Path:/dev/rdsk/c2t500000E0D0147B86d2s2
    Logical Path:/dev/rdsk/c3t500000E0D0147B06d2s2
  Node WWN:500000e0d0147b00  Device Type:Disk device
    Logical Path:/dev/rdsk/c2t500000E0D0147B86d3s2
    Logical Path:/dev/rdsk/c3t500000E0D0147B06d3s2
  Node WWN:500000e0d0147b00  Device Type:Disk device
    Logical Path:/dev/rdsk/c2t500000E0D0147B86d4s2
    Logical Path:/dev/rdsk/c3t500000E0D0147B06d4s2
  Node WWN:500000e0d0147b00  Device Type:Disk device
    Logical Path:/dev/rdsk/c2t500000E0D0147B86d5s2
    Logical Path:/dev/rdsk/c3t500000E0D0147B06d5s2
  Node WWN:500000e0d0147b00  Device Type:Disk device
    Logical Path:/dev/rdsk/c2t500000E0D0147B86d6s2
    Logical Path:/dev/rdsk/c3t500000E0D0147B06d6s2
  Node WWN:500000e0d0147b00  Device Type:Disk device
    Logical Path:/dev/rdsk/c2t500000E0D0147B86d7s2
    Logical Path:/dev/rdsk/c3t500000E0D0147B06d7s2
  Node WWN:500000e0d0147b00  Device Type:Disk device
    Logical Path:/dev/rdsk/c2t500000E0D0147B86d8s2
    Logical Path:/dev/rdsk/c3t500000E0D0147B06d8s2
  Node WWN:500000e0d0147b00  Device Type:Disk device
    Logical Path:/dev/rdsk/c2t500000E0D0147B86d9s2
    Logical Path:/dev/rdsk/c3t500000E0D0147B06d9s2

vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c1t0d0s2     auto            -            -            error
c1t1d0s2     auto            -            -            error
c1t2d0s2     auto            -            -            error
c1t3d0s2     auto            -            -            error
c1t4d0s2     auto            -            -            error
c1t5d0s2     auto            -            -            error
c2t500000E0D0147B86d0s2 auto            -            -            error
c2t500000E0D0147B86d9s2 auto            -            -            error

 /etc/vx/diag.d/vxdmpinq /dev/rdsk/c2t500000E0D0147B86d0s2

Inquiry for /dev/rdsk/c2t500000E0D0147B86d0s2, evpd 0x0, page code 0x0
        Vendor id                        : FUJITSU 
        Product id                       : E2000           
        Revision                         : 0000
        Serial Number                    :   00147B0000
 /etc/vx/diag.d/vxdmpinq /dev/rdsk/c2t500000E0D0147B86d1s2

Inquiry for /dev/rdsk/c2t500000E0D0147B86d1s2, evpd 0x0, page code 0x0
        Vendor id                        : FUJITSU 
        Product id                       : E2000           
        Revision                         : 0000
        Serial Number                    :   00147B0001
/etc/vx/diag.d/vxdmpinq /dev/rdsk/c2t500000E0D0147B86d3s2

Inquiry for /dev/rdsk/c2t500000E0D0147B86d3s2, evpd 0x0, page code 0x0
        Vendor id                        : FUJITSU 
        Product id                       : E2000           
        Revision                         : 0000
        Serial Number                    :   00147B0003
/etc/vx/diag.d/vxdmpinq /dev/rdsk/c2t500000E0D0147B86d4s2

Inquiry for /dev/rdsk/c2t500000E0D0147B86d4s2, evpd 0x0, page code 0x0
        Vendor id                        : FUJITSU 
        Product id                       : E2000           
        Revision                         : 0000
        Serial Number                    :   00147B0004
..... didn't want to put all nine in .....
/etc/vx/diag.d/vxdmpinq /dev/rdsk/c2t500000E0D0147B86d9s2

Inquiry for /dev/rdsk/c2t500000E0D0147B86d9s2, evpd 0x0, page code 0x0
        Vendor id                        : FUJITSU 
        Product id                       : E2000           
        Revision                         : 0000
        Serial Number                    :   00147B0009

vxdmpadm getsubpaths ctlr=c2
NAME         STATE[A]   PATH-TYPE[M] DMPNODENAME  ENCLR-TYPE   ENCLR-NAME   ATTRS
================================================================================
c2t500000E0D0147B86d0s2 ENABLED(A)   -          c2t500000E0D0147B86d0s2 FJ_E2000     FJ_E20000      -
c2t500000E0D0147B86d1s2 ENABLED(A)   -          c2t500000E0D0147B86d9s2 FJ_E2000     FJ_E20000      -
c2t500000E0D0147B86d2s2 ENABLED(A)   -          c2t500000E0D0147B86d9s2 FJ_E2000     FJ_E20000      -
c2t500000E0D0147B86d3s2 ENABLED(A)   -          c2t500000E0D0147B86d9s2 FJ_E2000     FJ_E20000      -
c2t500000E0D0147B86d4s2 ENABLED(A)   -          c2t500000E0D0147B86d9s2 FJ_E2000     FJ_E20000      -
c2t500000E0D0147B86d5s2 ENABLED(A)   -          c2t500000E0D0147B86d9s2 FJ_E2000     FJ_E20000      -
c2t500000E0D0147B86d6s2 ENABLED(A)   -          c2t500000E0D0147B86d9s2 FJ_E2000     FJ_E20000      -
c2t500000E0D0147B86d7s2 ENABLED(A)   -          c2t500000E0D0147B86d9s2 FJ_E2000     FJ_E20000      -
c2t500000E0D0147B86d8s2 ENABLED(A)   -          c2t500000E0D0147B86d9s2 FJ_E2000     FJ_E20000      -
c2t500000E0D0147B86d9s2 ENABLED(A)   -          c2t500000E0D0147B86d9s2 FJ_E2000     FJ_E20000      -



---------- Post updated at 03:10 PM ---------- Previous update was at 11:50 AM ----------

So it looks like all I was missing was a good old reboot.

I had previously loaded the ASL for the Eternus2000 (see Symantec Enabled Arrays - Array Support Library for Fujitsu ETERNUS DX60/DX80 and ETERNUS2000 Arrays (Active/Active) on Veritas Volume Manager (tm) 5.0 and 5.0MPx for Solaris (sparc) )

For the storage to be mapped properly, I had to reboot and start from a clean slate. (Thanks to Thomas Connerly @ symantec and his reply to an older post Gmane Loom )

Now, my disks are showing up properly:

Code:
 vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c1t0d0s2     auto:none       -            -            online invalid
c1t1d0s2     auto:none       -            -            online invalid
c1t2d0s2     auto            -            -            error
c1t3d0s2     auto            -            -            error
c1t4d0s2     auto:none       -            -            online invalid
c1t5d0s2     auto:none       -            -            online invalid
c2t500000E0D0147B86d0s2 auto:none       -            -            online invalid
c2t500000E0D0147B86d9s2 auto:none       -            -            online invalid
c3t500000E0D0147B06d1s2 auto:none       -            -            online invalid
c3t500000E0D0147B06d2s2 auto:none       -            -            online invalid
c3t500000E0D0147B06d3s2 auto:none       -            -            online invalid
c3t500000E0D0147B06d4s2 auto:none       -            -            online invalid
c3t500000E0D0147B06d5s2 auto:none       -            -            online invalid
c3t500000E0D0147B06d6s2 auto:none       -            -            online invalid
c3t500000E0D0147B06d7s2 auto:none       -            -            online invalid
c3t500000E0D0147B06d8s2 auto:none       -            -            online invalid

Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

Luxadm display not showing a LUN as expected

Hi all, I have the following LUN which is showing OK with its two paths: DEVICE PROPERTIES for disk: /dev/rdsk/c23t500507630A3BC579d123s2 Vendor: IBM Product ID: 2107900 Revision: 3010 Serial Num: 75WB0114900 Unformatted capacity:... (13 Replies)
Discussion started by: ludiegu
13 Replies

2. Solaris

Issue with luxadm?

Hello, I have Solaris 10 running on one of rack server with dual port FC card. Each port of FC card is connected to two switches respectively. I have been trying to test multipathing functionality with one of FC Storage. While I have two storage controllers , each connected to the two switches... (2 Replies)
Discussion started by: linuxfreaker
2 Replies

3. Solaris

Luxadm displaying incorrect LUN parameter...

Hello, I have Solaris 10 running on one of rack server with dual port FC card. Each port of FC card is connected to two switches respectively. I have been trying to test multipathing functionality with one of FC Storage. While I have two storage controllers , each connected to the two switches... (0 Replies)
Discussion started by: linuxfreaker
0 Replies

4. Solaris

SAN/Solaris: luxadm shows NOT CONNECTED

Hi, I have a question regarding HBA configuration. Here are the commands' output: # cfgadm -al | grep fc c1 fc-fabric connected unconfigured unknown c2 fc connected unconfigured unknown c5 ... (11 Replies)
Discussion started by: aixlover
11 Replies

5. Solaris

Non-Root mode ... luxadm to show path(s) for Disks

Hi Gurus out there... I am pondering over a situation where I have non-root access (user account), where I am trying to determine paths (including multipaths) on a host. "luxadm display" seems very appropriate, but requires root access. Is there anyway I can get the FC path information? ... (1 Reply)
Discussion started by: verisund
1 Replies

6. Filesystems, Disks and Memory

vxdisk list output showing extra LUNs

hi fren i am facing this problem i have sun 6140 storage 30 volumes bt my vxdisk list output is showing 37 disk which shd nt b there has neone faced this proble earlier vxdiks list output is like this SUN6140-2_0 auto - - online c4t201700A0B84853C0d2s2 SUN6140-2_1 auto - - online... (13 Replies)
Discussion started by: bond_ankur
13 Replies

7. High Performance Computing

What does the 'probe' do in VCS?

Weird question I know, but I'm intrigued. Say for instance you have an Application in an SG with the usual start/stop/monitor. To successfully probe does it just check for existence of the script/file ? Thanks... (1 Reply)
Discussion started by: itsupplies
1 Replies

8. Solaris

Help probe-scsi-all

I have run init 0 to bring it to OK prompt. I know that probe-scsi-all can hang the system. I want to know what is the difference between probe-scsi-all and probe-scsi. I was told that probe-scsi-all external and internal devices and probe-scsi shows only internal devices. what dose this ... (3 Replies)
Discussion started by: nitinkgoud
3 Replies

9. UNIX for Dummies Questions & Answers

probe software

can anyone point me towards a program to list what's installed on my sunOS box and their version numbers. (2 Replies)
Discussion started by: sphiengollie
2 Replies
Login or Register to Ask a Question