Centos 5.5 update NIC Driver bnx2 version: 2.0.2

Centos 5.5 update NIC Driver bnx2 version: 2.0.2 Operating System: CentOS release 5.5 (Final) fault symptom: Nic automatically goes down for no reason. It will not be long before it will be automatically down after restart using service network restart, the number of connections is about 200, no arp attack; Nic information: [root @ qs-wg-web2 ~] # Cat/var/log/dmesg | grep eth0eth0: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem d6000000, IRQ 90, node addr 842b2bfac367 current NIC Driver: [root @ qs-wg-web2 ~] # Ethtool-I eth0driver: bnx2version: 2.0.2firmware-version: 5.2.3 NCSI 2.0.10bus-info:. 0 Download latest NIC Driver: http://www.broadcom.com/support/ethernet_nic/netxtremeii.php Install update driver: [root @ qs-wg-web2 ~] # 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 @ qs-wg-web2 ~] # Cd Server/Linux/Driver/[root @ qs-wg-web2 Driver] # rpm-ivh netxtreme2-7.4.27-1.src.rpm rebuilding the rpm package for the corresponding system: [root @ qs-wg-web2 Driver] # cd/usr/src/redhat/SPECS/[root @ qs-wg-web2 SPECS] # rpmbuild-bb netxtreme2.spec install the new rmp package: [root @ qs-wg-web2 SPECS] # cd/usr/src/redhat/RPMS/x86_64 [root @ qs-wg-web2 x86_64] # rpm-ivh netxtreme2-7.4.27-1.x86_64.rpm switch NIC Driver: [root @ qs-wg-web2 ~] # Cat change_driver.sh rmmod bnx2 rmmod bnx2x modprobe bnx2 modprobe bnx2x [root @ qs-wg-web2 ~] # Chmod u + x change_driver.sh background execution Script: [root @ qs-wg-web2 ~] #./Change_driver.sh & Note: Sometimes you may need to restart the server to make the server system load the new driver completely: view the new NIC driver information: [root @ qs-wg-web2 ~] # Ethtool-I eth0driver: bnx2version: 2.2.3ffirmware-version: 6.2.12 bc 5.2.3 NCSI 2.0.11bus-info:. 0 automatic down is not found. Note: Please carefully check INSTALL before installation. TXT is as follows: [root @ qs-wg-web2 Driver] # cat INSTALL. TXT Installation Notes Broadcom NetXtremeII Linux Drivers 09/26/2011 Broadcom Corporation 5300 California Avenue, 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 unloadin G and Removing Driver Introduction ============ This file describes the installation procedures for the followingBroadcom 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 startingfrom 2.4.24 and all 2.6.x kernels. the driver may not compile on kernelsolder than 2.4.24. testing is concentrated on i386 and x86_64 ubuntures. only limited tes Ting has been done on some other ubuntures. minor changes to some source files and Makefile may be needed on somekernels. additionally, the Makefile will not compile the cnic driver on kernelsolder than 2.6.16. iSCSI offload is only supported on 2.6.16 and newerkernels. 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 tarformats. the file name for the source RPM is: netxtreme2-<version>. src. rpmThe 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 encoded-a) netxtreme2-<version>. src. rpm-NetXtreme II L2/cnic/bnx2fc/libfc/libfcoe driver source RPMb) netxtreme2-<version>. tar. Gz-tar zipped NetXtreme II L2/cnic/bnx2fc/libfc/libfcoe driver sourcec) INSTALL. TXT-This filed) 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 gu Idelines for installing the driver.1. Install the source RPM package: rpm-ivh netxtreme2-<version>. src. rpm2. 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.specor 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 buildthe driver for a kernel different than the running one, specify thekernel 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 anotherkernel that is installed on the system.3. Install the newly built package (driver and man page ): rpm-ivh RPMS/<arch>/netxtreme2-<version>. <arch>. rpmwhere <arch> is the machine architecture such as i386: rpm-ivh RPMS/i386/netxtreme2-<version>. i386.rpmNote that the -- force option may be needed on some Linux distributionsif 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. o2.6.0 kernels:/lib/modules/<kernel_version>/kernel/drivers/net/bnx2.ko/lib/modules/<kernel_version>/kernel/drivers/net/bnx2x. ko2.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. koNewer 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. ko4. Unload existing driver if necessary: rmmod bnx2 rmmod bnx2xIf the cnic driver is loaded, it shoshould also be unloaded along with dependentdrivers: rmmod bnx2fc rmmod bnx2i rmmod cnic5. Load the bnx2 driver for the BCM5706/BCM5708/5709/5716 devices: insmod bnx2.oor insmod bnx2.ko (on 2.6.x kernels) or modprobe bnx2To load the bnx2x driver for the BCM57710/BCM57711/BCM57711E/BCM57712 devices: insmod bnx2x. oor insmod bnx2x. ko (on 2.6.x kernels) or modprobe bnx2xTo load the cnic driver: insmod cnic. koor modprobe cnicTo load the bnx2i driver: insmod bnx2i. koor 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. koor 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 cnicdriver. it is important for FCoE offload user to unload these inbox versionsbefore attempting to load bnx2fc driver. there are 2 options to reach thedesired 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 of/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 Linuxdocumentations. building Driver From TAR File ========================== The following are general guidelines 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: makeThe driver will be compiled for the running kernel by default. to buildthe driver for a kernel different than the running one, specify thekernel by defining it in KVER: make KVER = <kernel version> where <kernel version> in the form of 2. x. y-z is the version of anotherkernel that is installed on the system.3. Test the driver by loading it (Same procedures as described in the Source RPM section above ). 4. install the driver and man page: make installSee RPM instructions abve for the location of the installed driver.5. To configure network protocol and address, refer to various Linuxdocumentations. unloading and Removing Driver ======================== If the driver was installed using rpm, do the following to remove it: rpm-e nextreme2Note-this will remove libfc2, libfcoe2, bnx2, bnx2x and cnic modules as wellIf the driver was installed using make install from the tar file, the drivershave 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-a ** The kernel will now be back to original state prior to instalation from tar file. you may now reload previous module versions if necessary.