Re: Antw: Re: Confirm that bnx2i iSCSI offload works for RHEL 5.5 on DELL EqualLogic
On 26 Aug., 22:34, Mike Christie wrote: > On 08/26/2010 09:23 AM, Michael Wolf wrote: > > > > > > > > > On 26 Aug., 10:46, "Ulrich Windl" > > wrote: > >>>>> Shyam Iyer schrieb am 25.08.2010 um 19:50 in > >>>>> Nachricht > > >> <4c7557f7.9000...@dell.com>: > > >>> On 08/25/2010 06:43 AM, Ciprian Marius Vizitiu (GBIF) wrote: > >>>> Michael Wolf wrote: > >>>>> Only four of them are connected to the SAN. How to figure out which hw- > >>>>> adress belongs to which interface? > >>>> Perhaps BIOS / iface's ROM util should give you some hint(s). > > >>> Offload HW address = ethX HW Address + 1 > > >> For a HP DL380G5 the ILO2 reports these under "System Information"/"NIC": > >> Port 1 NIC MAC address: 00:1A:4B:4D:25:B2 > >> Port 2 NIC MAC address: 00:1A:4B:4D:25:B0 > >> iLO 2: 00:1A:4B:4D:25:B4 > >> Port 1 iSCSI MAC address: 00:1A:4B:4D:25:B3 > >> Port 2 iSCSI MAC address: 00:1A:4B:4D:25:B1 > > >> So maybe it's a good idea to look at your management interface... > > >> Ulrich > > > Hi All, > > > Thank you for the information on hw addresses. > > It`s clear now. > > > We use OEL 5.5 kernel which is based on RHEL 5.5. > > > Is it correct to set the parameters > > node.conn[0].timeo.noop_out_timeout = 0 > > node.conn[0].timeo.noop_out_interval = 0 > > This will tell the initiator not to send nops as pings. But the target > will still send its own pings by default. You need to contact equalogic > to see how to turn them off.- Zitierten Text ausblenden - > > - Zitierten Text anzeigen - 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: Antw: Re: Connection faillure RHEL 5.5 bnx2i
On 6 Sep., 11:36, "Ulrich Windl" wrote: > >>> Michael Wolf 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 wrote: > On 4 Sep., 02:49, "Benjamin Li" 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 = iface.hwaddress = iface.transport_name = tcp iface.initiatorname = # 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 = iface.ipaddress = 10.10.77.65 iface.hwaddress = 00:10:18:64:98:b9 iface.transport_name = bnx2i iface.initiatorname = # 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-0
Re: Connection faillure RHEL 5.5 bnx2i
On 4 Sep., 02:49, "Benjamin Li" 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.
Connection faillure RHEL 5.5 bnx2i
eived iferror -1 Sep 3 16:46:56 ora-db-rac1-04 iscsid: cannot make a connection to 10.10.77.10:3260 (-1,11) Sep 3 16:47:04 ora-db-rac1-04 kernel: bnx2i [02:00.00]: ISCSI_INIT passed Sep 3 16:47:08 ora-db-rac1-04 iscsid: Received iferror -1 Sep 3 16:47:08 ora-db-rac1-04 iscsid: cannot make a connection to 10.10.77.10:3260 (-1,11) Sep 3 16:47:16 ora-db-rac1-04 kernel: bnx2i [02:00.00]: ISCSI_INIT passed Sep 3 16:47:19 ora-db-rac1-04 iscsid: Received iferror -1 Sep 3 16:47:19 ora-db-rac1-04 iscsid: cannot make a connection to 10.10.77.10:3260 (-1,11) Sep 3 16:47:28 ora-db-rac1-04 kernel: bnx2i [02:00.00]: ISCSI_INIT passed Sep 3 16:47:30 ora-db-rac1-04 iscsid: Received iferror -1 Sep 3 16:47:30 ora-db-rac1-04 iscsid: cannot make a connection to 10.10.77.10:3260 (-1,11) 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 Any idea what I am missing? Is bnx2i driver able to connect with multiple paths on RHEL 5.5? Regards Michael Wolf -- 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: Antw: Re: Confirm that bnx2i iSCSI offload works for RHEL 5.5 on DELL EqualLogic
On 26 Aug., 10:46, "Ulrich Windl" wrote: > >>> Shyam Iyer schrieb am 25.08.2010 um 19:50 in > >>> Nachricht > > <4c7557f7.9000...@dell.com>: > > > On 08/25/2010 06:43 AM, Ciprian Marius Vizitiu (GBIF) wrote: > > > Michael Wolf wrote: > > >> Only four of them are connected to the SAN. How to figure out which hw- > > >> adress belongs to which interface? > > > Perhaps BIOS / iface's ROM util should give you some hint(s). > > > Offload HW address = ethX HW Address + 1 > > For a HP DL380G5 the ILO2 reports these under "System Information"/"NIC": > Port 1 NIC MAC address: 00:1A:4B:4D:25:B2 > Port 2 NIC MAC address: 00:1A:4B:4D:25:B0 > iLO 2: 00:1A:4B:4D:25:B4 > Port 1 iSCSI MAC address: 00:1A:4B:4D:25:B3 > Port 2 iSCSI MAC address: 00:1A:4B:4D:25:B1 > > So maybe it's a good idea to look at your management interface... > > Ulrich Hi All, Thank you for the information on hw addresses. It`s clear now. We use OEL 5.5 kernel which is based on RHEL 5.5. Is it correct to set the parameters node.conn[0].timeo.noop_out_timeout = 0 node.conn[0].timeo.noop_out_interval = 0 to work with equallogic boxes? node.session.iscsi.FastAbort = No Any other issues with config files? On a second box I had done a fresh RHEL 5.5 installation from scratch. When I have problems here I think the best way is to open a new discussion for that. Hopefully original RHEL will work better than OEL. -- 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: Confirm that bnx2i iSCSI offload works for RHEL 5.5 on DELL EqualLogic
On 25 Aug., 09:55, Michael Wolf wrote: > On 25 Aug., 02:14, Mike Christie wrote: > > > > > > > On 08/24/2010 10:13 AM, Michael Wolf wrote: > > > > Hi ALL, > > > > I try to set up oracle cluster with four nodes (DELL R610) and > > > EqualLogig PS6000. > > > Servers has four Broadcom 5709C dual network cards, two intenal, two > > > PCI cards. > > > I`m trying to get the bnx2i driver to work using iSCSI offload for > > > four channels. > > > I can't get it to work, getting error > > > iscsiadm: Could not login to [iface: bnx2i.00:22:19:68:3a:04, target: > > > iqn.2001-05.com.equallogic:0-8a0906-76c630e04-e0492d35ddc63f-a1test, > > > portal: 10.10.77.10,3260): > > > iscsiadm: initiator reported error (4 - encountered connection > > > failure) > > > > Showing nothing in /var/log/messages and no events on the EQ box. > > > So there is no iferror error in messages or nothing from iscsid? > > > > DELL suport team is not shure if bnx2i driver will work with RHEL 5.5, > > > they ask me to reinstall RHEL 5.2, from my opinion is that not an > > > option. > > > I am using RHEL 5.5, oracle linux, kernel 2.6.18-194.11.1.0.1.el5 on > > > Is that a oracle linux kernel or the rhel 5.5 one? Are you running rhel > > 5.5 in a oracle linux vm? > > > > x86_64 > > > iscsi-initiator-utils-6.2.0.871-0.16.el5 > > > Also you need the updated iscsi > > utils.http://people.redhat.com/mchristi/iscsi/rhel5.6/iscsi-initiator-utils/ > > > > All firmware of the R610 is up to date > > > > All interfaces are shown as bnx2i > > > [r...@ora-db-rac1-04 ~]# scsiadm -m iface > > > -bash: scsiadm: command not found > > > [r...@ora-db-rac1-04 ~]# iscsiadm -m iface > > > default tcp > > > iser iser > > > bnx2i.00:22:19:68:3a:04 bnx2i,00:22:19:68:3a: > > > 04,10.10.77.69,, > > > Are these IPs on the same subnet as the network port they are attached to? > > > > bnx2i.00:22:19:68:3a:0a bnx2i,00:22:19:68:3a:0a, > > > 10.10.77.68,, > > > bnx2i.00:00:00:00:00:00 bnx2i, > > > 00:00:00:00:00:00,,, > > > bnx2i.00:22:19:68:3a:06 bnx2i,00:22:19:68:3a: > > > 06,10.10.77.67,, > > > bnx2i.00:10:18:64:2e:5b bnx2i,00:10:18:64:2e:5b, > > > 10.10.77.66,, > > > bnx2i.00:10:18:64:98:bb bnx2i,00:10:18:64:98:bb, > > > 10.10.77.65,, > > > bnx2i.00:22:19:68:3a:08 bnx2i,00:22:19:68:3a: > > > 08,10.10.77.64,, > > > bnx2i.00:10:18:64:98:b9 bnx2i, > > > 00:10:18:64:98:b9,10.10.77.63,, > > > > Only four of them are connected to the SAN. How to figure out which hw- > > > adress belongs to which interface? > > > Start the iscsi service (or at least make sure bnx2i is loaded) then run: > > > [r...@meanminna kernel]# iscsiadm -m host -P 1 > > Host Number: 8 > > State: running > > Transport: bnx2i > > Initiatorname: > > IPaddress: > > HWaddress: 00:10:18:15:fd:f1 > > Netdev: eth1 > > > You can see the network device the iscsi offload interface is attached > > to (in this case eth1), and you can see the MAC/hwaddress for the iscsi > > interface. > > > > Is bnx2i driver supported for RHEL5.5? > > > Yes. > > > > Is there a more detailed description for setting up such an > > > environment as the RedHat manuals? > > > Section 5.1.2 Setting up a iface for a iSCSI offload card of the iscsi > > readme in /usr/share/docs/iscsi-initiator-utils-$VERSION/README- Zitierten > > Text ausblenden - > > > - Zitierten Text anzeigen -- Zitierten Text ausblenden - > > > - Zitierten Text anzeigen - > > Hi Mike, > > Trying to connect to the EQL box there are no messagese at all. > > On these oracle related boxes we use the oracle linux kernel. We do > not use oracle linux vm. > Are there any issues with this kernel and iscsi? > > I have downloaded the update and will install and test with this > release, I will come back to you with the results. > > All storage IPs are on the same subnet 10.10.77.00. The EQL box > listens to 10.10.77.10. > > Kind regards > Michael- Zitierten Text ausblenden - > > - Zitierten Text anzeigen - With the new iscsi-initiator-utils set up, I now can connect to the target. I have set up two bnx2i ports with IP`s 63 and 64: [r...@ora-db-rac1-04 ~]# iscsiadm -m iface default tcp iser iser bnx2i.00:22:19:68:3a:04 bnx2i,00:22:19:68:3a: 04,,, bnx2i.00:22:19:68:3a:0a bnx2i,00:22:19:68:3a:0a, 10.10
Re: Confirm that bnx2i iSCSI offload works for RHEL 5.5 on DELL EqualLogic
On 25 Aug., 02:14, Mike Christie wrote: > On 08/24/2010 10:13 AM, Michael Wolf wrote: > > > > > > > Hi ALL, > > > I try to set up oracle cluster with four nodes (DELL R610) and > > EqualLogig PS6000. > > Servers has four Broadcom 5709C dual network cards, two intenal, two > > PCI cards. > > I`m trying to get the bnx2i driver to work using iSCSI offload for > > four channels. > > I can't get it to work, getting error > > iscsiadm: Could not login to [iface: bnx2i.00:22:19:68:3a:04, target: > > iqn.2001-05.com.equallogic:0-8a0906-76c630e04-e0492d35ddc63f-a1test, > > portal: 10.10.77.10,3260): > > iscsiadm: initiator reported error (4 - encountered connection > > failure) > > > Showing nothing in /var/log/messages and no events on the EQ box. > > So there is no iferror error in messages or nothing from iscsid? > > > DELL suport team is not shure if bnx2i driver will work with RHEL 5.5, > > they ask me to reinstall RHEL 5.2, from my opinion is that not an > > option. > > I am using RHEL 5.5, oracle linux, kernel 2.6.18-194.11.1.0.1.el5 on > > Is that a oracle linux kernel or the rhel 5.5 one? Are you running rhel > 5.5 in a oracle linux vm? > > > x86_64 > > iscsi-initiator-utils-6.2.0.871-0.16.el5 > > Also you need the updated iscsi > utils.http://people.redhat.com/mchristi/iscsi/rhel5.6/iscsi-initiator-utils/ > > > All firmware of the R610 is up to date > > > All interfaces are shown as bnx2i > > [r...@ora-db-rac1-04 ~]# scsiadm -m iface > > -bash: scsiadm: command not found > > [r...@ora-db-rac1-04 ~]# iscsiadm -m iface > > default tcp > > iser iser > > bnx2i.00:22:19:68:3a:04 bnx2i,00:22:19:68:3a: > > 04,10.10.77.69,, > > Are these IPs on the same subnet as the network port they are attached to? > > > > > > > bnx2i.00:22:19:68:3a:0a bnx2i,00:22:19:68:3a:0a, > > 10.10.77.68,, > > bnx2i.00:00:00:00:00:00 bnx2i, > > 00:00:00:00:00:00,,, > > bnx2i.00:22:19:68:3a:06 bnx2i,00:22:19:68:3a: > > 06,10.10.77.67,, > > bnx2i.00:10:18:64:2e:5b bnx2i,00:10:18:64:2e:5b, > > 10.10.77.66,, > > bnx2i.00:10:18:64:98:bb bnx2i,00:10:18:64:98:bb, > > 10.10.77.65,, > > bnx2i.00:22:19:68:3a:08 bnx2i,00:22:19:68:3a: > > 08,10.10.77.64,, > > bnx2i.00:10:18:64:98:b9 bnx2i, > > 00:10:18:64:98:b9,10.10.77.63,, > > > Only four of them are connected to the SAN. How to figure out which hw- > > adress belongs to which interface? > > Start the iscsi service (or at least make sure bnx2i is loaded) then run: > > [r...@meanminna kernel]# iscsiadm -m host -P 1 > Host Number: 8 > State: running > Transport: bnx2i > Initiatorname: > IPaddress: > HWaddress: 00:10:18:15:fd:f1 > Netdev: eth1 > > You can see the network device the iscsi offload interface is attached > to (in this case eth1), and you can see the MAC/hwaddress for the iscsi > interface. > > > Is bnx2i driver supported for RHEL5.5? > > Yes. > > > Is there a more detailed description for setting up such an > > environment as the RedHat manuals? > > Section 5.1.2 Setting up a iface for a iSCSI offload card of the iscsi > readme in /usr/share/docs/iscsi-initiator-utils-$VERSION/README- Zitierten > Text ausblenden - > > - Zitierten Text anzeigen -- Zitierten Text ausblenden - > > - Zitierten Text anzeigen - Hi Mike, Trying to connect to the EQL box there are no messagese at all. On these oracle related boxes we use the oracle linux kernel. We do not use oracle linux vm. Are there any issues with this kernel and iscsi? I have downloaded the update and will install and test with this release, I will come back to you with the results. All storage IPs are on the same subnet 10.10.77.00. The EQL box listens to 10.10.77.10. Kind regards 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.
Confirm that bnx2i iSCSI offload works for RHEL 5.5 on DELL EqualLogic
Hi ALL, I try to set up oracle cluster with four nodes (DELL R610) and EqualLogig PS6000. Servers has four Broadcom 5709C dual network cards, two intenal, two PCI cards. I`m trying to get the bnx2i driver to work using iSCSI offload for four channels. I can't get it to work, getting error iscsiadm: Could not login to [iface: bnx2i.00:22:19:68:3a:04, target: iqn.2001-05.com.equallogic:0-8a0906-76c630e04-e0492d35ddc63f-a1test, portal: 10.10.77.10,3260): iscsiadm: initiator reported error (4 - encountered connection failure) Showing nothing in /var/log/messages and no events on the EQ box. DELL suport team is not shure if bnx2i driver will work with RHEL 5.5, they ask me to reinstall RHEL 5.2, from my opinion is that not an option. I am using RHEL 5.5, oracle linux, kernel 2.6.18-194.11.1.0.1.el5 on x86_64 iscsi-initiator-utils-6.2.0.871-0.16.el5 All firmware of the R610 is up to date All interfaces are shown as bnx2i [r...@ora-db-rac1-04 ~]# scsiadm -m iface -bash: scsiadm: command not found [r...@ora-db-rac1-04 ~]# iscsiadm -m iface default tcp iser iser bnx2i.00:22:19:68:3a:04 bnx2i,00:22:19:68:3a: 04,10.10.77.69,, bnx2i.00:22:19:68:3a:0a bnx2i,00:22:19:68:3a:0a, 10.10.77.68,, bnx2i.00:00:00:00:00:00 bnx2i, 00:00:00:00:00:00,,, bnx2i.00:22:19:68:3a:06 bnx2i,00:22:19:68:3a: 06,10.10.77.67,, bnx2i.00:10:18:64:2e:5b bnx2i,00:10:18:64:2e:5b, 10.10.77.66,, bnx2i.00:10:18:64:98:bb bnx2i,00:10:18:64:98:bb, 10.10.77.65,, bnx2i.00:22:19:68:3a:08 bnx2i,00:22:19:68:3a: 08,10.10.77.64,, bnx2i.00:10:18:64:98:b9 bnx2i, 00:10:18:64:98:b9,10.10.77.63,, Only four of them are connected to the SAN. How to figure out which hw- adress belongs to which interface? Is bnx2i driver supported for RHEL5.5? Is there a more detailed description for setting up such an environment as the RedHat manuals? I am searching for the best way to figure out he reason for the connect failures? Thanks for any helping hand. -- 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.
