Solaris OS having issue accessing LUN from Qlogic swich

UNIX Solaris
1

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:

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 ----------

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

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.

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

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

2

Check for a hardware error.

3

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

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
4

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

no SFP is already changed to brocade as suggested by Brocade support.

6

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

Did you try known-to-be good FC cables?

Run this under sh/bash:

for hba in `fcinfo hba-port | grep WWN | awk '{ print $4 }'`; do fcinfo remote-port -ls -p $hba; done

Post the results.

8

HI

thanks all SAN issue got it seems .after patch update

but still having issue with 10 G network card. if i reset the port from san switch , it will ping the IP and after sometime it's going offline and on Switch side this interface is not learning MAC address.

---------- Post updated 03-20-15 at 01:17 AM ---------- Previous update was 03-19-15 at 03:43 PM ----------

bash-3.2# for hba in `fcinfo hba-port | grep WWN | awk '{ print $4 }'`; do fcinfo remote-port -ls -p $hba; done
Remote Port WWN: 5006016808603b42
        Active FC4 Types: SCSI
        SCSI Target: yes
        Node WWN: 5006016088603b42
        Link Error Statistics:
                Link Failure Count: 3
                Loss of Sync Count: 256
                Loss of Signal Count: 2
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 510
                Invalid CRC Count: 1
        LUN: 0
          Vendor: DGC
          Product: LUNZ
          OS Device Name: /dev/rdsk/c20t5006016808603B42d0s2
        LUN: 1
          Vendor: DGC
          Product: VRAID
          OS Device Name: /dev/rdsk/c1t6006016053C0380015CD88A372B7E411d0s2
        LUN: 2
          Vendor: DGC
          Product: VRAID
          OS Device Name: /dev/rdsk/c1t6006016053C03800A680673729CEE411d0s2
Remote Port WWN: 5006016108603b42
        Active FC4 Types: SCSI
        SCSI Target: yes
        Node WWN: 5006016088603b42
        Link Error Statistics:
                Link Failure Count: 1
                Loss of Sync Count: 1
                Loss of Signal Count: 1
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 255
                Invalid CRC Count: 0
        LUN: 0
          Vendor: DGC
          Product: LUNZ
          OS Device Name: /dev/rdsk/c20t5006016108603B42d0s2
        LUN: 1
          Vendor: DGC
          Product: VRAID
          OS Device Name: /dev/rdsk/c1t6006016053C0380015CD88A372B7E411d0s2
        LUN: 2
          Vendor: DGC
          Product: VRAID
          OS Device Name: /dev/rdsk/c1t6006016053C03800A680673729CEE411d0s2
Remote Port WWN: 5006016408643b42
        Active FC4 Types: SCSI
        SCSI Target: yes
        Node WWN: 5006016088603b42
        Link Error Statistics:
                Link Failure Count: 0
                Loss of Sync Count: 0
                Loss of Signal Count: 2
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 255
                Invalid CRC Count: 0
        LUN: 0
          Vendor: DGC
          Product: LUNZ
          OS Device Name: /dev/rdsk/c12t5006016408643B42d0s2
        LUN: 3
          Vendor: DGC
          Product: VRAID
          OS Device Name: /dev/rdsk/c1t6006016053C0380006E0535A33CEE411d0s2
Remote Port WWN: 5006016d08643b42
        Active FC4 Types: SCSI
        SCSI Target: yes
        Node WWN: 5006016088603b42
        Link Error Statistics:
                Link Failure Count: 0
                Loss of Sync Count: 0
                Loss of Signal Count: 1
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 255
                Invalid CRC Count: 0
        LUN: 0
          Vendor: DGC
          Product: LUNZ
          OS Device Name: /dev/rdsk/c12t5006016D08643B42d0s2
        LUN: 3
          Vendor: DGC
          Product: VRAID
          OS Device Name: /dev/rdsk/c1t6006016053C0380006E0535A33CEE411d0s2

and moreover fro yesterday onwords i am watching the logs, from another script i did some mount->touch files -> delete files -> unmount is doing. till now no isues for SAN connectivity

But still have issue with network card

---------- Post updated at 01:17 AM ---------- Previous update was at 01:17 AM ----------

bash-3.2# dladm show-dev
bge0            link: up        speed: 1000  Mbps       duplex: full
bge1            link: unknown   speed: 0     Mbps       duplex: unknown
qlge2           link: up        speed: 10000 Mbps       duplex: full
qlge3           link: unknown   speed: 10000 Mbps       duplex: half
 
bash-3.2# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.200.52 netmask ffffff00 broadcast 172.16.200.255
        ether 0:21:28:d6:41:10
qlge2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
        inet 172.16.200.51 netmask ffffff00 broadcast 172.16.200.255
        ether 0:c0:dd:29:7f:68
 
port is showing as UP
 
what is the steps to diaganose this issue.
 
Network also same physical layer.
card : Qlogic
Switch : Brocade

