Driver Disk for Emulex Be2net 4.0.359.0 and Lpfc 8.3.5.44.4p - For XenServer 6.0
Who Should Install This Driver Disk?
Customers running Citrix XenServer 6.0, who wish to use Emulex OneCommand to manage their Emulex Fibre Channel (FC) Host Bus Adapters (HBA), Fibre Channel over Ethernet (FCoE) Converged Network Adapters (CNA), and Ethernet Network Adapters.
Issues Resolved In This Driver Disk
This provides an Emulex built Driver Disk that includes versions of lpfc, be2net, and OneCommand Manager Corekit. The versions for these components are:
- lpfc: 8.3.5.44.4p
- be2net: 4.0.359.0
- OneComand: 5.2.12.2-1
Users must ensure that they are running the 4.0.493.0 Emulex firmware version for your CNA to be supported by Citrix. The firmware is available from http://www.emulex.com/downloads/emulex/linux/xenserver-60/drivers.html
Installing the Driver Disk
Customers should use the XenServer CLI to install this driver disk. Once the driver has been installed, the server must be restarted, in order for the driver to be loaded. As with any software update, Citrix advises customers to back up their data before applying this driver disk.
Please note that the attachment to this article is a zip file. It contains both the driver disk ISO mentioned below, and the source code for the driver. The zip file should be unzipped (to produce the driver disk ISO image), before carrying out the steps below. The source code file is not necessary for driver disk installation: it is provided to fulfill licensing obligations.
The file with filename ending metadata.md5 contains the checksum of the driver disk's metadata. If, when you install the driver disk, you elect to verify the driver disk when prompted, you should check that the checksum presented by the installer is the same as that in the metadata MD5 checksum file included as part of this download.
Also present in the zip file is an MD5 checksum for the ISO image named emulex.iso.md5. This will allow you to verify that your download has been successful. This checksum is of the ISO only, and can be verified by following the instructions at CTX116166: How to verify downloaded ISO images.
Installing as Part of a Clean XenServer Installation
- Once you have selected your keyboard layout at the first installer prompt, you will be presented with a welcome screen. At this point, press F9 on your keyboard, and insert the CD with the driver disk in it, or use one of the other methods such as installation over the network.
Users should note that if installation over HTTP or FTP is to be used, the ISO image must be unpacked at that location (i.e. the installer expects to find the contents of the ISO at that network location, not the ISO itself). - The installer will proceed to attempt to load the driver. If this is successful, you can continue with the installation as normal. Near the end of the installation, you will be prompted to re-insert the driver disk (otherwise known as a XenServer supplemental pack) so that the driver can be installed onto disk. You must re-supply the driver disk at this point. Failure to do so will mean that the installation will not contain the new drivers. After this step, no further action is required.
If the installer fails to load the new driver from the driver disk, it is likely to be because an earlier version of the driver has already been loaded. In general, this is because a hardware component is present that is supported by the version of the driver that ships as part of XenServer (even if another component is present that requires a newer version of the driver). To avoid the existing driver being loaded, use the following procedure.
- Reboot the host, leaving the XenServer installation CD-ROM in the drive.
- At the boot: prompt, type:
shell
- You will now be presented with a command prompt. Enter the following:
rmmod be2net
If this succeeds (i.e. there are no error messages printed),the installer's versions of the drivers have been unloaded. If error messages are presented, it is likely that other drivers depend on one or more of the drivers you are attempting to unload. If this is the case, please contactCitrix Technical Support.
rmmod lpfc - Type
exit
or press Control+D on your keyboard, to return to the installer. - Use the procedure described above to provide the driver disk to the installer, which should now load correctly.
Installing onto a Running XenServer System
- Download the driver disk directly to the XenServer host to be updated (Citrix recommends storing it in the /tmp/ directory), or first download the file to an Internet-connected computer, and burn the ISO image to a CD.
- Use XenCenter to access the XenServer host's console, or log in directly using SSH.
- Mount the driver disk image. The directory being mounted varies depending on whether the driver disk is still in ISO form, or was burnt to CD. For a CD-ROM, use:
mkdir -p /mnt/tmp
If instead, the ISO file is used, the steps are:
mount /dev/
cd /mnt/tmp/
./install.sh
cd /
umount /mnt/tmpmkdir -p /mnt/tmp
mount /tmp/
cd /mnt/tmp/
./install.sh
cd /
umount /mnt/tmp - To complete the installation, restart the host. This ensures that the driver loads correctly.
Vendor Notes: Unable to make permanent LPFC driver parameter changes with OneCommand Manager
Due to a bug, the One Command Manager (OCM) component included in this updated Driver Disk causes a failure when persistent commands are issued. Therefore customers will not be able to make permanent changes in the LPFC driver’s parameters using the OCM CLI. Instead, customers should set the LFPC driver parameter to "T" (not persist on system reboot). See the example below:
hbacmd SetDriverParamT
The LPFC driver parameter change will need to be re-issued on any subsequent system reboots, .
Files
Driver Disk Files
| File Name | File MD5 Checksum |
|---|---|
| emulex.iso | 84a655be406644a69fe5dce45eaa2b03 |
| metadata | 2f514bde436232c4ed0b783ac543e415 |
Drivers Provided
| Module Name | Version | RPM Name |
|---|---|---|
| be2net-modules-xen (Xen kernel) | 4.0.359 | be2net-modules-xen-2.6.32.12-0.7.1.xs6.0.0.529.170661-4.0.359.0-1.i386.rpm |
| be2net-modules-kdump (Kdump kernel) | 4.0.359 | be2net-modules-kdump-2.6.32.12-0.7.1.xs6.0.0.529.170661-4.0.359.0-1.i386.rpm |
| elxocmcore | 4.0.359 | elxocmcore-5.2.12.2-1.i386.rpm |
| elxocmlibhbaapi | 4.0.359 | elxocmlibhbaapi-5.2.12.2-1.i386.rpm |
| lpfc-modules-xen (Xen kernel) | 8.3.5.44 | lpfc-modules-xen-2.6.32.12-0.7.1.xs6.0.0.529.170661-8.3.5.44.4p-1.i386.rpm |
| lpfc-modules-modules-kdump (Kdump kernel) | 8.3.5.44 | lpfc-modules-kdump-2.6.32.12-0.7.1.xs6.0.0.529.170661-8.3.5.44.4p-1.i386.rpm |
More Information
For information on how to build driver disks, refer to CTX124957 - XenServer 5.6 Supplemental Pack Guide.
No comments:
Post a Comment