I agree that I am getting a different error message. The reason I responded to the thread was that it looked like others were having trouble getting HW iSCSI working on Centos 5.4 using bnx2i.
> Are you using RHEL or Centos? If so, how did you start the iscsi system > and what is the iscsi-initiator-utils version? Using Centos 5.4. iscsi was started as a service (/etc/init.d/iscsi restart.) As for the version, I've tried both current upstream yum version and the version provided on HP's website. The version I am running now is the HP version. [r...@snd-testg6a ~]# rpm -qa |grep iscsi iscsi-initiator-utils-6.2.0.871-0.12.el5_4.1 The upstream version is SLIGHTLY older. iscsi-initiator-utils-6.2.0.871-0.10.el5 > 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 > Yes I am using service. Running iscsiadm -m node -I iface0-HW | grep bnx2i confirms that node connections are using the bnx2i transport. I tried running the commands above to login manually. Still cannot find the driver. What versions of the driver are you using and which Broadcom NIC card do you have? Since you say your system is working, do you mind pasting the relevant parts of dmesg when the iSCSI driver is loaded so I can compare my dmesg? I've included mine below for reference. Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.0.8c (Mar 31, 2010) GSI 20 sharing vector 0x82 and IRQ 20 ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 31 (level, low) -> IRQ 130 PCI: Setting latency timer of device 0000:02:00.0 to 64 eth0: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f8000000, IRQ 130, node addr f4:ce:46:b9:49:2c GSI 21 sharing vector 0x8A and IRQ 21 ACPI: PCI Interrupt 0000:02:00.1[B] -> GSI 39 (level, low) -> IRQ 138 PCI: Setting latency timer of device 0000:02:00.1 to 64 eth1: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f6000000, IRQ 138, node addr f4:ce:46:b9:49:2e shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Floppy drive(s): fd0 is 1.44M floppy0: no floppy controllers found Floppy drive(s): fd0 is 1.44M floppy0: no floppy controllers found lp: driver loaded but no devices found ACPI: Power Button (FF) [PWRF] md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. device-mapper: multipath: version 1.0.5 loaded EXT3 FS on dm-0, internal journal kjournald starting. Commit interval 5 seconds EXT3 FS on cciss/c0d0p1, internal journal EXT3-fs: mounted filesystem with ordered data mode. SELinux: initialized (dev cciss/c0d0p1, type ext3), uses xattr SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs Adding 200146936k swap on /dev/VolGroup01/LogVol01. Priority:-1 extents:1 across:200146936k SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts IA-32 Microcode Update Driver: v1.14a <[email protected]> Broadcom NetXtreme II CNIC Driver cnic v1.9.13b (Dec 16, 2009) cnic: Added CNIC device: eth0 cnic: Added CNIC device: eth1 Loading iSCSI transport class v2.0-871. Broadcom NetXtreme II iSCSI Driver bnx2i v1.8.12f (Jan 19, 2010) 802.1Q VLAN Support v1.8 Ben Greear <[email protected]> All bugs added by David S. Miller <[email protected]> cxgb3i: tag itt 0x1fff, 13 bits, age 0xf, 4 bits. iscsi: registered transport (cxgb3i) iscsi: registered transport (tcp) iscsi: registered transport (iser) bnx2: eth0: using MSI iscsi: registered transport (bcm570x-020000) bnx2i: netif=eth0, iscsi=bcm570x-020000 bnx2i [02:00.00]: ISCSI_INIT passed bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON bnx2: eth0 NIC Copper Link is Down bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON scsi0 : iSCSI Initiator over TCP/IP scsi1 : iSCSI Initiator over TCP/IP scsi2 : iSCSI Initiator over TCP/IP scsi3 : iSCSI Initiator over TCP/IP Vendor: HP Model: P200<5> Vendor: HP Model: P2000G3 FC/iSCSI Rev: T100 Thanks. On May 6, 12:54 pm, Mike Christie <[email protected]> wrote: > 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 [email protected]. > To unsubscribe from this group, send email to > [email protected]. > 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 [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.
