Fibre Channel (SAN)

Reply
New Member
Posts: 1
Registered: ‎08-30-2017

SNS scan failed

一台服务器通过博科300交换机连接存储。存储端的操作系统是unbuntu ,客户端的操作系统是redhat7.2。然后客户端和存储端操作系统的HBA卡是qlogic qle 2562。该HBA卡一连接交换机就报错,但是客户端能够识别存储端的映射的LUN,就是无法对LUN进行任何操作。报错日志查看文件。但是客户端不适用交换机直接与存储端连接,就能够正确识别磁盘,并能够正常读写

部分报错日志客户端:

systemd: Started Stop Read-Ahead Data Collection.
Aug 28 16:17:44 host02 kernel: scsi 8:0:0:0: Direct-Access LIO-ORG IBLOCK 4.0 PQ: 0 ANSI: 5
Aug 28 16:18:14 host02 kernel: qla2xxx [0000:05:00.1]-801c:8: Abort command issued nexus=8:0:0 -- 1 2002.
Aug 28 16:18:14 host02 kernel: scsi 8:0:0:0: alua: supports implicit and explicit TPGS
Aug 28 16:18:14 host02 kernel: scsi 8:0:0:0: alua: port group 00 rel port 01
Aug 28 16:18:14 host02 kernel: scsi 8:0:0:0: alua: port group 00 state A non-preferred supports TOlUSNA
Aug 28 16:18:14 host02 kernel: scsi 8:0:0:0: alua: Attached
Aug 28 16:18:14 host02 kernel: sd 8:0:0:0: Attached scsi generic sg2 type 0
Aug 28 16:18:14 host02 kernel: sd 8:0:0:0: [sdb] 3847223296 512-byte logical blocks: (1.96 TB/1.79 TiB)
Aug 28 16:18:45 host02 kernel: qla2xxx [0000:05:00.1]-801c:8: Abort command issued nexus=8:0:0 -- 1 2002.
Aug 28 16:19:16 host02 kernel: qla2xxx [0000:05:00.1]-801c:8: Abort command issued nexus=8:0:0 -- 1 2002.
Aug 28 16:19:16 host02 kernel: sd 8:0:0:0: [sdb] Write Protect is off
Aug 28 16:19:16 host02 kernel: sd 8:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
Aug 28 16:19:47 host02 kernel: qla2xxx [0000:05:00.1]-801c:8: Abort command issued nexus=8:0:0 -- 1 2002.
Aug 28 16:19:48 host02 kernel: sd 8:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Aug 28 16:19:48 host02 kernel: sd 8:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Aug 28 16:19:48 host02 kernel: blk_update_request: I/O error, dev sdb, sector 0
Aug 28 16:19:48 host02 kernel: Buffer I/O error on device sdb, logical block 0
Aug 28 16:20:20 host02 kernel: qla2xxx [0000:05:00.1]-801c:8: Abort command issued nexus=8:0:0 -- 1 2002.
Aug 28 16:20:30 host02 kernel: qla2xxx [0000:05:00.1]-801c:8: Abort command issued nexus=8:0:0 -- 1 2002.
Aug 28 16:20:30 host02 kernel: qla2xxx [0000:05:00.1]-8009:8: DEVICE RESET ISSUED nexus=8:0:0 cmd=ffff880417742a00.
Aug 28 16:20:30 host02 kernel: qla2xxx [0000:05:00.1]-800e:8: DEVICE RESET SUCCEEDED nexus:8:0:0 cmd=ffff880417742a00.
Aug 28 16:20:40 host02 kernel: qla2xxx [0000:05:00.1]-801c:8: Abort command issued nexus=8:0:0 -- 1 2002.
Aug 28 16:20:40 host02 kernel: qla2xxx [0000:05:00.1]-8009:8: TARGET RESET ISSUED nexus=8:0:0 cmd=ffff880417742a00.
Aug 28 16:20:40 host02 kernel: qla2xxx [0000:05:00.1]-800e:8: TARGET RESET SUCCEEDED nexus:8:0:0 cmd=ffff880417742a00.
Aug 28 16:20:50 host02 kernel: qla2xxx [0000:05:00.1]-801c:8: Abort command issued nexus=8:0:0 -- 1 2002.
Aug 28 16:20:50 host02 kernel: qla2xxx [0000:05:00.1]-8012:8: BUS RESET ISSUED nexus=8:0:0.
Aug 28 16:20:50 host02 kernel: qla2xxx [0000:05:00.1]-802b:8: BUS RESET SUCCEEDED nexus=8:0:0.
Aug 28 16:21:00 host02 kernel: qla2xxx [0000:05:00.1]-8018:8: ADAPTER RESET ISSUED nexus=8:0:0.
Aug 28 16:21:00 host02 kernel: qla2xxx [0000:05:00.1]-00af:8: Performing ISP error recovery - ha=ffff880412918000.
Aug 28 16:21:12 host02 kernel: qla2xxx [0000:05:00.1]-d001:8: Firmware dump saved to temp buffer (8/ffffc90012327000), dump status flags (0x3f).
Aug 28 16:21:13 host02 kernel: qla2xxx [0000:05:00.1]-500a:8: LOOP UP detected (8 Gbps).
Aug 28 16:21:13 host02 kernel: qla2xxx [0000:05:00.1]-8017:8: ADAPTER RESET SUCCEEDED nexus=8:0:0.
Aug 28 16:21:23 host02 kernel: sd 8:0:0:0: Device offlined - not ready after error recovery
Aug 28 16:21:23 host02 kernel: sd 8:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
Aug 28 16:21:23 host02 kernel: sd 8:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Aug 28 16:21:23 host02 kernel: blk_update_request: I/O error, dev sdb, sector 0

 

