Login or Register to Ask a Question and Join Our Community


Solaris

Solaris OS having issue accessing LUN from Qlogic swich

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Solaris Solaris OS having issue accessing LUN from Qlogic swich
# 1  
Old 03-19-2015
Solaris OS having issue accessing LUN from Qlogic swich
Hi Community,

I am facing one issue related storage accessing from solaris 10 machine(M5000). it was working fine then we shifted to another site. the only change on that site is FC switch.

The issue i am facing is from solaris machine i can able to see the LUN, it;s only a test lun of 30 GB. If i gave format against that LUN. it's taking long time to respond and we cannot able to newfs that.

Some times it acting as normal . and that time we formatted once. and mounted. . Even if we try to write some data, the transfer speed we are getting is very low.

sometimes it's working normally and sometimes slow. we cannot able to find the actual issue. As we rise the case with storage and switch team , they are pointing this as solaris issue.

we put another server T2000 on that location and did the same steps and the result is same.

Here is the details hardware information:

Code:
Storage: VNX5600 Unified
FE version: 05.33.000.5.079
FC Switch : Brocade DS 6500
Switch firmware: 7.3.05

Oracle Solaris 10 8/11 s10s_u10wos_17b SPARC
 
HBA Port WWN: 2100001b329a5d63
OS Device Name: /dev/cfg/c20
Manufacturer: QLogic Corp.
Model: 371-4325-01
Firmware Version: 05.06.00
FCode/BIOS Version:  BIOS: 2.02; fcode: 2.03; EFI: 2.01;
Serial Number: 0402H00-0951796948
 
XSCF#0 (Active )
XCP0 (Reserve): 1119
OpenBoot PROM : 02.32.0000
XSCF : 01.11.0009
XCP1 (Current): 1119
OpenBoot PROM : 02.32.0000
XSCF : 01.11.0009
OpenBoot PROM BACKUP
#0: 01.25.0000
#1: 02.32.0000


Please anyone help me to fix this

Thanks & Regards,
Ben

---------- Post updated at 01:06 AM ---------- Previous update was at 01:05 AM ----------

Code:
bash-3.2# iostat -En
c1t0d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 1
Vendor: MATSHITA Product: CD-RW  CW-8124   Revision: DZ13 Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
c0t0d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: FUJITSU  Product: MAY2073RCSUN72G  Revision: 0401 Serial No: 0551S005EG
Size: 73.41GB <73407865856 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
c0t1d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: SEAGATE  Product: ST930003SSUN300G Revision: 0868 Serial No: 123771NVS2
Size: 300.00GB <300000000000 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c0t2d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: SEAGATE  Product: ST930003SSUN300G Revision: 0868 Serial No: 123670KQ0A
Size: 300.00GB <300000000000 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c0t3d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: SEAGATE  Product: ST930003SSUN300G Revision: 0868 Serial No: 12247569PE
Size: 300.00GB <300000000000 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c4t5006016808603B42d0 Soft Errors: 0 Hard Errors: 3 Transport Errors: 8
Vendor: DGC      Product: LUNZ             Revision: 0533 Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 39 Predictive Failure Analysis: 0
c4t5006016108603B42d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: DGC      Product: LUNZ             Revision: 0533 Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 38 Predictive Failure Analysis: 0
c5t5006016908603B42d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: DGC      Product: LUNZ             Revision: 0533 Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 40 Predictive Failure Analysis: 0
c5t5006016008603B42d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: DGC      Product: LUNZ             Revision: 0533 Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 40 Predictive Failure Analysis: 0
c8t6006016053C038008B0B1ABC90C1E411d0 Soft Errors: 0 Hard Errors: 1239 Transport Errors: 1413
Vendor: DGC      Product: VRAID            Revision: 0533 Serial No:
Size: 32.21GB <32212254720 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 23 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0

