Error on discovery using emulex be2iscsi

514 views
Skip to first unread message

adebarbara

unread,
Mar 14, 2014, 3:33:25 PM3/14/14
to open-...@googlegroups.com
Hi guys,

I am hitting an issue where I could not even discovery targets using be2iscsi driver.
So If someone are using emulex on HP Proliant servers and have any hint on what is going please drop me a line. 
 
The following is the output I get when I load the kernel driver and trying to discover on a target running ilo (tgt do the same).

My system 

Kernel : Linux 3.9.6-030906-generic #201306131535 SMP Thu Jun 13 19:35:54 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Controller : Mass storage controller: Emulex Corporation OneConnect 10Gb iSCSI Initiator (rev 02)
Emulex driver: Emulex OneConnectOpen-iSCSI Driver version10.0.272.0
Distro : Ubuntu 12.10

Thanks in advance!


------

modprobe be2iscsi

[10835.048474] scsi17 : Emulex 10Gbe open-iscsi Initiator Driver
[10835.049145] be2iscsi 0000:05:00.2: irq 112 for MSI/MSI-X
[10835.049164] be2iscsi 0000:05:00.2: irq 113 for MSI/MSI-X
[10835.049188] be2iscsi 0000:05:00.2: irq 114 for MSI/MSI-X
[10835.049204] be2iscsi 0000:05:00.2: irq 115 for MSI/MSI-X
[10835.049220] be2iscsi 0000:05:00.2: irq 116 for MSI/MSI-X
[10835.049236] be2iscsi 0000:05:00.2: irq 117 for MSI/MSI-X
[10835.049251] be2iscsi 0000:05:00.2: irq 118 for MSI/MSI-X
[10835.049266] be2iscsi 0000:05:00.2: irq 119 for MSI/MSI-X
[10840.391427] scsi host17: BC_174 : MBX Cmd Completion timed out
[10840.402716] scsi host17: BG_1163 : MBX CMD get_boot_target Failed
[10840.413885] scsi host17: BM_3880 : No boot session
[10840.436963] scsi host17: BC_174 : MBX Cmd Completion timed out
[10840.447943] scsi host17: BG_751 : mgmt_exec_nonemb_cmd Failed status
[10840.470781] scsi host17: BC_174 : MBX Cmd Completion timed out
[10840.481637] scsi host17: BG_751 : mgmt_exec_nonemb_cmd Failed status

iscsiadm -m discovery -I be2iscsi.38:ea:a7:a5:62:89.ipv4.0 -p 10.70.3.250 -t st

