Re: Antw: Re: Connection faillure RHEL 5.5 bnx2i
On 6 Sep., 11:36, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote: Michael Wolf mwol...@me.com schrieb am 06.09.2010 um 10:54 in Nachricht 4c9e0ac7-c76b-49b8-9a38-67f9cba19...@q2g2000yqq.googlegroups.com: I am not able to connect with nx2i protocol. Why? Ethereal / Wireshark, maybe? Hi all, I think I was able to find a solution for the connectivity failures. 1) For the connectivity beetween hosts and EQ box I use DELL 6248 switches. The hosts interfacese, switches and EQ box are confiured to use jumbo frames (MTU=9000). The reason for my connectivity problems was, that the DELL switches need to be configured with Maximum Frame Size = 9216. 9000 is not enougth. After changing this parameter it works. The other option is to use standard frame size on all devices MTU 1500. 2) The Broadcom adapters and there aktual driver does not support multipathing. I was able to connect with one adapter whithout problem, but I was not able to get an second connection to the EQ-Box. Thanks for your help. Michael -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Connection faillure RHEL 5.5 bnx2i
On 4 Sep., 17:42, Michael Wolf mwol...@me.com wrote: On 4 Sep., 02:49, Benjamin Li be...@broadcom.com wrote: Hi Michael, My responses are below: On Fri, 2010-09-03 at 11:51 -0700, Mike Christie wrote: On 09/03/2010 10:06 AM, Michael Wolf wrote: Sep 3 16:47:35 ora-db-rac1-04 iscsid: Received iferror -1 Sep 3 16:47:35 ora-db-rac1-04 iscsid: cannot make a connection to 10.10.77.10:3260 (-1,11) Sep 3 16:47:40 ora-db-rac1-04 kernel: bnx2i [02:00.00]: ISCSI_INIT passed Are both network interfaces for the offload cards ifup'd, have a ip address on the same subnet as the iscsi offload card, and started ok? Could you provide the iface files you are using, the /var/log/messsage logs, the /var/log/brcm-iscsi.log, and a network trace when the connection fails? This will definitely help in debugging this problem. Any idea what I am missing? Is bnx2i driver able to connect with multiple paths on RHEL 5.5? It works here. I have not tired it when they are all on the same subnet, but from some of the bug fix patches it looks like broadcom has been testing equalogic/dell targets so I think they have. ccing them. Our PQA has tested this configuration, but you need to specify 1 iface per path and specify the device using the MAC address of the HBA via the 'iface.hwaddress' field of the iface. Thanks again. -Ben @Mike Both networkinterfaces are up and running. Connection with TCP protocol on these interfaces is no problem. Tey have IP addesses 10.10.77.163 and 10.10.77.164, which is the same subnet as the bnx2i interfaces 10.10.77.63 and 10.10.77.64. The netmask is 255.255.255.0. The EQ box has only one Group IP address 10.10.77.10. I have found informations in the internet, that broadcon does not support multpath connection with more than one adapter, because of driver problems. @Ben I'm not in the office today, I will deliver the logs on monday. /var/ log/messages and iface files are included in my first posting. The server has four broadcom dual port cards. For my first test I used only one internal dual adapter. eth2 and eth3 are on one broadcom interface with separete HW adresses. Might that be a problem? I will test with two iface on two separate broadcom cards on monday. Thanks again. Michael Monday morning, another try... I will try to set up ONE bnx2i interface to connect with my EQ box. I will use eth4 for that test. eth4 is up and running: eth4 Link encap:Ethernet HWaddr 00:10:18:64:98:B8 inet addr:10.10.77.165 Bcast:10.10.77.255 Mask: 255.255.255.0 inet6 addr: fe80::210:18ff:fe64:98b8/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:569 errors:0 dropped:0 overruns:0 frame:0 TX packets:310 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:162620 (158.8 KiB) TX bytes:101138 (98.7 KiB) Interrupt:122 Memory:d600-d6012800 with these iface file I am able to connect with TCP protocol. [r...@ora-db-rac1-04 ~]# iscsiadm --mode iface --interface eth4 # BEGIN RECORD 2.0-871 iface.iscsi_ifacename = eth4 iface.net_ifacename = eth4 iface.ipaddress = empty iface.hwaddress = empty iface.transport_name = tcp iface.initiatorname = empty # END RECORD TCP connections works great! Now I have configured my bnx2i iface as [r...@ora-db-rac1-04 ~]# iscsiadm -m iface -I bnx2i.00:10:18:64:98:b9 # BEGIN RECORD 2.0-871 iface.iscsi_ifacename = bnx2i.00:10:18:64:98:b9 iface.net_ifacename = empty iface.ipaddress = 10.10.77.65 iface.hwaddress = 00:10:18:64:98:b9 iface.transport_name = bnx2i iface.initiatorname = empty # END RECORD Then I discover my target... [r...@ora-db-rac1-04 ~]# iscsiadm -m discovery -t sendtargets -p 10.10.77.10 -I bnx2i.00:10:18:64:98:b9 -P3 Target: iqn.2001-05.com.equallogic:0-8a0906-ee18a0704-22d0020a97c4c7fb- mpio Portal: 10.10.77.10:3260,1 Iface Name: bnx2i.00:10:18:64:98:b9 Then I restart my iscsi service...Getting connect failure! [r...@ora-db-rac1-04 ~]# service iscsi restart Stopping iSCSI daemon: iscsid dead but pid file exists[ OK ] Starting iSCSI daemon: [ OK ] [ OK ] Setting up iSCSI targets: Logging in to [iface: bnx2i. 00:10:18:64:98:b9, target: iqn.2001-05.com.equallogic:0-8a0906- ee18a0704-22d0020a97c4c7fb-mpio, portal: 10.10.77.10,3260] iscsiadm: Could not login to [iface: bnx2i.00:10:18:64:98:b9, target: iqn.2001-05.com.equallogic:0-8a0906-ee18a0704-22d0020a97c4c7fb-mpio, portal: 10.10.77.10,3260]: iscsiadm: initiator reported error (8 - connection timed out) iscsiadm: Could not log into all portals. Err 8. [ OK ] /var/log/messages: Sep 6 10:44:45 ora-db-rac1-04 iscsid: iscsid shutting down. Sep 6 10:44:45 ora-db-rac1-04 kernel:
Antw: Re: Connection faillure RHEL 5.5 bnx2i
Michael Wolf mwol...@me.com schrieb am 06.09.2010 um 10:54 in Nachricht 4c9e0ac7-c76b-49b8-9a38-67f9cba19...@q2g2000yqq.googlegroups.com: I am not able to connect with nx2i protocol. Why? Ethereal / Wireshark, maybe? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Connection faillure RHEL 5.5 bnx2i
On 4 Sep., 02:49, Benjamin Li be...@broadcom.com wrote: Hi Michael, My responses are below: On Fri, 2010-09-03 at 11:51 -0700, Mike Christie wrote: On 09/03/2010 10:06 AM, Michael Wolf wrote: Sep 3 16:47:35 ora-db-rac1-04 iscsid: Received iferror -1 Sep 3 16:47:35 ora-db-rac1-04 iscsid: cannot make a connection to 10.10.77.10:3260 (-1,11) Sep 3 16:47:40 ora-db-rac1-04 kernel: bnx2i [02:00.00]: ISCSI_INIT passed Are both network interfaces for the offload cards ifup'd, have a ip address on the same subnet as the iscsi offload card, and started ok? Could you provide the iface files you are using, the /var/log/messsage logs, the /var/log/brcm-iscsi.log, and a network trace when the connection fails? This will definitely help in debugging this problem. Any idea what I am missing? Is bnx2i driver able to connect with multiple paths on RHEL 5.5? It works here. I have not tired it when they are all on the same subnet, but from some of the bug fix patches it looks like broadcom has been testing equalogic/dell targets so I think they have. ccing them. Our PQA has tested this configuration, but you need to specify 1 iface per path and specify the device using the MAC address of the HBA via the 'iface.hwaddress' field of the iface. Thanks again. -Ben @Mike Both networkinterfaces are up and running. Connection with TCP protocol on these interfaces is no problem. Tey have IP addesses 10.10.77.163 and 10.10.77.164, which is the same subnet as the bnx2i interfaces 10.10.77.63 and 10.10.77.64. The netmask is 255.255.255.0. The EQ box has only one Group IP address 10.10.77.10. I have found informations in the internet, that broadcon does not support multpath connection with more than one adapter, because of driver problems. @Ben I'm not in the office today, I will deliver the logs on monday. /var/ log/messages and iface files are included in my first posting. The server has four broadcom dual port cards. For my first test I used only one internal dual adapter. eth2 and eth3 are on one broadcom interface with separete HW adresses. Might that be a problem? I will test with two iface on two separate broadcom cards on monday. Thanks again. Michael -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Connection faillure RHEL 5.5 bnx2i
Michael Wolf wrote: Is bnx2i driver able to connect with multiple paths on RHEL 5.5? Out of a sick curiosity: does it make any difference if you're connected only to the iSCSI via only one interface? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Connection faillure RHEL 5.5 bnx2i
On 09/03/2010 10:06 AM, Michael Wolf wrote: Sep 3 16:47:35 ora-db-rac1-04 iscsid: Received iferror -1 Sep 3 16:47:35 ora-db-rac1-04 iscsid: cannot make a connection to 10.10.77.10:3260 (-1,11) Sep 3 16:47:40 ora-db-rac1-04 kernel: bnx2i [02:00.00]: ISCSI_INIT passed Are both network interfaces for the offload cards ifup'd, have a ip address on the same subnet as the iscsi offload card, and started ok? Any idea what I am missing? Is bnx2i driver able to connect with multiple paths on RHEL 5.5? It works here. I have not tired it when they are all on the same subnet, but from some of the bug fix patches it looks like broadcom has been testing equalogic/dell targets so I think they have. ccing them. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Connection faillure RHEL 5.5 bnx2i
Hi Michael, My responses are below: On Fri, 2010-09-03 at 11:51 -0700, Mike Christie wrote: On 09/03/2010 10:06 AM, Michael Wolf wrote: Sep 3 16:47:35 ora-db-rac1-04 iscsid: Received iferror -1 Sep 3 16:47:35 ora-db-rac1-04 iscsid: cannot make a connection to 10.10.77.10:3260 (-1,11) Sep 3 16:47:40 ora-db-rac1-04 kernel: bnx2i [02:00.00]: ISCSI_INIT passed Are both network interfaces for the offload cards ifup'd, have a ip address on the same subnet as the iscsi offload card, and started ok? Could you provide the iface files you are using, the /var/log/messsage logs, the /var/log/brcm-iscsi.log, and a network trace when the connection fails? This will definitely help in debugging this problem. Any idea what I am missing? Is bnx2i driver able to connect with multiple paths on RHEL 5.5? It works here. I have not tired it when they are all on the same subnet, but from some of the bug fix patches it looks like broadcom has been testing equalogic/dell targets so I think they have. ccing them. Our PQA has tested this configuration, but you need to specify 1 iface per path and specify the device using the MAC address of the HBA via the 'iface.hwaddress' field of the iface. Thanks again. -Ben -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