Code:
bash-3.2# fcinfo hba-port -l
HBA Port WWN: 21000024ff316d12
        OS Device Name: /dev/cfg/c5
        Manufacturer: QLogic Corp.
        Model: 371-4325-02
        Firmware Version: 05.04.03
        FCode/BIOS Version:  BIOS: 2.02; fcode: 2.03; EFI: 2.01;
        Serial Number: 0402H00-1052897823
        Driver Name: qlc
        Driver Version: 20110321-3.05
        Type: N-port
        State: online
        Supported Speeds: 2Gb 4Gb 8Gb
        Current Speed: 8Gb
        Node WWN: 20000024ff316d12
        Link Error Statistics:
                Link Failure Count: 1
                Loss of Sync Count: 0
                Loss of Signal Count: 0
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 0
                Invalid CRC Count: 0
HBA Port WWN: 21000024ff316d13
        OS Device Name: /dev/cfg/c4
        Manufacturer: QLogic Corp.
        Model: 371-4325-02
        Firmware Version: 05.04.03
        FCode/BIOS Version:  BIOS: 2.02; fcode: 2.03; EFI: 2.01;
        Serial Number: 0402H00-1052897823
        Driver Name: qlc
        Driver Version: 20110321-3.05
        Type: N-port
        State: online
        Supported Speeds: 2Gb 4Gb 8Gb
        Current Speed: 8Gb
        Node WWN: 20000024ff316d13
 
 
        Link Error Statistics:
                Link Failure Count: 1
                Loss of Sync Count: 0
                Loss of Signal Count: 0
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 0
                Invalid CRC Count: 0
HBA Port WWN: 210000c0dd297f59
        OS Device Name: /dev/cfg/c6
        Manufacturer: QLogic Corp.
        Model: 7053422
        Firmware Version: 05.04.03
        FCode/BIOS Version:  BIOS: 3.00; fcode: 3.15; EFI: 3.20;
        Serial Number: 463916R+1404161941
        Driver Name: qlc
        Driver Version: 20110321-3.05
        Type: unknown
        State: offline
        Supported Speeds: 10Gb
        Current Speed: not established
        Node WWN: 200000c0dd297f59
        Link Error Statistics:
                Link Failure Count: 0
                Loss of Sync Count: 0
                Loss of Signal Count: 0
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 0
                Invalid CRC Count: 0
HBA Port WWN: 210000c0dd297f5b
        OS Device Name: /dev/cfg/c7
        Manufacturer: QLogic Corp.
        Model: 7053422
        Firmware Version: 05.04.03
        FCode/BIOS Version:  BIOS: 3.00; fcode: 3.15; EFI: 3.20;
        Serial Number: 463916R+1404161941
        Driver Name: qlc
        Driver Version: 20110321-3.05
        Type: unknown
        State: offline
        Supported Speeds: 10Gb
        Current Speed: not established
        Node WWN: 200000c0dd297f5b
        Link Error Statistics:
                Link Failure Count: 0
                Loss of Sync Count: 0
                Loss of Signal Count: 0
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 0
                Invalid CRC Count: 0
HBA Port WWN: 2100001b321f5e37
        OS Device Name: /dev/cfg/c2
        Manufacturer: QLogic Corp.
        Model: QLA2462
        Firmware Version: 05.04.03
        FCode/BIOS Version:  BIOS: 1.12; fcode: 1.16; EFI: 1.04;
        Serial Number: RFC0719U45790
        Driver Name: qlc
        Driver Version: 20110321-3.05
        Type: unknown
        State: offline
        Supported Speeds: 1Gb 2Gb 4Gb
        Current Speed: not established
        Node WWN: 2000001b321f5e37
        Link Error Statistics:
                Link Failure Count: 0
                Loss of Sync Count: 0
                Loss of Signal Count: 0
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 0
                Invalid CRC Count: 0