---------- Post updated at 05:00 PM ---------- Previous update was at 01:17 AM ----------

HI

any helps please

regards,
Ben

9

What's the output from netstat -rn? What's the contents of /etc/defaultrouter?

10

Hi please find below o/p's

bash-3.2# netstat -nr

Routing Table: IPv4
  Destination           Gateway           Flags  Ref     Use     Interface
-------------------- -------------------- ----- ----- ---------- ---------
default              172.16.200.10        UG        1        163
172.16.200.0         172.16.200.52        U         1         52 bge0
172.16.200.0         172.16.200.51        U         1          0 qlge2
192.168.254.1        192.168.254.2        UH        1          0 sppp0
224.0.0.0            172.16.200.52        U         1          0 bge0
127.0.0.1            127.0.0.1            UH        1          0 lo0


bash-3.2# cat /etc/defaultrouter
172.16.200.10

---------- Post updated at 12:18 PM ---------- Previous update was at 01:17 AM ----------

we noticed that wen we reset the port from the switch side, it's working for at-least 2 hours, after that ip is not pining

11

What's not responding to pings? From where?

Can you ping 172.16.200.10 from the server?

12

Hi
i tried to ping from outside.

if i ping the gateway, it's pining because the server already has one another 1 G interface.

13

Swap the network cables and see which one works.

14

Hi thanks for the replay.

we already changed the cables and card too.

we have opened once case with brocade (switch vendor).and what they find out from server is:

Type: unknown 
State: offline 
Current Speed: Not Established 
Note:- This implies that the speed not auto negotiable 
Type: unknown 
Note:- This implies that the Server is not even detecting the Card installed. 

Probably, the Drivers/Firmware has to be updated to get this resolved from the Server. There is no issue from the VDX reason being the Connectivity, Link and Protocol status is UP (TenGigabitEthernet 4/0/42 is up, line protocol is up (connected).

and the hba info is showing card as online and is giving the speed as 10 GB

Regards,
Ben

---------- Post updated at 08:46 AM ---------- Previous update was at 06:17 AM ----------

hi

the card is showing as offline always

HBA Port WWN: 210000c0dd297f69
        OS Device Name: /dev/cfg/c16
        Manufacturer: QLogic Corp.
        Model: 7053422
        Firmware Version: 5.08.00
        FCode/BIOS Version:  BIOS: 3.00; fcode: 3.15; EFI: 3.20;
        Serial Number: 463916R+1404161944
        Driver Name: qlc
        Driver Version: 20140422-5.01
        Type: unknown
        State: offline
        Supported Speeds: 10Gb
        Current Speed: not established
        Node WWN: 200000c0dd297f69
HBA Port WWN: 210000c0dd297f6b
        OS Device Name: /dev/cfg/c17
        Manufacturer: QLogic Corp.
        Model: 7053422
        Firmware Version: 5.08.00
        FCode/BIOS Version:  BIOS: 3.00; fcode: 3.15; EFI: 3.20;
        Serial Number: 463916R+1404161944
        Driver Name: qlc
        Driver Version: 20140422-5.01
        Type: unknown
        State: offline
        Supported Speeds: 10Gb
        Current Speed: not established
        Node WWN: 200000c0dd297f6b

but wen we reset the port from switch, it will start ping . that time also card status is offline

bash-3.2# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
lo0:1: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        zone archibus
        inet 127.0.0.1 netmask ff000000
bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.200.52 netmask ffffff00 broadcast 172.16.200.255
        ether 0:21:28:d6:41:10
bge0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        zone archibus
        inet 172.16.200.53 netmask ffffff00 broadcast 172.16.200.255
qlge2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
        inet 172.16.200.51 netmask ffff0000 broadcast 172.16.255.255
        ether 0:c0:dd:29:7f:68
sppp0: flags=10010008d1<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST,IPv4,FIXEDMTU> mtu 1500 index 4
        inet 192.168.254.2 --> 192.168.254.1 netmask ffffff00
15

Is autonegotiation enabled?

16

HI

don't know much details.

how to check that..?

17

Probably something like:

for parm in `ndd /dev/net/qlge2 \? | awk '{ print $1 }' | grep -v '?'`;
do
    echo -n $parm:
    ndd /dev/net/qlge2 $parm 2> /dev/null
done

Replace /dev/net/qlge2 with whatever the device path is in your version of Solaris.

1 Like
18

Hi

iit's not runnig

operation:operation failed: Invalid argument
bash-3.2# sh -x auto
+ grep -v ?
+ awk { print $1 }
+ ndd /dev/qlge2 ?
+ echo -n operation:
-n operation:
+ ndd /dev/qlge2 operation
operation failed: Invalid argument

---------- Post updated at 01:38 AM ---------- Previous update was at 12:01 AM ----------

HI

i am getting invalid argument on ndd

bash-3.2# ndd /dev/qlge \?
operation failed: Invalid argument