Re: Centos 5.4 bnx2i iscsi woes
Sorry for the duplicate email Eddie. I'm not used to gmail's interface just yet. On Thu, Jul 15, 2010 at 3:49 PM, Eddie Wai w...@broadcom.com wrote: Hello Kai, FYI, the bnx2i: iSCSI not supported message indicates that the port associated with eth3 is not licensed to do iSCSI offload. Echoing Mike's question, are you getting this message on all the ethXs that you intend to do iSCSI offload? I get the same message on all of the ethXs, even the ones that we do not intend to do iSCSI offloading. I was not aware there was a licensing issue to deal with here. Should I be addressing this with Dell then? Eddie -Original Message- From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com] On Behalf Of Mike Christie Sent: Thursday, July 15, 2010 2:05 PM To: open-iscsi@googlegroups.com Cc: Kai Meyer Subject: Re: Centos 5.4 bnx2i iscsi woes On 07/15/2010 11:57 AM, Kai Meyer wrote: Just to make sure, you are using something like kernel version 2.6.18-194.8.1? Yes, 2.6.18-194.8.1.el5 Are you getting this no supported error on the other ethXs? Yes, see above response to Eddie Wai When using iscsi_tcp are you using iface binding and with that do you still have to do tricks with the routing tables and ARP? Are doing binding by iscsi iface hw address/MAC or by the vlan (iscsi iface iface.net_ifacename = ethX.Y setting)? When using iscsi_tcp, we are basically leaving all iscsi settings to default (whatever the iscsi and iscsid services default to.) The routing tricks I was talking about are implemented in /etc/rc.local, like so: --- . /etc/sysconfig/network- scripts/ifcfg-eth2 eval `ipcalc -n -p $IPADDR $NETMASK` ip route add $NETWORK/$PREFIX dev $DEVICE tab 2 ip rule add from $IPADDR/32 tab 2 priority 200 . /etc/sysconfig/network-scripts/ifcfg-eth3 eval `ipcalc -n -p $IPADDR $NETMASK` ip route add $NETWORK/$PREFIX dev $DEVICE tab 3 ip rule add from $IPADDR/32 tab 3 priority 300 ip route flush cache --- and in /etc/sysctl.conf, we added the following two lines: net.ipv4.conf.all.arp_ignore=1 net.ipv4.conf.all.arp_announce=2 These changes are intended to ensure that inbound traffic to a specific ethX device is responded to out the same interface it was received on, instead of the first route in the routing table, as well as to ensure that the ARP requests are only responded to on the interface that the physical mac address is on (with out the sysctl rules, eth3 will respond to arps for eth2's mac). From what it sounds like, I should be asking Dell if we are licensed to use the iSCSI offloader? -Kai Meyer -- 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: Centos 5.4 bnx2i iscsi woes
The first time I login to the bnx2i interface after reboot, it works. Subsequent times fails. Here is my /var/log/messages for first and second time Jul 16 14:47:13 qd-db-01 kernel: ip_conntrack version 2.4 (8192 buckets, 65536 max) - 304 bytes per conntrack Jul 16 14:47:13 qd-db-01 kernel: bnx2: eth0: using MSIX Jul 16 14:47:13 qd-db-01 kernel: bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex Jul 16 14:47:13 qd-db-01 kernel: bnx2: eth4: using MSIX Jul 16 14:47:13 qd-db-01 kernel: bnx2: eth4 NIC Copper Link is Up, 1000 Mbps full duplex Jul 16 14:47:13 qd-db-01 kernel: ipmi message handler version 39.1 Jul 16 14:47:19 qd-db-01 puppetd[5289]: Finished catalog run in 7.48 seconds Jul 16 14:48:31 qd-db-01 kernel: NET: Registered protocol family 10 Jul 16 14:48:31 qd-db-01 kernel: lo: Disabled Privacy Extensions Jul 16 14:48:31 qd-db-01 kernel: IPv6 over IPv4 tunneling driver Jul 16 14:49:02 qd-db-01 iscsid: iscsid shutting down. Jul 16 14:49:02 qd-db-01 kernel: Loading iSCSI transport class v2.0-871. Jul 16 14:49:02 qd-db-01 kernel: cxgb3i: tag itt 0x1fff, 13 bits, age 0xf, 4 bits. Jul 16 14:49:02 qd-db-01 kernel: iscsi: registered transport (cxgb3i) Jul 16 14:49:02 qd-db-01 kernel: Broadcom NetXtreme II CNIC Driver cnic v2.1.0 (Oct 10, 2009) Jul 16 14:49:02 qd-db-01 kernel: cnic: Added CNIC device: eth0 Jul 16 14:49:02 qd-db-01 kernel: cnic: Added CNIC device: eth1 Jul 16 14:49:02 qd-db-01 kernel: cnic: Added CNIC device: eth2 Jul 16 14:49:02 qd-db-01 kernel: cnic: Added CNIC device: eth3 Jul 16 14:49:02 qd-db-01 kernel: cnic: Added CNIC device: eth4 Jul 16 14:49:02 qd-db-01 kernel: cnic: Added CNIC device: eth5 Jul 16 14:49:02 qd-db-01 kernel: cnic: Added CNIC device: eth6 Jul 16 14:49:02 qd-db-01 kernel: cnic: Added CNIC device: eth7 Jul 16 14:49:02 qd-db-01 kernel: Broadcom NetXtreme II iSCSI Driver bnx2i v2.1.0 (Dec 06, 2009) Jul 16 14:49:02 qd-db-01 kernel: iscsi: registered transport (bnx2i) Jul 16 14:49:02 qd-db-01 kernel: scsi3 : Broadcom Offload iSCSI Initiator Jul 16 14:49:02 qd-db-01 kernel: scsi4 : Broadcom Offload iSCSI Initiator Jul 16 14:49:02 qd-db-01 kernel: scsi5 : Broadcom Offload iSCSI Initiator Jul 16 14:49:02 qd-db-01 kernel: scsi6 : Broadcom Offload iSCSI Initiator Jul 16 14:49:04 qd-db-01 kernel: scsi7 : Broadcom Offload iSCSI Initiator Jul 16 14:49:04 qd-db-01 kernel: scsi8 : Broadcom Offload iSCSI Initiator Jul 16 14:49:04 qd-db-01 kernel: scsi9 : Broadcom Offload iSCSI Initiator Jul 16 14:49:04 qd-db-01 kernel: scsi10 : Broadcom Offload iSCSI Initiator Jul 16 14:49:06 qd-db-01 kernel: iscsi: registered transport (tcp) Jul 16 14:49:06 qd-db-01 kernel: iscsi: registered transport (iser) Jul 16 14:49:06 qd-db-01 kernel: iscsi: registered transport (be2iscsi) Jul 16 14:49:06 qd-db-01 iscsid: iSCSI logger with pid=6631 started! Jul 16 14:49:07 qd-db-01 iscsid: transport class version 2.0-871. iscsid version 2.0-871 Jul 16 14:49:07 qd-db-01 iscsid: iSCSI daemon with pid=6632 started! Jul 16 14:49:07 qd-db-01 iscsid: Could not broadcast to uIP after 3 tries Jul 16 14:49:11 qd-db-01 last message repeated 4 times Jul 16 14:49:12 qd-db-01 iscsid: Received iferror -1 Jul 16 14:49:12 qd-db-01 iscsid: cannot make a connection to 10.1.4.10:3260(-1,11) Jul 16 14:49:15 qd-db-01 kernel: bnx2i [04:00.00]: ISCSI_INIT passed Jul 16 14:49:15 qd-db-01 kernel: connection1:0: detected conn error (1011) Jul 16 14:49:16 qd-db-01 kernel: bnx2i [04:00.00]: ISCSI_INIT passed Jul 16 14:49:21 qd-db-01 kernel: bnx2i [04:00.00]: ISCSI_INIT passed Jul 16 14:49:22 qd-db-01 kernel: connection1:0: detected conn error (1011) Jul 16 14:49:22 qd-db-01 kernel: bnx2i [04:00.00]: ISCSI_INIT passed Jul 16 14:49:23 qd-db-01 kernel: connection1:0: bnx2i: conn update - MBL 0x10 FBL 0x4MRDSL_I 0x4 MRDSL_T 0x4 Jul 16 14:49:23 qd-db-01 kernel: connection1:0: bnx2i: iscsi_warning - invalid TTT Jul 16 14:49:23 qd-db-01 kernel: Vendor: LEFTHAND Model: iSCSIDisk Rev: 8500 Jul 16 14:49:23 qd-db-01 kernel: Type: Direct-Access ANSI SCSI revision: 05 Jul 16 14:49:23 qd-db-01 kernel: SCSI device sdb: 20971520 512-byte hdwr sectors (10737 MB) Jul 16 14:49:23 qd-db-01 kernel: sdb: Write Protect is off Jul 16 14:49:23 qd-db-01 kernel: SCSI device sdb: drive cache: none Jul 16 14:49:23 qd-db-01 kernel: SCSI device sdb: 20971520 512-byte hdwr sectors (10737 MB) Jul 16 14:49:23 qd-db-01 kernel: sdb: Write Protect is off Jul 16 14:49:23 qd-db-01 kernel: SCSI device sdb: drive cache: none Jul 16 14:49:23 qd-db-01 kernel: sdb: unknown partition table Jul 16 14:49:23 qd-db-01 kernel: sd 6:0:0:0: Attached scsi disk sdb Jul 16 14:49:23 qd-db-01 kernel: sd 6:0:0:0: Attached scsi generic sg4 type 0 Jul 16 14:49:23 qd-db-01 iscsid: connection1:0 is operational now Jul 16 14:49:23 qd-db-01 iscsid: Could not write to /sys/bus/scsi/devices/6:0:0:0/queue_depth. Invalid permissions. Jul 16 14:49:23 qd-db-01 iscsid: Could not queue depth for LUN 0 err 13. Jul 16 14:49:42 qd-db-01 kernel: connection1:0: received itt 0
Re: Centos 5.4 bnx2i iscsi woes
Same error with M610 and rh el 5.5 x86_64 connected with EQL PS6010XV. -- 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: Centos 5.4 bnx2i iscsi woes
Hello, I have the same problem. HW is M610 with RH EL 5.5 x86_64 updated (kernel 2.6.18-194.8.1). I'm connected with an EQL PS6010XV through 10Gbs adapters on the blade sw iSCSI works with and without multipath. Same problems with iSCSI offload. Tried also installing version 6.2.0.871-0.18.el5 without success. Latest steps: - disable iscsi/iscsid at startup - stop iscsid - update iscsi-initiator-utils - shutdown -r - clean /var/lib/iscsi from previous configs: cd /var/lib/iscsi rm -rf nodes/* rm -rf send_targets/* # ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:10:18:58:E8:F8 inet addr:10.10.100.178 Bcast:10.10.100.255 Mask: 255.255.255.0 inet6 addr: fe80::210:18ff:fe58:e8f8/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:1025 errors:0 dropped:0 overruns:0 frame:0 TX packets:50 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:104130 (101.6 KiB) TX bytes:4700 (4.5 KiB) Interrupt:82 Memory:dc80-dcff # ifconfig eth1 eth1 Link encap:Ethernet HWaddr 00:10:18:58:E8:FA inet addr:10.10.100.179 Bcast:10.10.100.255 Mask: 255.255.255.0 inet6 addr: fe80::210:18ff:fe58:e8fa/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:1014 errors:0 dropped:0 overruns:0 frame:0 TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:83638 (81.6 KiB) TX bytes:630 (630.0 b) Interrupt:90 Memory:dd80-ddff # cat ifaces/bnx2i.00:10:18:58:e8:f9 # BEGIN RECORD 2.0-871 iface.iscsi_ifacename = bnx2i.00:10:18:58:e8:f9 iface.ipaddress = 10.10.100.198 iface.hwaddress = 00:10:18:58:e8:f9 iface.transport_name = bnx2i # END RECORD # cat ifaces/bnx2i.00:10:18:58:e8:fb # BEGIN RECORD 2.0-871 iface.iscsi_ifacename = bnx2i.00:10:18:58:e8:fb iface.ipaddress = 10.10.100.199 iface.hwaddress = 00:10:18:58:e8:fb iface.transport_name = bnx2i # END RECORD # service iscsid start Starting iSCSI daemon: [ OK ] [ OK ] # iscsiadm -m discovery -t st -p 10.10.100.30:3260 -I bnx2i. 00:10:18:58:e8:fb -I bnx2i.00:10:18:58:e8:f9 -P 1 Target: iqn.2001-05.com.equallogic:0-8a0906-97d4b5e06-59600264bc83- blg9-vol3 Portal: 10.10.100.30:3260,1 Iface Name: bnx2i.00:10:18:58:e8:f9 Iface Name: bnx2i.00:10:18:58:e8:fb Target: iqn.2001-05.com.equallogic:0-8a0906-8904b5e06-b6600204bc83- blg9-vol1 Portal: 10.10.100.30:3260,1 Iface Name: bnx2i.00:10:18:58:e8:f9 Iface Name: bnx2i.00:10:18:58:e8:fb Target: iqn.2001-05.com.equallogic:0-8a0906-94c4b5e06-df900234bc83- blg9-vol2 Portal: 10.10.100.30:3260,1 Iface Name: bnx2i.00:10:18:58:e8:f9 Iface Name: bnx2i.00:10:18:58:e8:fb # iscsiadm -m node --loginall=all the command show suddenly the first successful line, then stays there for about three minutes and at the end shows the remaining successfull one and the failed ones. Complete output of the command: Logging in to [iface: bnx2i.00:10:18:58:e8:f9, target: iqn. 2001-05.com.equallogic:0-8a0906-97d4b5e06-59600264bc83-blg9-vol3, portal: 10.10.100.30,3260] Logging in to [iface: bnx2i.00:10:18:58:e8:fb, target: iqn. 2001-05.com.equallogic:0-8a0906-97d4b5e06-59600264bc83-blg9-vol3, portal: 10.10.100.30,3260] Logging in to [iface: bnx2i.00:10:18:58:e8:f9, target: iqn. 2001-05.com.equallogic:0-8a0906-8904b5e06-b6600204bc83-blg9-vol1, portal: 10.10.100.30,3260] Logging in to [iface: bnx2i.00:10:18:58:e8:fb, target: iqn. 2001-05.com.equallogic:0-8a0906-8904b5e06-b6600204bc83-blg9-vol1, portal: 10.10.100.30,3260] Logging in to [iface: bnx2i.00:10:18:58:e8:f9, target: iqn. 2001-05.com.equallogic:0-8a0906-94c4b5e06-df900234bc83-blg9-vol2, portal: 10.10.100.30,3260] Logging in to [iface: bnx2i.00:10:18:58:e8:fb, target: iqn. 2001-05.com.equallogic:0-8a0906-94c4b5e06-df900234bc83-blg9-vol2, portal: 10.10.100.30,3260] Login to [iface: bnx2i.00:10:18:58:e8:f9, target: iqn. 2001-05.com.equallogic:0-8a0906-97d4b5e06-59600264bc83-blg9-vol3, portal: 10.10.100.30,3260]: successful iscsiadm: Could not login to [iface: bnx2i.00:10:18:58:e8:fb, target: iqn.2001-05.com.equallogic:0-8a0906-97d4b5e06-59600264bc83-blg9- vol3, portal: 10.10.100.30,3260]: iscsiadm: initiator reported error (8 - connection timed out) iscsiadm: Could not login to [iface: bnx2i.00:10:18:58:e8:f9, target: iqn.2001-05.com.equallogic:0-8a0906-8904b5e06-b6600204bc83-blg9- vol1, portal: 10.10.100.30,3260]: iscsiadm: initiator reported error (4 - encountered connection failure) iscsiadm: Could not login to [iface: bnx2i.00:10:18:58:e8:fb, target: iqn.2001-05.com.equallogic:0-8a0906-8904b5e06-b6600204bc83-blg9- vol1, portal: 10.10.100.30,3260]: iscsiadm:
Re: Centos 5.4 bnx2i iscsi woes
On 07/15/2010 11:57 AM, Kai Meyer wrote: We are experiencing nearly exactly the same issues as the original poster. We are fully updated RHEL 5.5, including the iscsi-initiator- Just to make sure, you are using something like kernel version 2.6.18-194.8.1? utils-6.2.0.871-0.18.el5 posted earlier in the list (http:// people.redhat.com/mchristi/iscsi/rhel5.6/iscsi-initiator-utils/) We are on a Dell Blade M610 with a Quad 1GB NIC + iscsi offloader mezzanine card. We're using the physical interfaces eth2 and eth3, and would like to add Multipath into the mix once iSCSI is worked out. We can use the 1GB connections on eth2 and eth3 to connect, login, and do anything we want, so we thought it would be worthwhile to switch to the iscsi offloader. During boot, we see these messages a lot: ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready bnx2i: iSCSI not supported, dev=eth3 Are you getting this no supported error on the other ethXs? Then much later, when iscsi starts, we get: Broadcom NetXtreme II iSCSI Driver bnx2i v2.1.0 (Dec 06, 2009) iscsi: registered transport (bnx2i) scsi6 : Broadcom Offload iSCSI Initiator scsi7 : Broadcom Offload iSCSI Initiator scsi8 : Broadcom Offload iSCSI Initiator scsi9 : Broadcom Offload iSCSI Initiator scsi10 : Broadcom Offload iSCSI Initiator scsi11 : Broadcom Offload iSCSI Initiator iscsi: registered transport (tcp) iscsi: registered transport (iser) iscsi: registered transport (be2iscsi) We are basing our selection of iscsi offloading nics by their HW address: eth0 Link encap:Ethernet HWaddr 00:26:B9:FA:10:38 inet addr:172.20.1.1 Bcast:172.20.15.255 Mask: 255.255.240.0 eth1 Link encap:Ethernet HWaddr 00:26:B9:FA:10:3A eth2 Link encap:Ethernet HWaddr 00:23:AE:F9:38:74 inet addr:172.20.17.1 Bcast:172.20.31.255 Mask: 255.255.240.0 eth3 Link encap:Ethernet HWaddr 00:23:AE:F9:38:76 inet addr:172.20.18.1 Bcast:172.20.31.255 Mask: 255.255.240.0 eth4 Link encap:Ethernet HWaddr 00:23:AE:F9:38:78 eth5 Link encap:Ethernet HWaddr 00:23:AE:F9:38:7A # iscsiadm -m iface default tcp,empty,empty,empty,empty iser iser,empty,empty,empty,empty bnx2i.00:23:ae:f9:38:79 bnx2i, 00:23:ae:f9:38:79,empty,empty,empty bnx2i.00:26:b9:fa:10:3b bnx2i,00:26:b9:fa: 10:3b,empty,empty,empty bnx2i.00:23:ae:f9:38:77 bnx2i, 00:23:ae:f9:38:77,172.20.20.1,empty,empty bnx2i.00:26:b9:fa:10:39 bnx2i,00:26:b9:fa: 10:39,empty,empty,empty bnx2i.00:23:ae:f9:38:75 bnx2i, 00:23:ae:f9:38:75,172.20.19.1,empty,empty bnx2i.00:23:ae:f9:38:7b bnx2i, 00:23:ae:f9:38:7b,empty,empty,empty We are guessing (bnx2i.00:23:ae:f9:38:75 == eth2) and (bnx2i. 00:23:ae:f9:38:77 == eth3), which is only important because of the VLan configuration. iscsiadm -m iface -I bnx2i.00:23:ae:f9:38:75 # BEGIN RECORD 2.0-871 iface.iscsi_ifacename = bnx2i.00:23:ae:f9:38:75 iface.net_ifacename =empty iface.ipaddress = 172.20.19.1 iface.hwaddress = 00:23:ae:f9:38:75 iface.transport_name = bnx2i iface.initiatorname =empty # END RECORD iscsiadm -m iface -I bnx2i.00:23:ae:f9:38:77 # BEGIN RECORD 2.0-871 iface.iscsi_ifacename = bnx2i.00:23:ae:f9:38:77 iface.net_ifacename =empty iface.ipaddress = 172.20.20.1 iface.hwaddress = 00:23:ae:f9:38:77 iface.transport_name = bnx2i iface.initiatorname =empty # END RECORD Send Targets works just fine, here's the result of one of the targets I got back: iscsiadm -m node -I bnx2i.00:23:ae:f9:38:75 -T iqn. 2001-05.com.equallogic:0-8a0906-db234b706-9e70001687b4c378-008513 -p 172.20.16.14 # BEGIN RECORD 2.0-871 node.name = iqn.2001-05.com.equallogic:0-8a0906- db234b706-9e70001687b4c378-008513 node.tpgt = 1 node.startup = automatic iface.hwaddress = 00:23:ae:f9:38:75 iface.ipaddress = 172.20.19.1 iface.iscsi_ifacename = bnx2i.00:23:ae:f9:38:75 iface.net_ifacename =empty iface.transport_name = bnx2i iface.initiatorname =empty node.discovery_address = 172.20.16.14 node.discovery_port = 3260 node.discovery_type = send_targets node.session.initial_cmdsn = 0 node.session.initial_login_retry_max = 8 node.session.xmit_thread_priority = -20 node.session.cmds_max = 1024 node.session.queue_depth = 128 node.session.auth.authmethod = CHAP node.session.auth.username = chap1 node.session.auth.password = node.session.auth.username_in =empty node.session.auth.password_in =empty node.session.timeo.replacement_timeout = 120 node.session.err_timeo.abort_timeout = 15 node.session.err_timeo.lu_reset_timeout = 20 node.session.err_timeo.host_reset_timeout = 60 node.session.iscsi.FastAbort = Yes node.session.iscsi.InitialR2T = No node.session.iscsi.ImmediateData = Yes node.session.iscsi.FirstBurstLength = 262144 node.session.iscsi.MaxBurstLength = 16776192 node.session.iscsi.DefaultTime2Retain = 0 node.session.iscsi.DefaultTime2Wait = 2 node.session.iscsi.MaxConnections = 1 node.session.iscsi.MaxOutstandingR2T = 1 node.session.iscsi.ERL = 0 node.conn[0].address = 172.20.16.14 node.conn[0].port = 3260 node.conn[0].startup = manual
Re: Centos 5.4 bnx2i iscsi woes
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 micha...@cs.wisc.edu 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/ -- 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: Centos 5.4 bnx2i iscsi woes
On Mon, Jul 12, 2010 at 2:25 PM, Tarun Reddy tar...@gmail.com 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 micha...@cs.wisc.eduwrote: 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 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: Centos 5.4 bnx2i iscsi woes
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 tar...@gmail.com 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
micha...@cs.wisc.edu 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 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: Centos 5.4 bnx2i iscsi woes
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 be...@broadcom.com 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 tar...@gmail.com 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
micha...@cs.wisc.edu 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
Re: Centos 5.4 bnx2i iscsi woes
On 07/12/2010 05:26 PM, Tarun Reddy wrote: 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 Yes. That is expected. We will use the offload engine for discovery in the next version. 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) Are there some bnx2i messages in /var/log/messages and could you send them too? Also what is the Centos 5.5 kernel version? -- 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: Centos 5.4 bnx2i iscsi woes
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/ -- 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: Centos 5.4 bnx2i iscsi woes
Ben, Mike, Is there a RedHat bug covered by this? I've searched and the closest I see is https://bugzilla.redhat.com/show_bug.cgi?id=578005 but that seems to indicate that a service network restart would be a workaround. I'm not seeing that work for me. Thank you, Tarun On Mon, May 24, 2010 at 3:16 PM, Benjamin Li be...@broadcom.com wrote: Hi Mike, I don't have a version of brcm_iscsiuio which I have readily avaliable for 5.5.z which has the fix you are looking for without adding new features. I will need to create a version of brcm_iscsiuio with the iscsid/brcm_iscsiuio backported for 5.5.z. When does this need to be accomplished? Thanks again. -Ben On Mon, 2010-05-24 at 14:05 -0700, Mike Christie wrote: On 05/21/2010 07:35 PM, Tarun Reddy wrote: Mike, So is there any update to this? It seems to fix the problem in RHEL 6 testing. http://people.redhat.com/mchristi/iscsi/rhel6.0/iscsi-initiator-utils/ (I think the rhel6 init scripts will not work with RHEL5 perfectly). Ben, did you have a brcm release you wanted me to use for a 5.5.z release (the 5.5.z should not have new features as you know so I could not use the brcm release I used in the RHEL 6 realease). -- 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: Centos 5.4 bnx2i iscsi woes
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. Thanks again. -Ben On Thu, 2010-06-10 at 15:30 -0700, Tarun Reddy wrote: Ben, Mike, Is there a RedHat bug covered by this? I've searched and the closest I see is https://bugzilla.redhat.com/show_bug.cgi?id=578005 but that seems to indicate that a service network restart would be a workaround. I'm not seeing that work for me. Thank you, Tarun On Mon, May 24, 2010 at 3:16 PM, Benjamin Li be...@broadcom.com wrote: Hi Mike, I don't have a version of brcm_iscsiuio which I have readily avaliable for 5.5.z which has the fix you are looking for without adding new features. I will need to create a version of brcm_iscsiuio with the iscsid/brcm_iscsiuio backported for 5.5.z. When does this need to be accomplished? Thanks again. -Ben On Mon, 2010-05-24 at 14:05 -0700, Mike Christie wrote: On 05/21/2010 07:35 PM, Tarun Reddy wrote: Mike, So is there any update to this? It seems to fix the problem in RHEL 6 testing. http://people.redhat.com/mchristi/iscsi/rhel6.0/iscsi-initiator-utils/ (I think the rhel6 init scripts will not work with RHEL5 perfectly). Ben, did you have a brcm release you wanted me to use for a 5.5.z release (the 5.5.z should not have new features as you know so I could not use the brcm release I used in the RHEL 6 realease). -- 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: Centos 5.4 bnx2i iscsi woes
Hi Mike, I don't have a version of brcm_iscsiuio which I have readily avaliable for 5.5.z which has the fix you are looking for without adding new features. I will need to create a version of brcm_iscsiuio with the iscsid/brcm_iscsiuio backported for 5.5.z. When does this need to be accomplished? Thanks again. -Ben On Mon, 2010-05-24 at 14:05 -0700, Mike Christie wrote: On 05/21/2010 07:35 PM, Tarun Reddy wrote: Mike, So is there any update to this? It seems to fix the problem in RHEL 6 testing. http://people.redhat.com/mchristi/iscsi/rhel6.0/iscsi-initiator-utils/ (I think the rhel6 init scripts will not work with RHEL5 perfectly). Ben, did you have a brcm release you wanted me to use for a 5.5.z release (the 5.5.z should not have new features as you know so I could not use the brcm release I used in the RHEL 6 realease). -- 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: Centos 5.4 bnx2i iscsi woes
Mike, So is there any update to this? Thank you, Tarun On Wed, May 5, 2010 at 9:42 AM, Mike Christie micha...@cs.wisc.edu wrote: On 04/29/2010 04:44 AM, Oliver Hookins wrote: I believe I'm hitting the exact same error... pity. Any word on the fix? I believe they have a fix. It is being tested now. -- 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.comopen-iscsi%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en. -- 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: Centos 5.4 bnx2i iscsi woes
I am trying to do the same thing and am seeing very similar behavior. I have a brand new HP DL 360 G6 with Broadcom HP nc382i dual-port 1GB NIC. Software iSCSI works fine but I am cannot get hardware iSCSI to work. I defined an iface0-HW as seen below: [r...@snd-testg6a ifaces]# cat iface0-HW # BEGIN RECORD 2.0-871 iface.iscsi_ifacename = iface0-HW iface.ipaddress = 10.30.40.80 iface.hwaddress = f4:ce:46:B9:49:2d iface.transport_name = bnx2i # END RECORD When I try and login, I see the following: Setting up iSCSI targets: Logging in to [iface: iface0-HW, target: iqn. 1986-03.com.hp:storage.p2000g3.0939da0280, portal: 10.30.40.78,3260] Logging in to [iface: iface0-HW, target: iqn. 1986-03.com.hp:storage.p2000g3.0939da0280, portal: 10.30.40.79,3260] Logging in to [iface: iface0-HW, target: iqn. 1986-03.com.hp:storage.p2000g3.0939da0280, portal: 10.30.40.76,3260] Logging in to [iface: iface0-HW, target: iqn. 1986-03.com.hp:storage.p2000g3.0939da0280, portal: 10.30.40.77,3260] iscsiadm: Could not login to [iface: iface0-HW, target: iqn. 1986-03.com.hp:storage.p2000g3.0939da0280, portal: 10.30.40.78,3260]: iscsiadm: initiator reported error (12 - iSCSI driver not found. Please make sure it is loaded, and retry the operation) iscsiadm: Could not login to [iface: iface0-HW, target: iqn. 1986-03.com.hp:storage.p2000g3.0939da0280, portal: 10.30.40.79,3260]: iscsiadm: initiator reported error (12 - iSCSI driver not found. Please make sure it is loaded, and retry the operation) iscsiadm: Could not login to [iface: iface0-HW, target: iqn. 1986-03.com.hp:storage.p2000g3.0939da0280, portal: 10.30.40.76,3260]: iscsiadm: initiator reported error (12 - iSCSI driver not found. Please make sure it is loaded, and retry the operation) iscsiadm: Could not login to [iface: iface0-HW, target: iqn. 1986-03.com.hp:storage.p2000g3.0939da0280, portal: 10.30.40.77,3260]: iscsiadm: initiator reported error (12 - iSCSI driver not found. Please make sure it is loaded, and retry the operation) iscsiadm: Could not log into all portals. Err 12. I've installed all the latest drivers and firmware. lsmod shows the modules loaded too: [r...@snd-testg6a ifaces]# lsmod |egrep -i bnx|scsi bnx2i 102944 0 cnic 75288 1 bnx2i iscsi_tcp 50509 4 libiscsi_tcp 53317 2 cxgb3i,iscsi_tcp libiscsi2 77125 5 ib_iser,bnx2i,cxgb3i,iscsi_tcp,libiscsi_tcp scsi_transport_iscsi274073 7 ib_iser,bnx2i,cxgb3i,iscsi_tcp,libiscsi2 scsi_transport_iscsi35017 1 scsi_transport_iscsi2 scsi_dh41665 1 dm_multipath bnx2 219404 0 scsi_mod 196697 10 ib_iser,bnx2i,cxgb3i,sg,iscsi_tcp,libiscsi2,scsi_transport_iscsi2,scsi_dh,cciss,sd_mod I am thinking this could be similiar behavior to what you are seeing? On May 5, 11:42 am, Mike Christie micha...@cs.wisc.edu wrote: On 04/29/2010 04:44 AM, Oliver Hookins wrote: I believe I'm hitting the exact same error... pity. Any word on the fix? I believe they have a fix. It is being tested now. -- 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 athttp://groups.google.com/group/open-iscsi?hl=en. -- 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: Centos 5.4 bnx2i iscsi woes
On 05/05/2010 02:57 PM, Nate Salemme wrote: I am trying to do the same thing and am seeing very similar behavior. Your problem is completely different. I have a brand new HP DL 360 G6 with Broadcom HP nc382i dual-port 1GB NIC. Software iSCSI works fine but I am cannot get hardware iSCSI to work. I defined an iface0-HW as seen below: [r...@snd-testg6a ifaces]# cat iface0-HW # BEGIN RECORD 2.0-871 iface.iscsi_ifacename = iface0-HW iface.ipaddress = 10.30.40.80 iface.hwaddress = f4:ce:46:B9:49:2d iface.transport_name = bnx2i # END RECORD When I try and login, I see the following: Setting up iSCSI targets: Logging in to [iface: iface0-HW, target: iqn. 1986-03.com.hp:storage.p2000g3.0939da0280, portal: 10.30.40.78,3260] Logging in to [iface: iface0-HW, target: iqn. 1986-03.com.hp:storage.p2000g3.0939da0280, portal: 10.30.40.79,3260] Logging in to [iface: iface0-HW, target: iqn. 1986-03.com.hp:storage.p2000g3.0939da0280, portal: 10.30.40.76,3260] Logging in to [iface: iface0-HW, target: iqn. 1986-03.com.hp:storage.p2000g3.0939da0280, portal: 10.30.40.77,3260] iscsiadm: Could not login to [iface: iface0-HW, target: iqn. 1986-03.com.hp:storage.p2000g3.0939da0280, portal: 10.30.40.78,3260]: iscsiadm: initiator reported error (12 - iSCSI driver not found. Please make sure it is loaded, and retry the operation) We do not even get to the connection/login phase like the other bug reporters did. In your case it is complaining that bnx2i is not loaded, but from the info below it looks like it is. Are you using RHEL or Centos? If so, how did you start the iscsi system and what is the iscsi-initiator-utils version? Did you do service iscsi start or was the iscsi service started for you? Try starting it by hand: // stop the iscsi service so we can start from scratch # service iscsi stop // make sure that the record has the bnx2i driver set # iscsiadm -m node -I iface0-HW | grep bnx2i // start iscsi by hand # modprobe bnx2i # iscsid # brcm_iscsi_uio // login by hand # iscsiadm -m node -I iface iface0-HW -l -- 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: Centos 5.4 bnx2i iscsi woes
On 05/06/2010 12:38 PM, Nate Salemme wrote: iscsi: registered transport (cxgb3i) iscsi: registered transport (tcp) iscsi: registered transport (iser) bnx2: eth0: using MSI iscsi: registered transport (bcm570x-02) For the bnx2i driver that comes with RHEL you should see: May 6 11:10:11 localhost kernel: iscsi: registered transport (bnx2i) The registered transport message you got above came from HP's driver. I am not sure how to configure HP's tools and driver. They are slightly different because HP's driver is older and based on a non-upstream driver that registers a transport per pci function and the RHEL/Centos/upstream driver registers a transport per driver. So for RHEL you would use bnx2i for the iface.transport_name like you did below: # BEGIN RECORD 2.0-871 iface.iscsi_ifacename = iface0-HW iface.ipaddress = 10.30.40.80 iface.hwaddress = f4:ce:46:B9:49:2d iface.transport_name = bnx2i # END RECORD But for HP's driver you probably want to set the iface.transport_name as what you see in the registered transport message in your log, bcm570x-02. I am not 100% sure what/how to config HP's stuff because I do not have the source in front of me. I am 99% sure though that just using the bnx2i name string is wrong for that driver because of how it is registering transport names. -- 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: Centos 5.4 bnx2i iscsi woes
On 04/29/2010 04:44 AM, Oliver Hookins wrote: I believe I'm hitting the exact same error... pity. Any word on the fix? I believe they have a fix. It is being tested now. -- 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: Centos 5.4 bnx2i iscsi woes
On 04/16/2010 03:15 PM, Tarun Reddy wrote: Output from /var/log/messages: Apr 16 14:12:03 dsc-loadtestdb-01 iscsid: Received iferror -1 Apr 16 14:12:03 dsc-loadtestdb-01 iscsid: cannot make a connection to 10.32.13.33:3260 (-1,11) Apr 16 14:12:05 dsc-loadtestdb-01 iscsid: Received iferror -1 Apr 16 14:12:05 dsc-loadtestdb-01 iscsid: cannot make a connection to 10.32.13.33:3260 (-1,11) Apr 16 14:12:07 dsc-loadtestdb-01 iscsid: Received iferror -1 Apr 16 14:12:07 dsc-loadtestdb-01 iscsid: cannot make a connection to 10.32.13.33:3260 (-1,11) Apr 16 14:12:09 dsc-loadtestdb-01 iscsid: Received iferror -1 Apr 16 14:12:09 dsc-loadtestdb-01 iscsid: cannot make a connection to 10.32.13.33:3260 (-1,11) I have got the card to work, but I think I am getting lucky. I think you might be hitting a race. Benjamin from Broadcom is working on a fix. I ccd him here, so when he is done we can give you some rpms to try out. -- 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.
