CentOS 5.5 update NIC Driver bnx2 version: 2.0.2

Operating System: CentOS release 5.5 (Final)

Fault description: The NIC is automatically down for no reason. It does not take long for the NIC to automatically go down after restart using the service network restart. The number of connections is about 200, without arp attacks;

Nic information:
Root@www.bkjia.com ~ # Cat/var/log/dmesg | grep eth0
Eth0: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem d6000000, IRQ 90, node addr 842b2bfac367

Current NIC Driver:
Root@www.bkjia.com ~ # Ethtool-I eth0
Driver: bnx2
Version: 2.0.2
Firmware-version: 5.2.3 NCSI 2.0.10
Bus-info:. 0

Download the latest NIC Driver:
Http://www.broadcom.com/support/ethernet_nic/netxtremeii.php

Install the update driver:
Root@www.bkjia.com ~ # Unzip linux-7.4.27.zip
Archive: linux-7.4.27.zip
Creating: Server/Linux/Driver/
Inflating: Server/Linux/Driver/INSTALL. TXT
Inflating: Server/Linux/Driver/netxtreme2-7.4.27-1.src.rpm
Inflating: Server/Linux/Driver/netxtreme2-7.4.27.tar.gz
Inflating: Server/Linux/Driver/netxtreme2_sup-7.4.27-1.ISO.tar.gz
Inflating: Server/Linux/Driver/README. bnx2.TXT
Inflating: Server/Linux/Driver/README. bnx2fc. TXT
Inflating: Server/Linux/Driver/README. bnx2i. TXT
Inflating: Server/Linux/Driver/README. bnx2x. TXT
Inflating: Server/Linux/Driver/RELEASE. bnx2.TXT
Inflating: Server/Linux/Driver/RELEASE. bnx2fc. TXT
Inflating: Server/Linux/Driver/RELEASE. bnx2i. TXT
Inflating: Server/Linux/Driver/RELEASE. bnx2x. TXT
Inflating: Server/Linux/Driver/RELEASE. fclibs. TXT

Root@www.bkjia.com ~ # Cd Server/Linux/Driver/
Root@www.bkjia.com Driver # rpm-ivh netxtreme2-7.4.27-1.src.rpm

Re-create the rpm package for the corresponding system:

[Root@www.bkjia.com Driver] # cd/usr/src/RedHat/SPECS/
[Root@www.bkjia.com SPECS] # rpmbuild-bb netxtreme2.spec

Install the new rmp package:
[Root@www.bkjia.com SPECS] # cd/usr/src/redhat/RPMS/x86_64
[Root@www.bkjia.com x86_64] # rpm-ivh netxtreme2-7.4.27-1.x86_64.rpm


Switch NIC Driver:
Root@www.bkjia.com ~ # Cat change_driver.sh
Rmmod bnx2
Rmmod bnx2x
Modprobe bnx2

Modprobe bnx2x

Root@www.bkjia.com ~ # Chmod u + x change_driver.sh


Script Execution in the background:

Root@www.bkjia.com ~ #./Change_driver.sh &

Note: Sometimes you may need to restart the server so that the server system can load the new driver completely again:

 

 

View the new NIC driver information:

Root@www.bkjia.com ~ # Ethtool-I eth0

Driver: bnx2
Version: 2.2.3f
Firmware-version: 6.2.12 bc 5.2.3 NCSI 2.0.11
Bus-info:. 0

 

No automatic down occurs currently.




Note: Check INSTALL. TXT carefully before installation.
As follows:
[Root@www.bkjia.com Driver] # cat INSTALL. TXT
Installation Notes
Broadcom NetXtremeII Linux Drivers
09/26/2011

Broadcom Corporation
5300 California Boulevard,
Irvine, CA 92617

Copyright (c) 2004-2011 Broadcom Corporation
All rights reserved

Table of Contents
========================

Introduction
Limitations
Packaging
Installing Source RPM Package
Building Driver From TAR File
Unloading and Removing Driver

