FILE NAME: hp-mlnx-en-1.4.2-1.src.rpm TITLE: HP NC-Series Mellanox 10GbE Driver for Linux VERSION: 1.4.2 RELEASE: 1 LANGUAGE: English CATEGORY: Software Solutions DIVISIONS: Enterprise and Mainstream Servers PRODUCTS AFFECTED: HP NC542m Dual Port Flex-10 10GbE BL-c Adapter OPERATING SYSTEM: Red Hat Enterprise Linux 5 AS/ES for AMD64/EM64T Red Hat Enterprise Linux 5 AS/ES for x86 Red Hat Enterprise Linux 4 AS/ES for AMD64/EM64T Red Hat Enterprise Linux 4 AS/ES for x86 SUSE LINUX Enterprise Server 11 for AMD64/EM64T SUSE LINUX Enterprise Server 11 for x86 SUSE LINUX Enterprise Server 10 for AMD64/EM64T SUSE LINUX Enterprise Server 10 for x86 PREREQUISITES: ProLiant server supporting one of the above operating systems 2GB RAM minimum Latest HP System ROM NOTE: Visit the following URL to download the latest System ROM http://welcome.hp.com/country/us/en/support.html Select "Download drivers and software (and firmware)" EFFECTIVE DATE: 11/16/2009 SUPERSEDES: Initial Release DESCRIPTION: This RPM contains the HP Tested and Approved Linux mlx4_en driver for use with the Mellanox 10Gig Ethernet Adapter Cards ENHANCEMENTS/FIXES: Table of Contents ================= Introduction Packaging Build Environment Setup Installing the RPM Package Uninstalling the RPM Package Caveat Limitations Introduction ============ This file describes the Linux driver for the HP Mellanox Server Adapters mentioned in the PRODUCTS AFFECTED section. After installation additional information can be found in the MAN page for mlx4_en User guides and additional HP Network Adapter information can be found at: http://h18004.www1.hp.com/products/servers/networking/index-nic.html Packaging ========= The driver is released in a source RPM format. The file name for the package is hp-mlnx-en-.src.rpm You should have the right build environment to compile a binary from the source package. See the "Build Environment Setup" Section below Build Environment Setup ======================== hp-mlnx-en requires the presence of some packages that provide the right build environment. These packages provide kernel headers, makefiles and symbol files, though the last one is suggested only on SLES distributions. Red Hat installations: For each kernel flavor you want to build the driver make sure you have the associated kernel-devel package. Ex: kernel-2.6.18.92.el5 would require kernel-devel-2.6.18-92.el5 kernel-PAE-2.6.18.92.el5 would require kernel-PAE-devel-2.6.18-92.el5 SUSE SLES Installation: Make sure that kernel-source and kernel-syms packages are installed. kernel-syms package contains symbol versions for the all the flavors that the distribution supports. Installing the RPM Package ============================= 1. This package requires couple of other packges to complete the build. Please refer the "Build Environment Setup" Section before proceding to the next step. 2. Install the source RPM package. # rpm -ivh hp-mlnx-en-.src.rpm 3. Build the binary RPM for the hp-mlnx-en driver. Red Hat Installation: # cd /usr/src/redhat # rpmbuild -bb SPECS/hp-mlnx-en.spec SLES Installations: # cd /usr/src/packages # rpmbuild -bb SPECS/hp-mlnx-en.spec If you get an error during the build process, refer to the "Build Environment Setup" section. 4. Remove the loaded mlx4_en module. # modprobe -r mlx4_en Check for the existence of a current version of the hp-mlnx-en package as follows: # rpm -q hp-mlnx-en If an old version of the package exists, the RPM package should be removed. # rpm -e hp-mlnx-en Verify that the old package has been removed as follows: # rpm -q hp-mlnx-en 5. Install the new RPM package. This installs the hp-mlnx-en driver and man page. Do not use the U (Upgrade) flag in the RPM command below - previous hp-mlnx-en drivers must be removed as described in step 4 above before installing this version. # rpm -ivh RPMS//hp-mlnx-en-..rpm --force The driver will be installed in the following path: 2.6.x kernels; /lib/modules//updates/kernel/drivers/net/mlx4/mlx4_en.ko 6. Configure your network setting and address. You may need to refer to your Linux vendor documentation. Helpful network configuration tools such as "yast2" in SLES or linuxconf/redhat-config-network/netconfig in Red Hat exist for easy configuration. For SLES, you must specify the module as mlnx_en while configuring the network. The module can be specified in Hardware Details of Advanced configuration 7. 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. Refer to the modules.conf man page for more information. alias eth0 mlx4_en alias eth1 mlx4_en alias eth# mlx4_en For SLES, the configuration file is /etc/modprobe.conf or /etc/modprobe.conf.local Note: If the above entry does not exist, add it in the configuration file. 8. Reboot your server. Upon reboot the network should start with the hp-mlnx-en driver loaded and the correct network configuration. To verify that the hp-mlnx-en driver is loaded, use the following command. # lsmod If mlx4_en is listed then the hp-mlnx-en driver loaded. Load the hp-mlnx-en driver: # modprobe mlx4_en Use ifconfig to bring up the network with the new driver: # ifconfig eth# up Refer to the man pages for lsmod, ifconfig, rmmod, insmod, modprobe, modules.conf and modprobe.conf for more detailed information. Uninstalling the RPM Package ============================= The following command will uninstall the hp-mlnx-en RPM. # rpm -e hp-mlnx-en- Caveat ======= When creating port configuration files using YAST on SLES systems, not all (or no) mlx4_en network interfaces are seen by the tool. The interface configuration needs to be done by "adding" a new interface and setting its MAC address manually. Run YAST and add a new configuration file. Get the MAC address by running ifconfig on the interface. Edit network card configuration file under /etc/sysconfig/network and restart network after adding the MAC address to the file. Limitations =========== None (C) Copyright 2002, 2003 - 2009 Hewlett-Packard Development Company, L.P. Product names mentioned herein may be trademarks and/or registered trademarks of their respective companies.