		   be2net Linux Drivers Package

			Emulex Corporation

		Copyright (C) 2012 Emulex Corporation
			All rights reserved



Table Of Contents
-----------------
1. Introduction
2. Linux Distribution support
3. Package Contents
4. Installation and Uninstallation of component Linux drivers
5. Errata Kernel Upgrade Support
6. Known Issues




1. Introduction

This be2net Linux Drivers Kit contains all the Linux device drivers
required for NET protocol support.


2. Linux Distribution support

The following Linux distributions are supported:

RHEL5.6             (kernel version 2.6.18-238.el5)
RHEL5.7             (kernel version 2.6.18-274.el5)
RHEL5.8             (kernel version 2.6.18-308.el5)
RHEL6.0             (kernel version 2.6.32_71.el6)
RHEL6.1             (kernel version 2.6.32_131.el6)
RHEL6.2             (kernel version 2.6.32_220.el6)
RHEL6.3             (kernel version 2.6.32_279.el6)
SLES10-SP3          (kernel version 2.6.16.60_0.54.5)
SLES10-SP4          (kernel version 2.6.16.60_0.85.1)
SLES11-SP1          (kernel version 2.6.32.12_0.7.1)
SLES11-SP1-errata   (kernel version 2.6.32.36_0.5.1)
SLES11-SP2          (kernel version 3.0.13-0.27)
OL5.6-UEK           (kernel version 2.6.32-100.26.2.el5uek)
OL5.7-UEK           (kernel version 2.6.32-200.13.1.el5uek)
OL5.8-UEK           (kernel version 2.6.32-300.10.1.el5uek)
OL6.1-UEK           (kernel version 2.6.32-100.34.1.el6uek)
OL6.2-UEK           (kernel version 2.6.32-300.3.1.el6uek)
OL6.3-UEK           (kernel version 2.6.32-200.24.1.el6uek)
OVM3.1.1-UEK        (kernel version 2.6.39-200.1.1)

The following architectures are supported:
- i686
- x86_64
- ia64
- ppc

3. Package Contents

The package is released as a single gzipped tar file.

After the file is uncompressed the package will will consist of the following 
components:

a. elx_net_install.sh

General installation script. A user will execute this script to install the
device drivers for the supported be2net protocol.

b. README

This file.

c. A gzipped tar file that contains the NET driver to be installed.

d. A SRPMS subdirectory which contains the device driver's Source RPM
   (be2net-<VERSION>.src.rpm)

4. Installation and Uninstallation of component Linux drivers

To install the device drivers included in the kit a user will execute the 
following command:

# ./elx_net_install.sh

Execution of this command will result in the device drivers of the net
protocol included in this kit, for the currently running Linux kernel, to be 
installed and loaded.

To uninstall the device drivers a user will use the "--uninstall" option:

# ./elx_net_install.sh --uninstall 

or,

# ./elx_net_install.sh -u


5. Errata Kernel Upgrade Support

If a user has installed this be2net package on a supported Generally
Available distribution kernel release (i.e. RHEL5.5, SLES10-SP3 etc),
any errata kernel upgrades will be handled automatically.

6. Known Issues

6.1 Backup and restore existing be2 drivers in DUP/DUD Boot-from-SAN 
    configurations after a kernel upgrade

6.1.1 Observed Problem

    When a user installs updated be2net drivers via the
    Driver Update Disk (DUD) process and then updates the system's
    kernel, the corresponding DUD be2 drivers are copied by
    the kernel upgrade process to the
    /lib/modules/<kernel>/weak-updates/updates directory.

    Based on the default loading priority of driver modules (defined
    in the /etc/depmod.d/depmod.conf.dist file), the driver modules
    resident in the /updates directory will load first, followed by
    driver updates built against the exact kernel installed
    (i.e. KMP), followed by the built-in distribution drivers.

    The result of this process though, kernel upgrade followed by
    be2net package installation, is that after the system is rebooted, the
    driver modules in the /lib/modules/<kernel>/weak-updates/updates
    directory will load first (Driver Update Disk drivers), although
    the desired result would be for the newly installed drivers via
    the be2net package to take affect/loaded instead.

6.1.2 Resolution

    In order to resolve the above issue, a user should take the
    following steps before and after the be2net driver is installed in a
    Boot-from-SAN configuration where a Driver Update Disk image was
    used.

    a. Before the be2net driver is installed:

    - If they exist, backup the be2net.ko files from the
      /lib/modules/<kernel>/weak-updates/updates directory to a well
      known system location.

      Example:
        # mkdir /tmp/updates_save_dir
        # cp /lib/modules/`uname -r`/weak-updates/updates/be2net.ko \
             /tmp/updates_save_dir

    - Remove the be2net.ko files from 
      the /lib/modules/<kernel>/weak-updates/updates directory:

        # rm /lib/modules/`uname -r`/weak-updates/updates/be2net*.ko

    Then install the be2net driver.

    b. Before the be2net driver is uninstalled and before the
    system is rebooted:

    - Restore the be2net.ko files to the 
      /lib/modules/<kernel>/weak-updates/updates directory.

      Example:
        # cp /tmp/updates_save_dir/*.ko \
             /lib/modules/`uname -r`/weak-updates/updates

    - Proceed with the net uninstallation and system reboot.

