Hi Tarun,

It looks like from the logs that eth0 is not iSCSI licensed but eth4 is
=)

In addition, I was also wondering if you could also post the following:

1.  The routing table of the machine.  Currently CNIC uses the L2
routine table to determine which port on the NIC to send requests to.

2.  If you could also provide the /var/log/brcm_iscsi.log file,  we can
also take a look at the Broadcom uIP user space daemon to see if
anything is wrong.  To enable deeper debugging for the brcm_iscsiuio
daemon, please modify the /etc/init.d/iscsid init script and append '-d
100' to the line which start 'brcm_iscsiuio'.  This should output all
the debug messages in the daemon.

Thanks again.

-Ben


On Fri, 2010-07-16 at 12:39 -0700, Tarun Reddy wrote:
> On Mon, Jul 12, 2010 at 9:45 PM, Mike Christie <micha...@cs.wisc.edu>
> wrote:
>         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?
> 
> 
> 
> Sorry it took me so long to get back to you.. 
> Here are all of the bnx2i messages in /var/log/messages while doing
> a /etc/init.d/iscsi restart
> 
> 
> Jul 16 13:36:00 qd-db-01 iscsid: iscsid shutting down.
> Jul 16 13:36:00 qd-db-01 kernel: cnic: Removed CNIC device: eth7
> Jul 16 13:36:00 qd-db-01 kernel: cnic: Removed CNIC device: eth6
> Jul 16 13:36:00 qd-db-01 kernel: cnic: Removed CNIC device: eth5
> Jul 16 13:36:00 qd-db-01 kernel: cnic: Removed CNIC device: eth4
> Jul 16 13:36:00 qd-db-01 kernel: cnic: Removed CNIC device: eth3
> Jul 16 13:36:00 qd-db-01 kernel: cnic: Removed CNIC device: eth2
> Jul 16 13:36:00 qd-db-01 kernel: cnic: Removed CNIC device: eth1
> Jul 16 13:36:00 qd-db-01 kernel: cnic: Removed CNIC device: eth0
> Jul 16 13:36:00 qd-db-01 kernel: Loading iSCSI transport class
> v2.0-871.
> Jul 16 13:36:00 qd-db-01 kernel: cxgb3i: tag itt 0x1fff, 13 bits, age
> 0xf, 4 bits.
> Jul 16 13:36:00 qd-db-01 kernel: iscsi: registered transport (cxgb3i)
> Jul 16 13:36:00 qd-db-01 kernel: Broadcom NetXtreme II CNIC Driver
> cnic v2.1.0 (Oct 10, 2009)
> Jul 16 13:36:00 qd-db-01 kernel: cnic: Added CNIC device: eth0
> Jul 16 13:36:00 qd-db-01 kernel: cnic: Added CNIC device: eth1
> Jul 16 13:36:00 qd-db-01 kernel: cnic: Added CNIC device: eth2
> Jul 16 13:36:00 qd-db-01 kernel: cnic: Added CNIC device: eth3
> Jul 16 13:36:00 qd-db-01 kernel: cnic: Added CNIC device: eth4
> Jul 16 13:36:00 qd-db-01 kernel: cnic: Added CNIC device: eth5
> Jul 16 13:36:00 qd-db-01 kernel: cnic: Added CNIC device: eth6
> Jul 16 13:36:00 qd-db-01 kernel: cnic: Added CNIC device: eth7
> Jul 16 13:36:00 qd-db-01 kernel: Broadcom NetXtreme II iSCSI Driver
> bnx2i v2.1.0 (Dec 06, 2009)
> Jul 16 13:36:00 qd-db-01 kernel: iscsi: registered transport (bnx2i)
> Jul 16 13:36:00 qd-db-01 kernel: scsi11 : Broadcom Offload iSCSI
> Initiator
> Jul 16 13:36:00 qd-db-01 kernel: scsi12 : Broadcom Offload iSCSI
> Initiator
> Jul 16 13:36:00 qd-db-01 kernel: scsi13 : Broadcom Offload iSCSI
> Initiator
> Jul 16 13:36:00 qd-db-01 kernel: scsi14 : Broadcom Offload iSCSI
> Initiator
> Jul 16 13:36:00 qd-db-01 kernel: scsi15 : Broadcom Offload iSCSI
> Initiator
> Jul 16 13:36:00 qd-db-01 kernel: scsi16 : Broadcom Offload iSCSI
> Initiator
> Jul 16 13:36:00 qd-db-01 kernel: scsi17 : Broadcom Offload iSCSI
> Initiator
> Jul 16 13:36:00 qd-db-01 kernel: scsi18 : Broadcom Offload iSCSI
> Initiator
> Jul 16 13:36:02 qd-db-01 kernel: iscsi: registered transport (tcp)
> Jul 16 13:36:02 qd-db-01 kernel: iscsi: registered transport (iser)
> Jul 16 13:36:02 qd-db-01 kernel: iscsi: registered transport
> (be2iscsi)
> Jul 16 13:36:02 qd-db-01 iscsid: iSCSI logger with pid=8137 started!
> Jul 16 13:36:03 qd-db-01 iscsid: transport class version 2.0-871.
> iscsid version 2.0-871
> Jul 16 13:36:03 qd-db-01 iscsid: iSCSI daemon with pid=8138 started!
> 
> 
> And the kernel is 194.8.1.
> 
> 
> Thank you,
> Tarun
> 
> 
> (Actually here is grep bnx /var/log/messages since this is a newly
> built machine and it is small)
> Jul 12 14:46:36 qd-db-01 kernel: Broadcom NetXtreme II Gigabit
> Ethernet Driver bnx2 v2.0.2 (Aug 21, 2009)
> Jul 12 14:46:38 qd-db-01 kernel: Broadcom NetXtreme II iSCSI Driver
> bnx2i v2.1.0 (Dec 06, 2009)
> Jul 12 14:46:38 qd-db-01 kernel: iscsi: registered transport (bnx2i)
> Jul 12 14:46:38 qd-db-01 kernel: bnx2: eth0: using MSIX
> Jul 12 14:46:38 qd-db-01 kernel: bnx2i: iSCSI not supported, dev=eth0
> Jul 12 14:46:38 qd-db-01 kernel: bnx2i: iSCSI not supported, dev=eth0
> Jul 12 14:46:38 qd-db-01 kernel: bnx2: eth0 NIC Copper Link is Up,
> 1000 Mbps full duplex
> Jul 12 14:54:41 qd-db-01 kernel: bnx2: eth4: using MSIX
> Jul 12 14:54:41 qd-db-01 kernel: bnx2i [04:00.00]: ISCSI_INIT passed
> Jul 12 14:54:44 qd-db-01 kernel: bnx2: eth4 NIC Copper Link is Up,
> 1000 Mbps full duplex
> Jul 12 14:55:05 qd-db-01 kernel: Broadcom NetXtreme II iSCSI Driver
> bnx2i v2.1.0 (Dec 06, 2009)
> Jul 12 14:55:05 qd-db-01 kernel: iscsi: registered transport (bnx2i)
> Jul 12 14:55:53 qd-db-01 kernel: Broadcom NetXtreme II iSCSI Driver
> bnx2i v2.1.0 (Dec 06, 2009)
> Jul 12 14:55:53 qd-db-01 kernel: iscsi: registered transport (bnx2i)
> Jul 12 15:00:08 qd-db-01 kernel: Broadcom NetXtreme II iSCSI Driver
> bnx2i v2.1.0 (Dec 06, 2009)
> Jul 12 15:00:08 qd-db-01 kernel: iscsi: registered transport (bnx2i)
> Jul 12 16:29:14 qd-db-01 kernel: Broadcom NetXtreme II iSCSI Driver
> bnx2i v2.1.0 (Dec 06, 2009)
> Jul 12 16:29:14 qd-db-01 kernel: iscsi: registered transport (bnx2i)
> Jul 12 16:29:22 qd-db-01 kernel: bnx2i [04:00.00]: ISCSI_INIT passed
> Jul 12 16:29:34 qd-db-01 kernel: bnx2i [04:00.00]: ISCSI_INIT passed
> Jul 12 17:07:20 qd-db-01 kernel: Broadcom NetXtreme II Gigabit
> Ethernet Driver bnx2 v2.0.2 (Aug 21, 2009)
> Jul 12 17:07:23 qd-db-01 kernel: bnx2: eth0: using MSIX
> Jul 12 17:07:23 qd-db-01 kernel: bnx2: eth0 NIC Copper Link is Up,
> 1000 Mbps full duplex
> Jul 16 13:35:38 qd-db-01 kernel: Broadcom NetXtreme II iSCSI Driver
> bnx2i v2.1.0 (Dec 06, 2009)
> Jul 16 13:35:38 qd-db-01 kernel: iscsi: registered transport (bnx2i)
> Jul 16 13:36:00 qd-db-01 kernel: Broadcom NetXtreme II iSCSI Driver
> bnx2i v2.1.0 (Dec 06, 2009)
> Jul 16 13:36:00 qd-db-01 kernel: iscsi: registered transport (bnx2i)
> 
> 
> 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.

Reply via email to