Solaris 10 6/06 (x86), StorEdge A5200, and unable to see SES enclosure using luxadm

From: Sam.Storie@EmersonProcess.com
Date: Tue Apr 17 2007 - 10:40:54 EDT


Sun Managers,

I have a Sun X4600 server with a dual-hba QLogic QLA2462 fibre-channel
card connected to both ports on the "B" interface board in a StorEdge
A5200 array. There is a sparc Solaris 9 server connected to both ports
of the "A" IB, and it has no issues like I'm about to describe.

I am using Solaris 10 6/06 and am having some issues getting the "luxadm
display <Enclosure>" command to see my SES enclosure. I have no problem
seeing the actual disks, but without the luxadm commands I'm used to
it's hard to see where the drives are physically in the array (as well
as other status info). Here's the output of the relevant commands:

# fcinfo hba-port
HBA Port WWN: 210000e08b90e91c
        OS Device Name: /dev/cfg/c4
        Manufacturer: QLogic Corp.
        Model: QLA2462
        Type: L-port
        State: online
        Supported Speeds: 1Gb 2Gb 4Gb
        Current Speed: 1Gb
        Node WWN: 200000e08b90e91c
HBA Port WWN: 210100e08bb0e91c
        OS Device Name: /dev/cfg/c5
        Manufacturer: QLogic Corp.
        Model: QLA2462
        Type: L-port
        State: online
        Supported Speeds: 1Gb 2Gb 4Gb
        Current Speed: 1Gb
        Node WWN: 200100e08bb0e91c

...and I can see all the disks and the enclosure, but the enclosure is
not configured correctly and appears to be in a failed condition...

# cfgadm -al
Ap_Id Type Receptacle Occupant
Condition
c4 fc-private connected configured
unknown
c4::210100e08bb0e91c unknown connected unconfigured
unknown
c4::22000004cfe02deb disk connected configured
unknown
c4::22000004cfe02e14 disk connected configured
unknown
c4::22000004cfe02e16 disk connected configured
unknown
c4::22000004cfe02e9e disk connected configured
unknown
c4::22000004cfe02eaa disk connected configured
unknown
c4::22000004cfe02eaf disk connected configured
unknown
c4::22000004cfe03039 disk connected configured
unknown
c4::22000004cfe03319 disk connected configured
unknown
c4::22000004cfe03328 disk connected configured
unknown
c4::22000004cfe0332a disk connected configured
unknown
c4::22000004cfe0355c disk connected configured
unknown
c4::22000004cfe03792 disk connected configured
unknown
c4::22000011c62a0e81 disk connected configured
unknown
c4::22000011c62a1032 disk connected configured
unknown
c4::22000011c62a1033 disk connected configured
unknown
c4::22000011c62a1035 disk connected configured
unknown
c4::22000011c62a10a3 disk connected configured
unknown
c4::22000011c62a1673 disk connected configured
unknown
c4::22000011c62a1680 disk connected configured
unknown
c4::22000011c62a16ad disk connected configured
unknown
c4::22000011c62a1702 disk connected configured
unknown
c4::22000011c62a1707 disk connected configured
unknown
c4::50800200000e56eb unavailable connected unconfigured
failed <-- SES enclosure
c4::50800200000e56ec unavailable connected unconfigured
failed <-- SES enclosure
c5 fc-private connected configured
unknown
c5::210000e08b90e91c unknown connected unconfigured
unknown
c5::22000004cfe02deb disk connected configured
unknown
c5::22000004cfe02e14 disk connected configured
unknown
c5::22000004cfe02e16 disk connected configured
unknown
c5::22000004cfe02e9e disk connected configured
unknown
c5::22000004cfe02eaa disk connected configured
unknown
c5::22000004cfe02eaf disk connected configured
unknown
c5::22000004cfe03039 disk connected configured
unknown
c5::22000004cfe03319 disk connected configured
unknown
c5::22000004cfe03328 disk connected configured
unknown
c5::22000004cfe0332a disk connected configured
unknown
c5::22000004cfe0355c disk connected configured
unknown
c5::22000004cfe03792 disk connected configured
unknown
c5::22000011c62a0e81 disk connected configured
unknown
c5::22000011c62a1032 disk connected configured
unknown
c5::22000011c62a1033 disk connected configured
unknown
c5::22000011c62a1035 disk connected configured
unknown
c5::22000011c62a10a3 disk connected configured
unknown
c5::22000011c62a1673 disk connected configured
unknown
c5::22000011c62a1680 disk connected configured
unknown
c5::22000011c62a16ad disk connected configured
unknown
c5::22000011c62a1702 disk connected configured
unknown
c5::22000011c62a1707 disk connected configured
unknown
c5::50800200000e56eb unavailable connected unconfigured
failed <-- SES enclosure
c5::50800200000e56ec unavailable connected unconfigured
failed <-- SES enclosure

...if I examine the c4 device using the show_FCP_dev option the status
of the SES device changes to unknown (not sure why)...

