Bnx2 and bnx2x driver, Bnx2i driver – Dell Broadcom NetXtreme Family of Adapters User Manual

Page 36

Advertising
background image

Linux Driver Software: Broadcom NetXtreme II® Network Adapter User Guide

file:///C|/Users/Nalina_N_S/Documents/NetXtremeII/English/linux.htm[9/5/2014 3:45:01 PM]

<level> to control the level at which messages appear on the console. Most systems are set to level 6 by default. To see all
messages, set the level higher.

bnx2 and bnx2x Driver
bnx2i Driver

bnx2 and bnx2x Driver

NOTE: The examples used in this procedure refer to the bnx2 driver, but also apply to the bnx2x driver.

Driver Sign on

Broadcom NetXtreme II Gigabit Ethernet Driver
bnx2 v1.6.3c (July 23, 2007)

CNIC Driver Sign on (bnx2 only)

Broadcom NetXtreme II cnic v1.1.19 (Sep 25, 2007)

NIC Detected

eth#: Broadcom NetXtreme II BCM5708 1000Base-T (B0)
PCI-X 64-bit 133MHz found at mem f6000000, IRQ 16, node addr 0010180476ae
cnic: Added CNIC device: eth0

Link Up and Speed Indication

bnx2: eth# NIC Link is Up, 1000 Mbps full duplex

Link Down Indication

bnx2: eth# NIC Link is Down

MSI enabled successfully (bnx2 only)

bnx2: eth0: using MSI

MSI-X enabled successfully (bnx2x only)

bnx2x: eth0: using MSI-X

bnx2i Driver

BNX2I Driver signon

Broadcom NetXtreme II iSCSI Driver bnx2i v2.1.1D (May 12, 2010)

Network port to iSCSI transport name binding

bnx2i: netif=eth2, iscsi=bcm570x-050000
bnx2i: netif=eth1, iscsi=bcm570x-030c00

Driver completes handshake with iSCSI offload-enabled CNIC device

bnx2i [05:00.00]: ISCSI_INIT passed

NOTE: This message is displayed only when the user attempts to make an iSCSI connection.

Driver detects iSCSI offload is not enabled on the CNIC device

bnx2i: iSCSI not supported, dev=eth3
bnx2i: bnx2i: LOM is not enabled to offload iSCSI connections, dev=eth0
bnx2i: dev eth0 does not support iSCSI

Exceeds maximum allowed iSCSI connection offload limit

bnx2i: alloc_ep: unable to allocate iscsi cid
bnx2i: unable to allocate iSCSI context resources

Network route to target node and transport name binding are two different devices

bnx2i: conn bind, ep=0x... ($ROUTE_HBA) does not belong to hba $USER_CHOSEN_HBA

where ROUTE_HBA --> net device on which connection was offloaded based on route information USER_CHOSEN_HBA -->
HBA to which target node is bound (using iscsi transport name)

Advertising