Hi Folks,
I've been having a time with connectivity for my T5120 + SunQlogic QLE2462 + DS14MK2 storage. I've spent over 10 days trying to figure this out, and could use some help. I bought the T5120 specifically to serve data from the storage (and to replace an aging Intel server).
The DS14MK2 is a Netapp shelf that I've procured. It worked beautifully with my DL380G4 + Qlogic (running X86_64, Solaris 11). It also worked beautifully with the QLE2452 connected to a Debian system.
So, I know that the shelf works, and I know that the Qlogic board is functioning. This leaves me with Solaris 11.1 on Sparc w/QLC driver.
The error I receive in /var/adm/messages is:
May 31 10:32:32 cohiba qlc: [ID 439991 kern.info] NOTICE: Qlogic qlc(3,0): Loop OFFLINE
May 31 10:32:32 cohiba qlc: [ID 439991 kern.info] NOTICE: Qlogic qlc(3,0): Loop ONLINE
May 31 10:32:42 cohiba scsi: [ID 243001 kern.warning] WARNING: /pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0,1/fp@0,0 (fcp5):
May 31 10:32:42 cohiba REPORT LUN to D_ID=0x79 lun=0x0 failed: State:Local Reject, Reason:Hardware Error. Giving up
May 31 10:32:42 cohiba scsi: [ID 243001 kern.warning] WARNING: /pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0,1/fp@0,0 (fcp5):
May 31 10:32:42 cohiba REPORT LUN to D_ID=0xc6 lun=0x0 failed: State:Local Reject, Reason:Hardware Error. Giving up
May 31 10:32:42 cohiba scsi: [ID 243001 kern.warning] WARNING: /pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0,1/fp@0,0 (fcp5):
May 31 10:32:42 cohiba REPORT LUN to D_ID=0x75 lun=0x0 failed: State:Local Reject, Reason:Hardware Error. Giving up
May 31 10:32:42 cohiba scsi: [ID 243001 kern.warning] WARNING: /pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0,1/fp@0,0 (fcp5):
May 31 10:32:42 cohiba REPORT LUN to D_ID=0x7a lun=0x0 failed: State:Local Reject, Re ..
...
.
Does anyone have any insight they could share? It would be most appreciated, as I've been banging my head against the literal wall with this.
cfgadm -c configure c1 return value is 0
cfgadm -f -c configure c1 return value is 0
I've tried to manually configure (cfgadm_fp mentions that fc-private is managed by driver, so I tried to manually configure) by adding "manual_configuration_only=1;" to fp.conf with the same result.
Some other system info:
root@cohiba:~# cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c1 fc-private connected unconfigured unknown
c1::220a000a338f5910 disk connected unconfigured unknown
c1::220a000a338f70fb disk connected unconfigured unknown
c1::220a000a338f7107 disk connected unconfigured unknown
c1::220a000a338f711b disk connected unconfigured unknown
c1::220a000a338f7140 disk connected unconfigured unknown
c1::220a000a338f714c disk connected unconfigured unknown
c1::220a000a338f7153 disk connected unconfigured unknown
c1::220a000a338f715d disk connected unconfigured unknown
c1::220a000a338f715f disk connected unconfigured unknown
c1::220a000a338f7165 disk connected unconfigured unknown
c1::220a000a338f7169 disk connected unconfigured unknown
c1::220a000a338f716d disk connected unconfigured unknown
c1::220a000a338f716e disk connected unconfigured unknown
c1::220a000a338f716f disk connected unconfigured unknown
c1::220a000a338f84f5 disk connected unconfigured unknown
c1::220a000a338f84fb disk connected unconfigured unknown
c1::220a000a338f84ff disk connected unconfigured unknown
c1::220a000a338f850a disk connected unconfigured unknown
c1::220a000a338f850d disk connected unconfigured unknown
c1::220a000a338f851b disk connected unconfigured unknown
c1::220a000a338f851f disk connected unconfigured unknown
c1::220a000a338f8525 disk connected unconfigured unknown
c1::220a000a338f8528 disk connected unconfigured unknown
c1::220a000a338f852c disk connected unconfigured unknown
c1::220a000a338f8535 disk connected unconfigured unknown
c1::220a000a338f8536 disk connected unconfigured unknown
c1::220a000a338f853e disk connected unconfigured unknown
c1::220a000a338f8543 disk connected unconfigured unknown
c1::220e000a332f169e ESI connected unconfigured unknown
c1::220e000a332f169f ESI connected unconfigured unknown
c1::220e000a33397e86 ESI connected unconfigured unknown
c1::220e000a33397e87 ESI connected unconfigured unknown
root@cohiba:~# uname -a
SunOS cohiba 5.11 11.1 sun4v sparc SUNW,SPARC-Enterprise-T5120
root@cohiba:~# fcinfo hba-port
HBA Port WWN: 21000024ff263086
Port Mode: Initiator
Port ID: 1
OS Device Name: /dev/cfg/c1
Manufacturer: QLogic Corp.
Model: 375-3356-02
Firmware Version: 5.6.4
FCode/BIOS Version: BIOS: 3.24; fcode: 3.19; EFI: 6.03;
Serial Number: 0402L00-1106921477
Driver Name: qlc
Driver Version: 20120717-4.01
Type: L-port
State: online
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: 2Gb
Node WWN: 20000024ff263086
Max NPIV Ports: 127
NPIV port list:
HBA Port WWN: 21000024ff263087
Port Mode: Initiator
Port ID: 1
OS Device Name: /dev/cfg/c6
Manufacturer: QLogic Corp.
Model: 375-3356-02
Firmware Version: 5.6.4
FCode/BIOS Version: BIOS: 3.24; fcode: 3.19; EFI: 6.03;
Serial Number: 0402L00-1106921477
Driver Name: qlc
Driver Version: 20120717-4.01
Type: L-port
State: online
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: 2Gb
Node WWN: 20000024ff263087
Max NPIV Ports: 127
NPIV port list:
root@cohiba:~# fcinfo remote-port -s -p 21000024ff263086
Remote Port WWN: 220a000a338f8543
Active FC4 Types:
SCSI Target: yes
Port Symbolic Name:
Node WWN: 2208000a338f8543
LUN: 0
Vendor: OCZ-VERT
Product: EX4 SX
OS Device Name: Unknown
Remote Port WWN: 220a000a338f5910
Active FC4 Types:
SCSI Target: yes
Port Symbolic Name:
Node WWN: 2208000a338f5910
LUN: 0
Vendor: HITACHI
Product: HUA721010KLA33SX
OS Device Name: Unknown
Remote Port WWN: 220e000a33397e86
| | Active FC4 Types: |
| | SCSI Target: yes |
| | Port Symbolic Name: |
| | Node WWN: 220c000a33397e86 |
| | LUN: 0 |
| | Vendor: XYRATEX |
| | Product: RS-1402-SA-XNS1 |
| | OS Device Name: Unknown |
Remote Port WWN: 220e000a33397e87
| | Active FC4 Types: |
| | SCSI Target: yes |
| | Port Symbolic Name: |
| | Node WWN: 220c000a33397e87 |
| | LUN: 0 |
| | Vendor: XYRATEX |
| | Product: RS-1402-SA-XNS1 |
| | OS Device Name: Unknown |
...
..
.
root@cohiba:/etc# luxadm -e port
/devices/pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0/fp@0,0:devctl CONNECTED
/devices/pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0,1/fp@0,0:devctl CONNECTED
root@cohiba:/etc# prtpicl -v | egrep "devfs-path|driver-name|subsystem-id" | nawk '/:subsystem-id/ { print $0; getline; print $0; getline; print $0; }' | nawk -F: '{ print $2 }'
| subsystem-id | 0x143 |
| devfs-path | /pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0 |
| driver-name | qlc |
| subsystem-id | 0x143 |
| devfs-path | /pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0,1 |
| driver-name | qlc |
root@cohiba:/etc# pkg update
No updates available for this image.
root@cohiba:/etc# pkg list -fav entire driver/fc/qlc
FMRI IFO
pkg://solaris/driver/fc/qlc@0.5.11,5.11-0.175.1.0.0.24.2:20120919T184250Z i--
pkg://solaris/driver/fc/qlc@0.5.11,5.11-0.175.0.10.1.0.0:20120918T160554Z ---
pkg://solaris/driver/fc/qlc@0.5.11,5.11-0.175.0.0.0.2.1:20111019T054709Z ---
pkg://solaris/entire@0.5.11,5.11-0.175.1.0.0.24.2:20120919T190135Z i--
pkg://solaris/entire@0.5.11,5.11-0.175.0.10.1.0.0:20120918T160900Z ---
pkg://solaris/entire@0.5.11,5.11-0.175.0.0.0.2.0:20111020T143822Z ---
pkg://solaris/entire@0.5.11,5.11-0.151.0.1:20101105T054056Z ---
root@cohiba:/etc#
I appreciate any help/assistance!!
Thanks,
Best,
Kevin