部分报错日志存储端:

Aug 29 10:10:27 host01 kernel: [431548.717572] qla2xxx [0000:05:00.1]-00af:8: Performing ISP error recovery - ha=ffff880415500000.
Aug 29 10:10:30 host01 kernel: [431552.222884] qla2xxx [0000:05:00.1]-707c:8: ISP reset active.
Aug 29 10:10:30 host01 kernel: [431552.280700] qla2xxx [0000:05:00.1]-707c:8: ISP reset active.
Aug 29 10:10:31 host01 kernel: [431552.871547] qla2xxx [0000:05:00.1]-707c:8: ISP reset active.
Aug 29 10:10:32 host01 kernel: [431553.582864] qla2xxx [0000:05:00.1]-500a:8: LOOP UP detected (8 Gbps).
Aug 29 10:10:46 host01 sudo: pam_ecryptfs: pam_sm_authenticate: /home/cloud is already mounted
Aug 29 10:11:02 host01 kernel: [431584.215509] qla2xxx [0000:05:00.1]-1005:8: Cmd access timeout, cmd=0x7c, Exiting.
Aug 29 10:16:45 host01 kernel: [431926.257356] qla2xxx [0000:05:00.1]-2064:8: SNS scan failed -- assuming zero-entry result.
Aug 29 10:17:01 host01 CRON[10237]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Aug 29 10:18:49 host01 kernel: [432050.419869] qla2xxx/21:00:00:24:ff:2b:86:d3: Unsupported SCSI Opcode 0xa3, sending CHECK_CONDITION.
Aug 29 10:25:44 host01 kernel: [432465.659819] qla2xxx [0000:05:00.1]-2064:8: SNS scan failed -- assuming zero-entry result.

 

 

Brocade Moderator
Posts: 318
Registered: ‎08-31-2009

Re: SNS scan failed

Hello,

 

Looking like your comments are not readable. Please can you provide additional details about your request/question?

Also provide the switch view if your question is about HBA to switch connection issue.

 

Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution"
Brocade Moderator
Posts: 414
Registered: ‎03-29-2011

Re: SNS scan failed

Hi xuyafang,

 

I translated your comment via google translate, giving:

 

A server is connected via a Brocade 300 switch. Storage side of the operating system is unbuntu, the client operating system is redhat7.2. Then the client and the storage-side operating system's HBA card is qlogic qle 2562. The HBA card connected to the switch on the error, but the client can identify the storage side of the mapping LUN, is unable to LUN on any operation. Error log view file. But the client does not apply to the switch directly connected with the storage side, you can correctly identify the disk, and can read and write

Part of the error log client:

 

From what I understand - it works when connectly connected - but not when via  switch.

 

1. server is running red hat 7.2, with qla2562, connectect to a brocade 300 (first log)

 

2. storage is LIO (scsi target) running under ubuntu, also with qla2562 (second log)

 

Have you zoned the server and storage port with each other?

 

What is the output from:

 

. firmwareshow

. defzone --show

. cfgactvShow

. switchshow

. portloginshow <port number for server>

. portloginshow <port number for server>

. portcamshow <port number for server>

. portcamshow <port number for storage>

 

 

 




If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution".


Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution"

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.

vADC is now Pulse Secure
Download FREE NVMe eBook