Mar 13 17:49:56 e31-host02 kernel: [10946.559435] scsi host15: BC_206
: MBX Cmd Failed for Subsys : 6 Opcode : 52 with Status : 32 and
Extd_Status : 1
Mar 13 17:49:56 e31-host02 kernel: [10946.569905] scsi host15: BS_1073
: mgmt_open_connection Failed
Mar 13 17:49:56 e31-host02 kernel: [10946.580209] scsi host15: BS_1141
: Failed in beiscsi_open_conn
iscsiadm: Received iferror -16: Device or resource busy.
iscsiadm: Connection to discovery portal 10.70.3.250 failed:
encountered connection failure
Mar 13 17:49:57 e31-host02 kernel: [10947.615583] scsi host15: BC_206
: MBX Cmd Failed for Subsys : 6 Opcode : 52 with Status : 32 and
Extd_Status : 1
Mar 13 17:49:57 e31-host02 kernel: [10947.626074] scsi host15: BS_1073
: mgmt_open_connection Failed
Mar 13 17:49:57 e31-host02 kernel: [10947.636385] scsi host15: BS_1141
: Failed in beiscsi_open_conn
iscsiadm: Received iferror -16: Device or resource busy.
iscsiadm: Connection to discovery portal 10.70.3.250 failed:
encountered connection failure
Mar 13 17:49:58 e31-host02 kernel: [10948.672143] scsi host15: BC_206
: MBX Cmd Failed for Subsys : 6 Opcode : 52 with Status : 32 and
Extd_Status : 1
Mar 13 17:49:58 e31-host02 kernel: [10948.682591] scsi host15: BS_1073
: mgmt_open_connection Failed
Mar 13 17:49:58 e31-host02 kernel: [10948.692899] scsi host15: BS_1141
: Failed in beiscsi_open_conn
iscsiadm: Received iferror -16: Device or resource busy.
iscsiadm: Connection to discovery portal 10.70.3.250 failed:
encountered connection failure
Mar 13 17:49:59 e31-host02 kernel: [10949.730847] scsi host15: BC_206
: MBX Cmd Failed for Subsys : 6 Opcode : 52 with Status : 32 and
Extd_Status : 1
Mar 13 17:49:59 e31-host02 kernel: [10949.741342] scsi host15: BS_1073
: mgmt_open_connection Failed
Mar 13 17:49:59 e31-host02 kernel: [10949.751655] scsi host15: BS_1141
: Failed in beiscsi_open_conn
iscsiadm: Received iferror -16: Device or resource busy.
iscsiadm: Connection to discovery portal 10.70.3.250 failed:
encountered connection failure
Mar 13 17:50:00 e31-host02 snmpd[10412]: error on subcontainer
'ia_addr' insert (-1)
Mar 13 17:50:00  snmpd[10412]: last message repeated 2 times
Mar 13 17:50:00 e31-host02 kernel: [10950.787615] scsi host15: BC_206
: MBX Cmd Failed for Subsys : 6 Opcode : 52 with Status : 32 and
Extd_Status : 1
Mar 13 17:50:00 e31-host02 kernel: [10950.798721] scsi host15: BS_1073
: mgmt_open_connection Failed
Mar 13 17:50:00 e31-host02 kernel: [10950.809107] scsi host15: BS_1141
: Failed in beiscsi_open_conn
iscsiadm: Received iferror -16: Device or resource busy.
iscsiadm: Connection to discovery portal 10.70.3.250 failed:
encountered connection failure
Mar 13 17:50:01 e31-host02 kernel: [10951.845008] scsi host15: BC_206
: MBX Cmd Failed for Subsys : 6 Opcode : 52 with Status : 32 and
Extd_Status : 1
Mar 13 17:50:01 e31-host02 kernel: [10951.855527] scsi host15: BS_1073
: mgmt_open_connection Failed
Mar 13 17:50:01 e31-host02 kernel: [10951.865858] scsi host15: BS_1141
: Failed in beiscsi_open_conn
iscsiadm: Received iferror -16: Device or resource busy.
iscsiadm: Connection to discovery portal 10.70.3.250 failed:
encountered connection failure
iscsiadm: connection login retries (reopen_max) 5 exceeded
iscsiadm: No portals found


Sony John-N

unread,
Mar 17, 2014, 1:39:04 AM3/17/14
to open-...@googlegroups.com

Hi

 

Looks like initiator is not able to establish a TCP_CXN with the target.

Can the wire-trace during discovery command be captured and provided for debugging the issue.

 

Had few queries regarding the setup

-          Is the initiator-name set in /etc/iscsi path.

-          Is the IP address set on the initiator port. If IP is set can a ping from target machine to the initiator IP be tried out.

-          Please provide the wire-trace when discovery command was issued.

 

-Sony

--
You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+...@googlegroups.com.
To post to this group, send email to open-...@googlegroups.com.
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.

Sony John-N

unread,
Mar 17, 2014, 3:10:48 AM3/17/14
to open-...@googlegroups.com

--

bouc...@gmail.com

unread,
Jul 28, 2014, 11:45:33 AM7/28/14
to open-...@googlegroups.com, sony....@emulex.com
Did you ever solve this issue?  Seeing something similar and was curious what you did to resolve it.
Reply all
Reply to author
Forward
0 new messages