HP NC532m Dual Port 10GbE Multifunction BL-c Adapter - Manual (Page 7)

Installation and configuration 7
If an old version of the package exists, the RPM package should be removed.
# rpm -e netxtreme2
5. Verify that the old netxtreme2 package has been removed as follows:
# rpm -q netxtreme2
6. Verify if a old version of bnx2 or bnx2x is loaded into the kernel and remove it, if needed, as
follows:
If you are installing the package over the network, it is not necessary to remove the modules. This
step is only necessary if you are doing the upgrade on the physical console and you want the new
drivers to take over immediately.
#lsmod | grep bnx2x
#lsmod | grep bnx2
7. Before removing the drivers, bring down the interfaces controlled by bnx2x and bnx2.
#ifconfig eth<n> down
8. Remove the drivers.
#rmmod bnx2x
#rmmod bnx2
9. Install the new RPM package. This installs bnx2/bnx2x and cnic drivers. Do not use the U (Upgrade)
flag in the RPM command below--previous netxtreme2 packages must be removed as described
above before installing this version.
#rpm -ivh RPMS/<arch>/netxtreme2-<version>.<arch>.rpm
The bnx2.ko, bnx2x.ko and cnic.ko modules are installed in the following directory:
Red Hat EL 4/5 installations:
/lib/modules/<kernel_version>/updates
SLES 9/10 installations:
/lib/modules/<kernel_version>/updates
10. Configure your network setting and address. See your Linux vendor documentation for more
information. Helpful network configuration tools such as "yast2" in SLES or linuxconf/redhat-config-
network/netconfig in Red Hat exist for easy configuration.
11. Ensure that the /etc/modules.conf file is configured similar to the example listed below. The example
below is presented as if more than one adapter is present. If so, one eth# instance should exist for
each ethernet port. See the modules.conf man page for more information.
If you have a 1Gb Network card use bnx2 below otherwise use bnx2x for 10Gb.
alias eth0 bnx2
alias eth1 bnx2
For SLES, the configuration file is /etc/modprobe.conf or /etc/modprobe.conf.local
12. You can now reboot your server or restart the network services. Upon reboot the network should start
with either bnx2 or bnx2x driver loaded.
To verify that the driver is loaded use the following command.
# lsmod
You should find bnx2 or bnx2x listed. You can also verify that the correct bnx2 or bnx2x driver is
loaded through any of the following methods. Note that version of the driver loaded should be same
as that of the package version.
Installing the Linux iSCSI offload bnx2i driver
The Linux iSCSI offload bnx2i driver is released in a source RPM format.