HBA Port WWN: 2101001b323f5e37
        OS Device Name: /dev/cfg/c3
        Manufacturer: QLogic Corp.
        Model: QLA2462
        Firmware Version: 05.04.03
        FCode/BIOS Version:  BIOS: 1.12; fcode: 1.16; EFI: 1.04;
        Serial Number: RFC0719U45790
        Driver Name: qlc
        Driver Version: 20110321-3.05
        Type: unknown
        State: offline
        Supported Speeds: 1Gb 2Gb 4Gb
        Current Speed: not established
        Node WWN: 2001001b323f5e37
        Link Error Statistics:
                Link Failure Count: 0
                Loss of Sync Count: 0
                Loss of Signal Count: 0
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 0
                Invalid CRC Count: 0
...

this is only 30 GB and it's taking long time if i gaave format also.

Code:
iostat -En is showing "c8t6006016053C038008B0B1ABC90C1E411d0 Soft Errors: 0 Hard Errors: 1239 Transport Errors: 1413"

wthat this error means..?

---------- Post updated at 01:07 AM ---------- Previous update was at 01:06 AM ----------

what is the Link Failure Count: 1 in this output?

/var/adm/messages has some errors and i am not sure what it related to

Code:
Nov 17 21:48:32 test.alshaya.com scsi: [ID 107833 kern.notice]  Requested Block: 155320                    Error Block: 155320
Nov 17 21:48:32 test.alshaya.com scsi: [ID 107833 kern.notice]  Vendor: DGC                                Serial Number: 0D54F58DFBCL
Nov 17 21:48:32 test.alshaya.com scsi: [ID 107833 kern.notice]  Sense Key: Unit Attention
Nov 17 21:48:32 test.alshaya.com scsi: [ID 107833 kern.notice]  ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Nov 17 21:49:33 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 21:49:33 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 21:49:33 test.alshaya.com scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10):
Nov 17 21:49:33 test.alshaya.com        SCSI transport failed: reason 'timeout': retrying command
Nov 17 21:50:33 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 21:50:33 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 21:51:34 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 21:51:34 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 21:51:44 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 21:51:44 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 21:53:36 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 21:53:36 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 21:54:37 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 21:54:37 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 21:55:38 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 21:55:38 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 21:56:38 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 21:56:38 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 21:57:39 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 21:57:39 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 21:58:40 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 21:58:40 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 21:58:43 test.alshaya.com scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Nov 17 21:58:43 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command failed to complete (3) on path fp5/ssd@w5006016808603b42,1
Nov 17 21:58:43 test.alshaya.com scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10):
Nov 17 21:58:43 test.alshaya.com        SCSI transport failed: reason 'tran_err': retrying command
Nov 17 21:58:43 test.alshaya.com genunix: [ID 153160 kern.warning] WARNING: Page83 data not standards compliant DGC      LUNZ             0533
Nov 17 21:58:43 test.alshaya.com scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10):
Nov 17 21:58:43 test.alshaya.com        Error for Command: write(10)               Error Level: Retryable
Nov 17 21:58:43 test.alshaya.com scsi: [ID 107833 kern.notice]  Requested Block: 160558                    Error Block: 160558
Nov 17 21:58:43 test.alshaya.com scsi: [ID 107833 kern.notice]  Vendor: DGC                                Serial Number: 0D54F58DFBCL
Nov 17 21:58:43 test.alshaya.com scsi: [ID 107833 kern.notice]  Sense Key: Unit Attention
Nov 17 21:58:43 test.alshaya.com scsi: [ID 107833 kern.notice]  ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Nov 17 21:59:44 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 21:59:44 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 21:59:44 test.alshaya.com scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10):
Nov 17 21:59:44 test.alshaya.com        SCSI transport failed: reason 'timeout': retrying command
Nov 17 22:00:45 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:00:45 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:01:46 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:01:46 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:02:47 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:02:47 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:02:57 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:02:57 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:04:49 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:04:49 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:05:49 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:05:49 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:06:50 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:06:50 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:07:51 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:07:51 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:08:01 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:08:01 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:08:52 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:08:52 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:09:53 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:09:53 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:10:53 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:10:53 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:11:54 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:11:54 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:12:55 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:12:55 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:13:56 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:13:56 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:14:06 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:14:06 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:15:58 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:15:58 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:16:08 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:16:08 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:18:00 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:18:00 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:19:10 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 17 22:19:10 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 17 22:42:05 test.alshaya.com SC Alert: [ID 628137 daemon.alert] BATTERY at SC/BAT/V_BAT has exceeded low warning threshold.
Nov 17 22:42:05 test.alshaya.com last message repeated 1 time
Nov 18 00:42:11 test.alshaya.com SC Alert: [ID 628137 daemon.alert] BATTERY at SC/BAT/V_BAT has exceeded low warning threshold.
Nov 18 00:42:11 test.alshaya.com last message repeated 1 time
Nov 18 02:42:16 test.alshaya.com SC Alert: [ID 628137 daemon.alert] BATTERY at SC/BAT/V_BAT has exceeded low warning threshold.
Nov 18 02:42:16 test.alshaya.com last message repeated 1 time
Nov 18 04:42:21 test.alshaya.com SC Alert: [ID 628137 daemon.alert] BATTERY at SC/BAT/V_BAT has exceeded low warning threshold.
Nov 18 04:42:21 test.alshaya.com last message repeated 1 time
Nov 18 06:42:25 test.alshaya.com SC Alert: [ID 628137 daemon.alert] BATTERY at SC/BAT/V_BAT has exceeded low warning threshold.
Nov 18 06:42:25 test.alshaya.com last message repeated 1 time
Nov 18 08:42:30 test.alshaya.com SC Alert: [ID 628137 daemon.alert] BATTERY at SC/BAT/V_BAT has exceeded low warning threshold.
Nov 18 08:42:30 test.alshaya.com last message repeated 1 time
Nov 18 10:42:35 test.alshaya.com SC Alert: [ID 628137 daemon.alert] BATTERY at SC/BAT/V_BAT has exceeded low warning threshold.
Nov 18 10:42:35 test.alshaya.com last message repeated 1 time
Nov 18 12:42:41 test.alshaya.com SC Alert: [ID 628137 daemon.alert] BATTERY at SC/BAT/V_BAT has exceeded low warning threshold.
Nov 18 13:15:17 test.alshaya.com scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Nov 18 13:15:17 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command failed to complete (3) on path fp5/ssd@w5006016808603b42,1
Nov 18 13:16:18 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 18 13:16:18 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 18 13:19:27 test.alshaya.com scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Nov 18 13:19:27 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command failed to complete (3) on path fp5/ssd@w5006016808603b42,1
Nov 18 13:19:28 test.alshaya.com scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Nov 18 13:19:28 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command failed to complete (3) on path fp5/ssd@w5006016808603b42,1
Nov 18 13:19:29 test.alshaya.com scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Nov 18 13:19:29 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command failed to complete (3) on path fp5/ssd@w5006016808603b42,1
Nov 18 13:20:30 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 18 13:20:30 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 18 13:25:20 test.alshaya.com scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Nov 18 13:25:20 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command failed to complete (3) on path fp5/ssd@w5006016808603b42,1
Nov 18 13:25:20 test.alshaya.com scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10):
Nov 18 13:25:20 test.alshaya.com        SCSI transport failed: reason 'tran_err': retrying command
Nov 18 13:26:30 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Nov 18 13:26:30 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command Timeout on path fp5/ssd@w5006016808603b42,1
Nov 18 13:26:30 test.alshaya.com scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10):
Nov 18 13:26:30 test.alshaya.com        SCSI transport failed: reason 'timeout': retrying command
Nov 18 13:34:34 test.alshaya.com scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Nov 18 13:34:34 test.alshaya.com        /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10): Command failed to complete (3) on path fp5/ssd@w5006016808603b42,1
Nov 18 13:34:34 test.alshaya.com scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10):
Nov 18 13:34:34 test.alshaya.com        SCSI transport failed: reason 'tran_err': retrying command
Nov 18 13:36:19 test.alshaya.com fp: [ID 517869 kern.info] NOTICE: fp(5): PLOGI to 20000 failed state=Timeout, reason=Hardware Error
Nov 18 13:36:19 test.alshaya.com fctl: [ID 517869 kern.warning] WARNING: fp(5)::PLOGI to 20000 failed. state=c reason=1.
Nov 18 13:36:19 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /pci@7c0/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0 (fcp5):
Nov 18 13:36:19 test.alshaya.com        PLOGI to D_ID=0x20000 failed: State:Timeout, Reason:Hardware Error. Giving up
Nov 18 13:36:39 test.alshaya.com scsi: [ID 243001 kern.info] /pci@7c0/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0 (fcp5):
Nov 18 13:36:39 test.alshaya.com        offlining lun=1 (trace=0), target=20000 (trace=2800101)
Nov 18 13:36:39 test.alshaya.com scsi: [ID 243001 kern.info] /pci@7c0/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0 (fcp5):
Nov 18 13:36:39 test.alshaya.com        offlining lun=0 (trace=0), target=20000 (trace=2800101)
Nov 18 13:36:39 test.alshaya.com genunix: [ID 483743 kern.info] /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10) multipath status: optimal: path 5 fp5/ssd@w5006016808603b42,1 is offline
Nov 18 13:36:39 test.alshaya.com genunix: [ID 408114 kern.info] /pci@7c0/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0/ssd@w5006016808603b42,0 (ssd6) offline
Nov 18 13:42:43 test.alshaya.com SC Alert: [ID 628137 daemon.alert] BATTERY at SC/BAT/V_BAT has exceeded low warning threshold.
bash-3.2# tail -f /var/adm/messages
Nov 18 13:36:19 test.alshaya.com fctl: [ID 517869 kern.warning] WARNING: fp(5)::PLOGI to 20000 failed. state=c reason=1.
Nov 18 13:36:19 test.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /pci@7c0/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0 (fcp5):
Nov 18 13:36:19 test.alshaya.com        PLOGI to D_ID=0x20000 failed: State:Timeout, Reason:Hardware Error. Giving up
Nov 18 13:36:39 test.alshaya.com scsi: [ID 243001 kern.info] /pci@7c0/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0 (fcp5):
Nov 18 13:36:39 test.alshaya.com        offlining lun=1 (trace=0), target=20000 (trace=2800101)
Nov 18 13:36:39 test.alshaya.com scsi: [ID 243001 kern.info] /pci@7c0/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0 (fcp5):
Nov 18 13:36:39 test.alshaya.com        offlining lun=0 (trace=0), target=20000 (trace=2800101)
Nov 18 13:36:39 test.alshaya.com genunix: [ID 483743 kern.info] /scsi_vhci/ssd@g6006016053c038008b0b1abc90c1e411 (ssd10) multipath status: optimal: path 5 fp5/ssd@w5006016808603b42,1 is offline
Nov 18 13:36:39 test.alshaya.com genunix: [ID 408114 kern.info] /pci@7c0/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0/ssd@w5006016808603b42,0 (ssd6) offline
Nov 18 13:42:43 test.alshaya.com SC Alert: [ID 628137 daemon.alert] BATTERY at SC/BAT/V_BAT has exceeded low warning threshold.