Introduction
================

This file describes the installation procedures for the following
Broadcom Linux drivers:

-Bnx2 driver for the Broadcom NetXtreme II BCM5706/BCM5708/5709/5716
10/100/1000/2500/10000 Mbps PCIX/PCIE Ethernet Network Controller.

-Bnx2x driver for the Broadcom NetXtremeII BCM57710/BCM57711/BCM57711E/BCM57712
10/100/1000/2500/10000 Mbps PCIE Ethernet Network Controller.

-Cnic driver that supports additional features required by the bnx2i iSCSI
Offload driver, and bnx2fc FCoE offload driver.

Limitations
==============

The current versions of the drivers have been tested on 2.4.x kernels starting
From 2.4.24 and all 2.6.x kernels. The driver may not compile on kernels
Older than 2.4.24. Testing is concentrated on i386 and x86_64 ubuntures.
Only limited testing has been done on some other ubuntures.

Minor changes to some source files and Makefile may be needed on some
Kernels.

Additionally, the Makefile will not compile the cnic driver on kernels
Older than 2.6.16. iSCSI offload is only supported on 2.6.16 and newer
Kernels. FCoE offload is only supported on 2.6.32 and newer kernels.

Packaging
==========

The driver is released in two packaging formats: source RPM and compressed tar
Formats. The file name for the source RPM is:

Netxtreme2-<version>. src. rpm

The file name for the tar archive is:
Netxtreme2-<version> .tar.gz.

Identical source files to build the drivers are supported in both packages.

Following is a list of files stored ded-

A) netxtreme2-<version>. src. rpm-NetXtreme II L2/cnic/bnx2fc/libfc/libfcoe
Driver source RPM
B) netxtreme2-<version> .tar.gz-tar zipped NetXtreme II
L2/cnic/bnx2fc/libfc/libfcoe driver source
C) INSTALL. TXT-This file
D) README. <driver>. TXT-driver specific readme instructions,
Where driver is bnx2, bnx2x, bnx2i, bnx2fc.
E) RELEASE. <driver>. TXT-release information text providing list of bug fixes
And enhancement for each driver.

Installing Source RPM Package
==================================

The following are general guidelines for installing the driver.

1. Install the source RPM package:

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

2. CD to the RPM path and build the binary driver for your kernel:

Cd/usr/src/{redhat, OpenLinux, turbo, packages, rpm ..}
(For RHEL 6.0 and above, cd ~ /Rpmbuild)

Rpm-bb SPECS/netxtreme2.spec

Or

Rpmbuild-bb SPECS/netxtreme2.spec (for RPM version 4.x. x)

Note that the RPM path is different for different Linux distributions.

The driver will be compiled for the running kernel by default. To build
The driver for a kernel different than the running one, specify
Kernel by defining it in KVER:

Rpmbuild-bb SPECS/netxtreme2.spec -- define "KVER <kernel version>"

Where <kernel version> in the form of 2. x. y-z is the version of another
Kernel that is installed on the system.

3. Install the newly built package (driver and man page ):

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

Where <arch> is the machine architecture such as i386:

Rpm-ivh RPMS/i386/netxtreme2-<version>. i386.rpm

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

The drivers will be installed in the following path:

2.4.x kernels:

/Lib/modules/<kernel_version>/kernel/drivers/net/bnx2.o
/Lib/modules/<kernel_version>/kernel/drivers/net/bnx2x. o

2.6.0 kernels:

/Lib/modules/<kernel_version>/kernel/drivers/net/bnx2.ko
/Lib/modules/<kernel_version>/kernel/drivers/net/bnx2x. ko

2.6.16 and newer kernels:

/Lib/modules/<kernel_version>/kernel/drivers/net/bnx2.ko
/Lib/modules/<kernel_version>/kernel/drivers/net/bnx2x. ko
/Lib/modules/<kernel_version>/kernel/drivers/net/cnic. ko

