I NSTALLING L INUX D RIVER S OFTWARE

• Installing the Source RPM Package

• Building the Driver from the Source TAR File

NOTE: If a bnx2/bnx2x/bnx2i driver is loaded and the Linux kernel is updated, the driver module must be recompiled if the driver module was installed using the source RPM or the TAR package.

I

S

RPM P

The following are guidelines for installing the driver source RPM Package.

Prerequisites:

• Linux kernel source

• C compiler Procedure:

1. Install the source RPM package:

rpm -ivh netxtreme2-<version>.src.rpm

2. Change the directory to the RPM path and build the binary RPM for your kernel:

For RHEL: 3. Install the newly compiled RPM:

rpm -ivh RPMS/<arch>/netxtreme2-<version>.<arch>.rpm

Note that the --force option may be needed on some Linux distributions if conflicts are reported.

4. Install open-fcoe utility.

For RHEL 6.4 and legacy versions, either of the following:

yum install fcoe-utils-<version>.rhel.64.brcm.<subver>.<arch>.rpm

-or-rpm -ivh fcoe-utils-<version>.rhel.64.brcm.<subver>.<arch>.-or-rpm For SLES11 SP2:

rpm -ivh open-fcoe-<version>.sles.sp1.brcm.<subver>.<arch>.rpm

For RHEL 6.4 and SLES11 SP2 and legacy versions, the version of fcoe-utils/open-fcoe included in your distribution is sufficient and no out of box upgrades are provided.

Where available, installation with yum will automatically resolve dependencies. Otherwise, required dependencies can be located on your O/S installation media.

Bro a d c o m Co rp o r a ti o n

Document INGSRVT78-CDUM100-R Installing Linux Driver Software Page 147

5. For SLES, turn on the fcoe and lldpad services.

For SLES11 SP1:

6. Inbox drivers are included with all of the supported operating systems. The simplest means to ensure the newly installed drivers are loaded is to reboot.

7. After rebooting, create configuration files for all FCoE ethX interfaces:

cd /etc/fcoe

cp cfg-ethx cfg-<ethX FCoE interface name>

NOTE: Note that your distribution might have a different naming scheme for Ethernet devices. (i.e., pXpX or emX instead of ethX).

8. Modify /etc/fcoe/cfg-<interface> by setting DCB_REQUIRED=yes to DCB_REQUIRED=no.

9. Turn on all ethX interfaces.

ifconfig <ethX> up

10. For SLES, use YaST to configure your Ethernet interfaces to automatically start at boot by setting a static IP address or enabling DHCP on the interface.

11. Disable lldpad on Broadcom CNA interfaces. This is required because Broadcom utilizes an offloaded DCBX client.

lldptool set-lldp –i <ethX> adminStatus=disasbled

12. Make sure /var/lib/lldpad/lldpad.conf is created and each <ethX> block does not specify “adminStatus” or if specified, it is set to 0 (“adminStatus=0”) as below.

lldp :

13. Restart lldpad service to apply new settings For SLES11 SP1, RHEL 6.4 and legacy versions:

service lldpad restart For SLES11 SP2:

rclldpad restart

14. Restart fcoe service to apply new settings

For SLES11 SP1, RHEL 6.4, and legacy versions:

service fcoe restart For SLES11 SP2:

Bro a d c o m C o rp o r a ti o n

Page 148 Installing Linux Driver Software Document INGSRVT78-CDUM100-R

rcfcoe restart

I

KMP P

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

1. Install the KMP package:

rpm -ivh <file>

rmmod bnx2x 2. Load the driver

Bro a d c o m Co rp o r a ti o n

Document INGSRVT78-CDUM100-R Installing Linux Driver Software Page 149

B

D

S

TAR F

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

1. Create a directory and extract the TAR files to the directory:

tar xvzf netxtreme2-version.tar.gz

2. Build the driver bnx2.ko (or bnx2.o) as a loadable module for the running kernel:

cd netxtreme2-version make

3. Test the driver by loading it (first unload the existing driver, if necessary):

rmmod bnx2 insmod bnx2.o

modprobe crc32 && insmod bnx2.o or, for Linux 2.6 kernels:

rmmod bnx2 insmod bnx2.ko

Verify that your network adapter supports iSCSI by checking the message log. If the message “bnx2i: dev eth0 does not support iSCSI” appears in the message log after loading the bnx2i driver, then iSCSI is not supported. This message may not appear until the interface is opened, as with:

ifconfig eth0 up

4. Load the cnic driver (if applicable):

insmod cnic.ko

5. Install the driver and man page:

make install

NOTE: See the RPM instructions above for the location of the installed driver.

6. Install the user daemon (brcm_iscsiuio).

Refer to Load and Run Necessary iSCSI Software Components for instructions on loading the software components required to use the Broadcom iSCSI offload feature.

To configure the network protocol and address after building the driver, refer to the manuals supplied with your operating system.

Verify that your network adapter supports iSCSI by checking the message log. If the message “bnx2i: dev eth0 does not support iSCSI” appears in the message log after loading the bnx2i driver, then iSCSI is not supported. This message may not appear until the interface is opened, as with:

ifconfig eth0 up

Bro a d c o m C o rp o r a ti o n

Page 150 Load and Run Necessary iSCSI Software Components Document INGSRVT78-CDUM100-R