Hmm... somehow that got removed. I've rebuilt the system (I'm setting up new hardware fortunately) and am back to trying it out again. Just for background, I'm testing out on a Dell R610 with 4 onboard nics (no iscsi offload enabled) and 4 broadcom nics pci-e cards with iscsi offload enabled.
I think I'm missing a basic step here.. but it feels close. 1. Installed CentOS 5.5 + updates, w/ iscsi-initiator-utils-6.2.0.871-0.18.el5 on x86_64 machine. 2. eth0 is set to 10.1.3.20 IP address 3. eth4 is set to 10.1.4.30 (MAC Address:00:10:18:6A:E4:78) 4. Lefthand iscsi is setup on 10.1.4.10 5. I set up /var/lib/iscsi/ifaces/bnx2i.00:10:18:6a:e4:79 with the following content # BEGIN RECORD 2.0-871 iface.iscsi_ifacename = bnx2i.00:10:18:6a:e4:79 iface.hwaddress = 00:10:18:6a:e4:79 iface.ipaddress = 10.1.4.31 iface.transport_name = bnx2i # END RECORD 6. iscsiadm -m discovery -t st -I bnx2i.00:10:18:6a:e4:79 -p 10.1.4.10 returns 10.1.4.10:3260,1 iqn.2003-10.com.lefthandnetworks:rally-qd:104:testbnxvol Cool.. looks like I've found the LUN. I think this uses the eth4 device here, not the bnx2i Trying to login.. iscsiadm -m node -l -P 1 Logging in to [iface: bnx2i.00:10:18:6a:e4:79, target: iqn.2003-10.com.lefthandnetworks:rally-qd:104:testbnxvol, portal: 10.1.4.10,3260] iscsiadm: Could not login to [iface: bnx2i.00:10:18:6a:e4:79, target: iqn.2003-10.com.lefthandnetworks:rally-qd:104:testbnxvol, portal: 10.1.4.10,3260]: iscsiadm: initiator reported error (4 - encountered connection failure) in /var/log/messages.. Jul 12 16:21:01 qd-db-01 iscsid: Received iferror -1 Jul 12 16:21:01 qd-db-01 iscsid: cannot make a connection to 10.1.4.10:3260(-1,11) And I can't ping 10.1.4.31, but I'm not sure if that is expected or not. I assume that I should not be setting anything up in the Broadcom setup for iSCSI. I guess I'm assuming that is for iSCSI boot which I don't want or need for now. But maybe I'm wrong? It's happened on plenty of occasions. Note: Using TCP for iscsi works. I.e. the following commands work great: iscsiadm -m discovery -t st -p 10.1.4.10 iscsiadm -m node -l Any ideas? Tarun P.S. Relevant lspci: 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) 01:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) 02:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) 04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) 05:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) On Mon, Jul 12, 2010 at 2:40 PM, Benjamin Li <[email protected]> wrote: > Hi Tarun, > > Is the ipv6 kernel module loaded? The missing symbols > ('__ipv6_addr_type' and 'ip6_route_output') reported by cnic are > resolved by loading the ipv6.ko module > > The path to that module on RHEL 5.5 is > > /lib/modules/2.6.18-194.el5/kernel/net/ipv6/ipv6.ko > > Is the modules.dep file stale? You can regenerate this via the command > 'depmod -a' which should allow the automatic loading of module > dependencies. > > Thanks again. > > -Ben > > On Mon, 2010-07-12 at 13:25 -0700, Tarun Reddy wrote: > > > > > > On Mon, Jul 12, 2010 at 2:25 PM, Tarun Reddy <[email protected]> wrote: > > Sigh... trying again with out much success. Running stock 5.5 > > system+iscsi-initiator-utils from below (194.3.1 kernel) > > > > > > So I upgraded my kernel 194.8.1 and I get this message in > > dmesg when doing a modprobe bnx2i: > > > > > > cnic: Unknown symbol __ipv6_addr_type > > cnic: Unknown symbol ip6_route_output > > > > > > Reboot back into 194.3.1... > > > > > > And I still get this error. Any ideas? I've reverted > > iscsi-initiator as well.. > > > > > > > > > > > > > > > > > > On Sun, Jul 11, 2010 at 4:32 AM, Mike Christie > > <[email protected]> wrote: > > On 06/10/2010 08:30 PM, Benjamin Li wrote: > > Hi Tarun, > > > > I think the bug which most likely matched what > > you were seeing was > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=572596 > > > > This is where the iscsid and uIP daemon were > > not synchronized when the > > uIP stack was coming up and iscsid didn't wait > > for uIP to fullly > > initialized. > > > > From that bugzilla we have generated > > patches for iscsid and uIP which > > resulted in the following bugzilla > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=595549 > > > > Where the patches will go into the next > > version of iscsi-initator-utils. > > > > Please let me know if there are any questions > > or concerns. > > > > > > > > Here are some rpms that we are testing here. > > > http://people.redhat.com/mchristi/iscsi/rhel5.6/iscsi-initiator-utils/ > > > > > > > > Sorry... should have bottom posted. > > > > > > Tarun > > > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