# cfgadm -alo show_FCP_dev c4
Ap_Id Type Receptacle Occupant
Condition
c4 fc-private connected configured
unknown
c4::210100e08bb0e91c unknown connected unconfigured
unknown
c4::22000004cfe02deb,0 disk connected configured
unknown
c4::22000004cfe02e14,0 disk connected configured
unknown
c4::22000004cfe02e16,0 disk connected configured
unknown
c4::22000004cfe02e9e,0 disk connected configured
unknown
c4::22000004cfe02eaa,0 disk connected configured
unknown
c4::22000004cfe02eaf,0 disk connected configured
unknown
c4::22000004cfe03039,0 disk connected configured
unknown
c4::22000004cfe03319,0 disk connected configured
unknown
c4::22000004cfe03328,0 disk connected configured
unknown
c4::22000004cfe0332a,0 disk connected configured
unknown
c4::22000004cfe0355c,0 disk connected configured
unknown
c4::22000004cfe03792,0 disk connected configured
unknown
c4::22000011c62a0e81,0 disk connected configured
unknown
c4::22000011c62a1032,0 disk connected configured
unknown
c4::22000011c62a1033,0 disk connected configured
unknown
c4::22000011c62a1035,0 disk connected configured
unknown
c4::22000011c62a10a3,0 disk connected configured
unknown
c4::22000011c62a1673,0 disk connected configured
unknown
c4::22000011c62a1680,0 disk connected configured
unknown
c4::22000011c62a16ad,0 disk connected configured
unknown
c4::22000011c62a1702,0 disk connected configured
unknown
c4::22000011c62a1707,0 disk connected configured
unknown
c4::50800200000e56eb ESI connected unconfigured
unknown
c4::50800200000e56ec ESI connected unconfigured
unknown

...now if we try to probe the array using luxadm we don't see any
enclosure information, but rather the disks themselves...

# luxadm probe

Found Fibre Channel device(s):
  Node WWN:20000004cfe02e14 Device Type:Disk device
    Logical Path:/dev/rdsk/c6t20000004CFE02E14d0s2
  Node WWN:20000004cfe02e16 Device Type:Disk device
    Logical Path:/dev/rdsk/c6t20000004CFE02E16d0s2
  Node WWN:20000004cfe03792 Device Type:Disk device
    Logical Path:/dev/rdsk/c6t20000004CFE03792d0s2
<snip>

...grab the port information so we can get a dump_map...

# luxadm -e port
/devices/pci@0,0/pci1022,7458@11/pci1077,141@2/fp@0,0:devctl
CONNECTED
/devices/pci@0,0/pci1022,7458@11/pci1077,141@2,1/fp@0,0:devctl
CONNECTED

...and here we can see how the SES enclosures are not recognized. From
the solaris 9 server attached to the same array the two lines marked end
with "0xd (SES device)"...

# luxadm -e dump_map
/devices/pci@0,0/pci1022,7458@11/pci1077,141@2/fp@0,0:devctl
Pos Port_ID Hard_Addr Port WWN Node WWN Type
0 88 0 22000011c62a1707 20000011c62a1707 0x0 (Disk
device)
1 ab 0 22000004cfe03319 20000004cfe03319 0x0 (Disk
device)
2 ad 0 22000004cfe02e9e 20000004cfe02e9e 0x0 (Disk
device)
3 9e 0 50800200000e56eb 50800200000e56e8 0x1f (Unknown
Type) <-- SES Enclosure not recognized
4 75 0 50800200000e56ec 50800200000e56e8 0x1f (Unknown
Type) <-- SES Enclosure not recognized
5 2 0 210100e08bb0e91c 200100e08bb0e91c 0x1f (Unknown
Type)
6 7c 0 22000011c62a1032 20000011c62a1032 0x0 (Disk
device)
7 7a 0 22000011c62a1033 20000011c62a1033 0x0 (Disk
device)
8 80 0 22000011c62a16ad 20000011c62a16ad 0x0 (Disk
device)
9 b2 0 22000004cfe0355c 20000004cfe0355c 0x0 (Disk
device)
10 97 0 22000011c62a1035 20000011c62a1035 0x0 (Disk
device)
11 81 0 22000011c62a1673 20000011c62a1673 0x0 (Disk
device)
12 8f 0 22000004cfe02eaa 20000004cfe02eaa 0x0 (Disk
device)
13 a9 0 22000004cfe02deb 20000004cfe02deb 0x0 (Disk
device)
14 aa 0 22000004cfe03328 20000004cfe03328 0x0 (Disk
device)
15 98 0 22000011c62a0e81 20000011c62a0e81 0x0 (Disk
device)
16 a7 0 22000004cfe0332a 20000004cfe0332a 0x0 (Disk
device)
17 b1 0 22000004cfe02eaf 20000004cfe02eaf 0x0 (Disk
device)
18 90 0 22000011c62a10a3 20000011c62a10a3 0x0 (Disk
device)
19 a5 0 22000004cfe02e14 20000004cfe02e14 0x0 (Disk
device)
20 84 0 22000011c62a1680 20000011c62a1680 0x0 (Disk
device)
21 ac 0 22000004cfe02e16 20000004cfe02e16 0x0 (Disk
device)
22 82 0 22000011c62a1702 20000011c62a1702 0x0 (Disk
device)
23 a6 0 22000004cfe03792 20000004cfe03792 0x0 (Disk
device)
24 ae 0 22000004cfe03039 20000004cfe03039 0x0 (Disk
device)
25 1 0 210000e08b90e91c 200000e08b90e91c 0x1f (Unknown
Type,Host Bus Adapter)

...it also appears that the ses kernel module is loaded correctly...

# modinfo -i `modinfo | grep ses | awk '{print $1}'` -w
 Id Loadaddr Size Info Rev Module Name
147 ffffffffef40f000 5eb0 200 1 ses (SCSI Enclosure Services Driver
)

# modinfo -i 147 -c
 Id Loadcnt Module Name State
147 2 ses LOADED/INSTALLED

...I've found these emails (http://tinyurl.com/2slvag &
http://tinyurl.com/28kexw) from several years ago describing the same
issue, but the resolution is to run "luxadm insert" to create the
/dev/es entries. However, this isn't supported on x86 apparently...

# luxadm insert
Unsupported

Is there something obvious I may have missed here?

Thanks for any help, and of course, I will summarize any responses.

-Sam

---
Sam Storie
Database Administrator
Rosemount Incorporated
Emerson Process Management
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers


This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:41:53 EDT