is there any other steps recommended like EIS patching or something like that? it it related to our system kernel
Last edited by Scrutinizer; 03-19-2015 at 04:42 AM.. Reason: CODE tags
# 2  
Old 03-19-2015
Quote:
Nov 18 13:36:19 test.alshaya.com fp: [ID 517869 kern.info] NOTICE: fp(5): PLOGI to 20000 failed state=Timeout, reason=Hardware Error
Check for a hardware error.
# 3  
Old 03-19-2015
Hi

thanks for the reply.

hardware error means which one i need to suspect?

HBA card, san switch, server boards...?

---------- Post updated at 06:05 AM ---------- Previous update was at 06:02 AM ----------

as i told earlier. i have 2 hardware on same site.

the above errors are from T2000 server.

just now i was checking the other system, M5000,

when i cd to that particular filesystem mounted under /mnt, i am getting below error on var/adm/messages
Code:
Mar 19 14:00:56 globalprod1.alshaya.com scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Mar 19 14:00:56 globalprod1.alshaya.com         /scsi_vhci/ssd@g6006016053c0380015cd88a372b7e411 (ssd44): Command failed to complete (3) on path fp29/ssd@w5006016808603b42,1
Mar 19 14:00:56 globalprod1.alshaya.com scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6006016053c0380015cd88a372b7e411 (ssd44):
Mar 19 14:00:56 globalprod1.alshaya.com         SCSI transport failed: reason 'tran_err': retrying command
Mar 19 14:00:57 globalprod1.alshaya.com scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6006016053c0380015cd88a372b7e411 (ssd44):
Mar 19 14:00:57 globalprod1.alshaya.com         SCSI transport failed: reason 'tran_err': giving up
Mar 19 14:00:59 globalprod1.alshaya.com scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6006016053c0380015cd88a372b7e411 (ssd44):
Mar 19 14:00:59 globalprod1.alshaya.com         SCSI transport failed: reason 'tran_err': giving up
Mar 19 14:02:00 globalprod1.alshaya.com scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
Mar 19 14:02:00 globalprod1.alshaya.com         /scsi_vhci/ssd@g6006016053c0380015cd88a372b7e411 (ssd44): Command Timeout on path fp29/ssd@w5006016808603b42,1
Mar 19 14:02:00 globalprod1.alshaya.com scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6006016053c0380015cd88a372b7e411 (ssd44):
Mar 19 14:02:00 globalprod1.alshaya.com         SCSI transport failed: reason 'timeout': retrying command
Mar 19 14:02:01 globalprod1.alshaya.com scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Mar 19 14:02:01 globalprod1.alshaya.com         /scsi_vhci/ssd@g6006016053c0380015cd88a372b7e411 (ssd44): Command failed to complete (3) on path fp29/ssd@w5006016808603b42,1
Mar 19 14:02:01 globalprod1.alshaya.com scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6006016053c0380015cd88a372b7e411 (ssd44):
Mar 19 14:02:01 globalprod1.alshaya.com         SCSI transport failed: reason 'tran_err': giving up
Mar 19 14:02:02 globalprod1.alshaya.com scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6006016053c0380015cd88a372b7e411 (ssd44):
Mar 19 14:02:02 globalprod1.alshaya.com         SCSI transport failed: reason 'tran_err': giving up
Mar 19 14:02:03 globalprod1.alshaya.com scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g6006016053c0380015cd88a372b7e411 (ssd44):
Mar 19 14:02:03 globalprod1.alshaya.com         SCSI transport failed: reason 'tran_err': giving up