Newer RHEL and SLES distros:

/Lib/modules/<kernel_version>/updates/bnx2.ko
/Lib/modules/<kernel_version>/updates/cnic. ko
/Lib/modules/<kernel_version>/updates/bnx2x. ko
/Lib/modules/<kernel_version>/updates/bnx2i. ko
/Lib/modules/<kernel_version>/updates/bnx2fc. ko

4. Unload existing driver if necessary:

Rmmod bnx2
Rmmod bnx2x

If the cnic driver is loaded, it shoshould also be unloaded along with dependent
Drivers:

Rmmod bnx2fc
Rmmod bnx2i
Rmmod cnic

5. Load the bnx2 driver for the BCM5706/BCM5708/5709/5716 devices:

Insmod bnx2.o
Or
Insmod bnx2.ko (on 2.6.x kernels)
Or
Modprobe bnx2

To load the bnx2x driver for the BCM57710/BCM57711/BCM57711E/BCM57712 devices:

Insmod bnx2x. o
Or
Insmod bnx2x. ko (on 2.6.x kernels)
Or
Modprobe bnx2x

To load the cnic driver:

Insmod cnic. ko
Or
Modprobe cnic

To load the bnx2i driver:

Insmod bnx2i. ko
Or
Modprobe bnx2i
Service iscsid restart (Please refer REDAME.bnx2i.txt for more details
About iSCSI operation)

To load the bnx2fc driver for BCM57712 device:

Insmod bnx2fc. ko
Or
Modprobe bnx2fc
Service fcoe start (Please refer README.bnx2fc.txt for more details about
FCoE operation)

Note that the inbox kernel may have an older version of bnx2, bnx2x and cnic
Driver. It is important for FCoE offload user to unload these inbox versions
Before attempting to load bnx2fc driver. There are 2 options to reach
Desired goal,
A) Reboot the server
OR
B) If already loaded, unload inbox bnx2, bnx2x, cnic drivers and load newly
Installed version from netxtreme2-foce package using 'modprobe <DRV-NAME>'

NOTE: Driver upgrade (rpm-Uvh) is not supported.
NOTE: On SLES 11, change "allow_unsupported_modules" parameter value
/Etc/modprobe. d/unsupport-modules 'from 0 to 1, until bnx2fc driver
Is inbox. Failing to do so will not load bnx2fc.

6. To configure network protocol and address, refer to various Linux
Documentations.

Building Driver From TAR File
==================================

The following are general guidelines for installing the driver.

1. Create a directory and extract the files:

Tar xvzf netxtreme2-<version> .tar.gz

2. Build the drivers as a loadable module for the running kernel:

Make

The driver will be compiled for the running kernel by default. To build
The driver for a kernel different than the running one, specify
Kernel by defining it in KVER:

Make KVER = <kernel version>

Where <kernel version> in the form of 2. x. y-z is the version of another
Kernel that is installed on the system.

3. Test the driver by loading it (Same procedures as described in
Source RPM section above ).

4. Install the driver and man page:

Make install

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

5. To configure network protocol and address, refer to various Linux
Documentations.

Unloading and Removing Driver
==================================

If the driver was installed using rpm, do the following to remove it:

Rpm-e nextreme2

Note-this will remove libfc2, libfcoe2, bnx2, bnx2x and cnic modules as well

If the driver was installed using make install from the tar file, the drivers
Have to be manually deleted from the system. Refer to the section
"Installing Source RPM Package" for the location of the installed driver.

1. rmmod <driver>

2. delete <driver>. ko from location given in section "Installing Source RPM Package"

3. depmod-

** The kernel will now be back to original state prior to instalation from tar file.
You may now reload previous module versions if necessary.

Recommended reading:

How to install the ESXi 5.0 U1 NIC driver on the DELL PowerEdge R720

RHEL6.4 install the Broadcom BCM4313 wireless NIC Driver

Install the BCM4313 wireless NIC Driver in 64-bit CentOS 6.4