Last edited by Franklin52; 03-19-2015 at 08:25 AM.. Reason: Please use code tags
# 4  
Old 03-19-2015
Problem could be anywhere, from a bad SFP+ module to bad fibre, etc... I think I have them all. The bad SFP+ is always sad since they are expensive (but you probably have it under warranty).
# 5  
Old 03-19-2015
no SFP is already changed to brocade as suggested by Brocade support.
# 6  
Old 03-19-2015
You mean, changed to Qlogic? Or did Brocade buy Qlogic and I missed that?

And by "change" you mean you are using a different one than you had before (when you saw the transmission errors). Right? And you're still seeing the errors?
# 7  
Old 03-19-2015
Did you try known-to-be good FC cables?

Run this under sh/bash:
Code:
for hba in `fcinfo hba-port | grep WWN | awk '{ print $4 }'`; do fcinfo remote-port -ls -p $hba; done

Post the results.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

How to get LUN WWN in Solaris?

How to get LUN WWN (i.e LUN mapped from a storage box say Symmetrix or clariion) in Solaris. fcinfo command does give the Target port wwn but what i'm looking for is the LUN WWN. Any help is appreciated. (2 Replies)
Discussion started by: Manish00712
2 Replies

2. Shell Programming and Scripting

Issue with accessing value inside while loop, outside it

Hi, GetName() { if then echo " Please enter the name: " read Name tempvar=0 while read line do if then tempvar=`expr $tempvar + 1` echo $tempvar ... (10 Replies)
Discussion started by: rituparna_gupta
10 Replies

3. Solaris

Problem with Solaris LUN and New FS

Hi All, I'm using Solaris server, SunOS 5.10 Generic_144488-08 sun4u sparc SUNW, SPARC-Enterprise. There is a newly created LUN of 250GB (EMC). I've scanned the system and able to see the new LUN. For example: 103. emcpower19a <DGC-VRAID-0430 cyl 48638 alt 2 hd 256 sec 16>... (4 Replies)
Discussion started by: superHonda123
4 Replies

4. Red Hat

lun masking at qlogic HBA level

need to do LUN masking at qlogic HBA level..at RHEL 5.x I am using qla* module at part of the Unix kernel, it is not OEM drivers that come with the HBA card, so I can't use Sansurfer to do this.. Is there a way to do this at all ?? :wall: (0 Replies)
Discussion started by: ppchu99
0 Replies

5. Linux

EMC, PowerPath and issue on using LUN

Hello guys, I'm going crazy over here with a problem with a LUN created on a EMC CX3. I did sucessfully managed to create the LUN on the Storage (the LUN is named DBLNX25EC_TST), after doing the following process: echo "1" > /sys/class/fc_host/host<n>/issue_lip and echo "- - -" >... (10 Replies)
Discussion started by: Zarnick
10 Replies

6. Solaris

new attached lun in solaris 10

hi, what are the steps to detect and configure a new attached lun in Solaris 10. Is there any difference between cfgadm and luxadm command ? rgds, snjksh (5 Replies)
Discussion started by: snjksh
5 Replies

7. Solaris

Solaris 10 - QLogic 4060C iSCSI adapter - multipathed (MPxIO)

System: Sun M3000 and M4000 OS: Solaris 10 (fully up to date with latest patches) iSCSI HBA: 2x QLE4060C (QLogic) In each system are 2 QLE4060C iSCSI adapters. I manage to set up both HBA's to connect to the LUNs on the SAN However I don't manage to enable multi-pathing. Made the... (4 Replies)
Discussion started by: sb008
4 Replies

8. Shell Programming and Scripting

Swich statement based on a grep?

I'm piping the results of a tcpdump into a shell script and want certain commands executed (specifically the firing of an SNMP alert) based on a grep for certain contents in the output of tcpdump. For example, I have #!/bin/bash while read str; do grep 'ttl 64' -q && sudo snmptrap -v 1... (2 Replies)
Discussion started by: paulobrad
2 Replies

9. Solaris

Solaris 9 or 10 LUN Limitations

Is there a limit to the number of LUNS that can be concatenated using Solaris Volume manager with Soft partitions? I have worked with some AIX admins in the past and there was such a limitation therefore limiting the size the filesystem could grow to. Is there such a limitation in Solaris 9... (6 Replies)
Discussion started by: BG_JrAdmin
6 Replies

10. Programming

Structure element accessing issue...

Hi all, Can someone advice, why I'm getting a segmentation fault on a Linux system for a program which looks like the below one--: typedef struct idev{ int p, char q; } Idev; typedef struct abc{ int i; Idev *idev_ptr; } ABC; int main(){ ABC a_var; char str; int... (4 Replies)
Discussion started by: Praveen_218
4 Replies
Login or Register to Ask a Question