Emulex Lpe12000 Drivers

Posted on by admin

Dell Update Package for updating firmware on the Emulex Network and Fibre Channel adapters Search. Driver Details. Choose another product. The driver information is up-to-date. To view all drivers for your OEMR R310, go to Drivers and downloads. Emulex Network and Fiber Channel Adapter Firmware. Dell Update Package for updating. Emulex network adapters are high-performance adapters that consolidate traffic for networking, Fibre Channel and FCoE storage. Includes FCoE Converged Network Adapter (CNA) and Host Bus Adapters (HBA). Visit Dell.com to learn more. Emulex Drivers Version 10.2 for VMware ESXi User Manual P010087-01A Rev. Introduction Supported Guest Operating Systems 9 Supported Guest Operating Systems The Emulex driver supports the following guest operating systems: CentOS 5.x CentOS 6.x RHEL 5.x RHEL 6.x RHEL 7.x SLES 11.x Windows Server 2008 R2 Windows Server 2012. Firmware for HP Branded 8Gb Emulex HBAs and Mezz Cards. By downloading, you agree to the terms and conditions of the Hewlett Packard Enterprise Software License Agreement. Note: Some software requires a valid warranty, current Hewlett Packard Enterprise support contract, or a license fee. Streamlined installation and management, plus unrivaled scalability and industry-leading virtualization support make the Emulex 8Gb Fibre Channel single-port and dual-port host bus adapters ideal solutions for enterprise and mixed-OS environments. With powerful management tools, they deliver maximum performance in the widest range of applications and environments. Mar 08, 2011  Firmware for FC2242 (A8003A) HBA and the Emulex LPe1105-HP 4Gb c-class Mezzanine HBA. By downloading, you agree to the terms and conditions of the Hewlett Packard Enterprise Software License Agreement. Note: Some software requires a valid warranty, current Hewlett Packard Enterprise support contract, or a license fee.

  1. Emulex Lpe12000 Driver Vmware
  2. Emulex Driver Download
  3. Emulex Lightpulse Hba Driver
  4. Emulex Lpe12000 Drivers License
  5. Emulex Drivers For Windows
  6. Emulex Lpe12000 Driver Download
Printable version

Firmware for FC2242 (A8003A) HBA and the Emulex LPe1105-HP 4Gb c-class Mezzanine HBA

By downloading, you agree to the terms and conditions of the Hewlett Packard Enterprise Software License Agreement.
Note: Some software requires a valid warranty, current Hewlett Packard Enterprise support contract, or a license fee.

Type:Firmware - Storage Fibre Channel and Fibre Channel Over Ethernet
Version:2.82x4(8 Mar 2011)
Operating System(s): OS Independent
File name:LPe11002_LPe1105_zf282x4.zip (289 KB)
Firmware for the FC2242 [A8003A] dual port 4Gb PCI-e Fibre Channel Host Bus Adapter and the Emulex LPe1105-HP 4Gb FC HBA for HP c-Class BladeSystem

End User License Agreements:
HPE Software License Agreement v1

HP StorageWorks Emulex Adapters Release Notes

Itanium® is a registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

Abstract

This document contains supplemental information for the Emulex Fibre Channel host bus adapters (HBAs) and converged network adapters (CNAs) for ProLiant and Integrity servers.

Product models
Supported CNA, HBA, and mezzanine product models
Devices supported
Operating systems
Linux support
Windows support
VMware support
Citrix operating system
Important notes and workarounds
General notes
CNA/HBA Linux notes
CNA/HBA with Windows notes
VMware notes
Citrix notes
Effective date

This section lists the HBAs and CNAs that are supported on ProLiant and Integrity servers.

Table 1, “Supported CNAs and Server LOMs” describes the CNAs and Server LOMs supported on servers running Linux, Windows, VMware, and Citrix operating systems.

Table 1 Supported CNAs and Server LOMs

Model

Windows Server 2003/2008

Linux

VMwareCitrix
CNA
HP StorageWorks CN1000E Dual Port Converged Network Adapter (AW520A)•••—
HP NC551m Dual-port FlexFabric 10-Gb Converged Network Adapter (580151-B21)•••—
Server LOM
Embedded BE2 LOM (AMD)—NC551i Dual-port FlexFabric 10-Gb Converged Network Adapter •••—
Embedded BE3 LOM (Intel)—NC553i Dual Port FlexFabric 10-Gb Converged Network Adapter •••—

NOTE: CNAs and Server LOMs are not supported on Integrity servers.

Table 2, “Supported 8-Gb and 4-Gb HBAs and mezzanine cards” describes the 8-Gb and 4-Gb HBAs and mezzanine cards supported on servers running Linux, Windows, VMware, and Citrix operating systems.

Table 2 Supported 8-Gb and 4-Gb HBAs and mezzanine cards

Model

Windows Server 2003/2008

Linux

VMwareCitrix
8-Gb HBAs and mezzanine cards
HP StorageWorks LPe1205–HP 8-Gb FC Mezzanine Card HBA (456972–B21)[1]••[2]••
HP StorageWorks 81E 8-Gb PCI-X HBA (AJ762A)••[2]••
HP StorageWorks 82E 8-Gb PCI-X Dual Channel HBA (AJ763A)••[2]••
HP PCIe 1-port 8-Gb Fibre Channel HBA (AH402A)•[3]———
HP PCI-e 2-port 8-Gb Fibre Channel HBA (AH403A)•[3]———
4-Gb HBAs and mezzanine cards
HP StorageWorks LPe1105–HP 4-Gb FC HBA for HP c-Class BladeSystem (403621- B21)••••
HP StorageWorks FC2142SR 4-Gb PCI-e FC HBA (A8002A)[4]••••
HP StorageWorks FC2242SR 4-Gb PCI-e dual port FC HBA (A8003A)••••
HP StorageWorks FC2143 4-Gb PCI-X FC HBA (AD167A)••••
HP StorageWorks FC2243 4-Gb PCI-X dual port FC HBA (AD168A)••••

Legend: • = supported; — = not supported

[1] The LPe1205 is supported with most G6 and later ProLiant blade servers with the exception of BL465G6 and BL495G6

[3] IA64 support only

[4] The FC2142 HBA is also supported on XW8400 and XW9300 workstations running Windows XP Professional (32-bit)

Table 3, “Supported 2-Gb HBAs and mezzanine cards” describes the 2-Gb HBAs and mezzanine cards supported on servers running Linux, Windows, VMware, and Citrix operating systems.

NOTE: The HBAs and mezzanine cards listed in Table 3, “Supported 2-Gb HBAs and mezzanine cards” are supported; however, they are no longer available for purchase.

Table 3 Supported 2-Gb HBAs and mezzanine cards

Model

Windows Server 2003/2008

Linux

VMwareCitrix
HP StorageWorks 1050EX 2-Gb PCI-e FC HBA (A7560A)•[1]———
HP StorageWorks A7388A 2-Gb PCI-X FC HBA (A7388A)•———
HP StorageWorks A7387A 2-Gb PCI-X dual port FC HBA (A7387A)•———
HP StorageWorks FCA2404DC 2-Gb PCI-X dual port FC HBA (323264-B21)•[1]———
HP StorageWorks FCA2404 2-Gb PCI-X FC HBA (305573-B21)•[1]———
HP Emulex-based BL20p 2-Gb PCI-X FC mezzanine card (394757-B21)•[1]———
HP Emulex-based BL25/30/35/45p PCI-X FC mezzanine card (394588-B21)•[1]———
HP StorageWorks AB467A 2-Gb 1-port FC HBA •[2]———
HP StorageWorks AB466A 2-Gb 2-port FC HBA •[2]———

Legend: • = supported; — = not supported

[2] Supported on Windows Server IA64 only

NOTE: For the latest information about storage array support, see the HP SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access.

Emulex CNAs, HBAs and LOMs are supported on HP Servers that:

  • Support the Linux, Windows, VMware, and Citrix operating systems listed on the HP website:

  • Support the servers listed on the HP website:

  • Support B-series, C-series, M-series, and H-series switch products. For the latest information, see the HP support website http://welcome.hp.com/country/us/en/support.html and the HP StorageWorks SAN Design Reference Guide at http://www.hp.com/go/sdgmanuals.

See the CNA QuickSpecs for information about the supported servers for the CNAs.

NOTE: The HP CNAs and LOMs are not currently supported on Citrix operating systems.

For more information about the NC551m FlexFabric Adapter, see the HP website:

http://h18004.www1.hp.com/products/blades/components/emulex/nc551m/index.html.

For the latest information about storage array support, see the HP SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access.

This section describes how you can obtain the latest information about supported operating systems and software.

For the latest information about supported HBAs, CNAs, LOMs, and mezzanine cards listed by operating systems, see the HP SPOCK website at: http://h20272.www2.hp.com/Pages/spock2Html.aspx?htmlFile=hw_hbas.html&lang=en&cc=US&

You must sign up for an HP Passport to enable access. From the web page, click HBA Software Support Matrix, and then select your operating system.

This section describes CNA and HBA support for Linux, including prerequisites and installation instructions.

Before you perform CNA or HBA updates, you must do the following:

  • Ensure that the system is running one of the operating system versions listed in HBA Software Support Matrices, available at the SPOCK website http://www.hp.com/storage/spock.

    You must sign up for an HP Passport to enable access.

  • See the HP server PCI slot specifications to determine if your server is compatible with the CNA or HBA.

  • If you are installing the Linux operating system for the first time, load the operating system before you download and install the Linux CNA/HBA/LOM driver from the HP website:

NOTE: Starting with RHEL 5 U3, SLES 10 SP3, and SLES 11; Fibre Channel HBAs and mezzanine cards are supported by Red Hat and Novell in-box drivers (included in the OS distribution), and multipath failover is handled by Device Mapper.

Starting with RHEL 5.5, CNAs are supported by Red Hat in-box drivers. However, SLES 10 and SLES 11 do not support CNAs with in-box drivers. CNA multipath failover is handled by Device Mapper.

NOTE: Do not install fibreutils on systems using CNAs.

For information on installing CNAs, see the HP StorageWorks Converged Network Adapter Installation Guide:

  1. Go to http://www.hp.com/go/support.

  2. Click .

  3. Using the HP model number as your guide, enter the CNA model number in the for product box.

  4. Select Manuals.

This section describes additional Linux installations required for HBAs.

IMPORTANT: If you have both CNAs and Fibre Channel HBAs installed in your system, you must load and use the CNA drivers.

Installing Linux using the in-box driver

Instructions on how to install Linux while using the in-box driver are available on the HP website:

From the website, search for device mapper + boot + san.

If you require multiple-path redundancy, you must install the HP-supplied Device Mapper Multipath Kit after you install the operating system. You can download the kit from the HP website:

You must also install the HP Fibre Channel Enablement Kit (hp-fc-enablement) after installing the operating system.

Installing the HP Fibre Channel Enablement Kit

The HP Fibre Channel Enablement Kit provides additional libraries and configuration utilities to enable HP StorageWorks Fibre Channel storage arrays to work with Linux. The kit is not required to use the lpfc and qla2xxx kernel modules; however, it provides configuration scripts that ensure that your configuration is set properly to work with HP StorageWorks Fibre Channel arrays. The Fibre Channel Enablement Kit also sets the correct lpfc and qla2xxx kernel module settings that are used with Device Mapper multipathing.

NOTE: If you are using any HP management applications, you will need the HBAAPI libraries that are included in the hp-fc-enablement kit.

To install the HP Fibre Channel Enablement Kit:

  1. Download the hp-fc-enablement-yyyy-mm-dd.tar.gz file for your operating system and copy it to the target server.

  2. Untar the enablement kit by executing the command to create the directory, hp-fc-enablement-yyyy-mm-dd:

    # tar zxvf hp-fc-enablement-yyyy-mm-dd.tar.gz

  3. Browse to the directory hp-fc-enablement-yyyy-mm-dd.

  4. Do one of the following to execute the install.sh script:

    • If you are not using Device Mapper multipathing, enter the following command:

      # ./install.sh -s

    • If you are using Device Mapper multipathing, enter the following command:

      # ./install.sh -m

  5. To verify the installation, enter the following commands:

    # rpm -q hp-fc-enablement

    # rpm -q fibreutils

Uninstalling the HP Fibre Channel Enablement Kit

To uninstall the Fibre Channel Enablement Kit, untar the kit as instructed in Step 1 through Step 3 (the section called “Installing the HP Fibre Channel Enablement Kit”), and then execute the install.sh script with the –u option:

# ./install.sh -u

To manually uninstall the enablement kit, enter the following commands:

# rpm -e hp-fc-enablement

# rpm -e fibreutils

Installing the Linux device driver using the HP kit (earlier than RHEL 5 U3)

HP does not support building the lpfc driver from source code. The driver versions for kernel-based distributions are as follows:

  • Driver 7.x.x for the 2.4 kernel

  • Driver 8.x.x.x for the 2.6 kernel

To install the device driver:

  1. Download the driver kit for your distribution. The driver kit file will be in the form of hp-lpfc-yyyy-mm-dd.tar.gz.

  2. Copy the driver kit to the target system.

  3. Uncompress and untar the driver kit by entering the following command:

    # tar zxvf hp-lpfc-yyyy-mm-dd.tar.gz

  4. Change the directory to hp-lpfc-yyyy-mm-dd.

  5. Do one of the following:

    • Enter the following command to install the Linux device driver:

      # ./INSTALL

      The command syntax varies depending on your configuration. Use the –h option of the command to list all supported options. If a driver kit is already installed, you can enter the command without any options, and then the script uses the current configuration.

    • Enter the following command to install the Linux device driver for SLES 10 SP1 only:

      #./INSTALL -p

      • Include the -m option to force the installation to failover mode.

        #./INSTALL –mp

      • Use the –s option to force the installation to single-path mode.

        #./INSTALL –s

        The INSTALL script installs the appropriate driver for your configuration and the appropriate fibreutils. When the script is finished, either reload the Emulex driver modules (lpfc, lpfcdfc, and lpfcmpl) or reboot your server.

Loading the driver

To load the driver, enter the following commands:

# modprobe lpfc

# modprobe lpfcdfc

NOTE: The command modprobe lpfcdfc is for RHEL 4 Ux and SLES 9 SPx.

# modprobe lpfcmpl

NOTE: The command modprobe lpfcmpl is for a MultiPulse configuration only.

Rebooting the server

To reboot the server, enter the following command:

# reboot

If your boot device is a SAN attached device, you must reboot your server.

Verifying the driver version

To verify the driver version, use the RPM command with the -q option.

# rpm -q hp-lpfc

# rpm -q hp-multipulse

For MultiPulse configuration only:

# rpm -q fibreutils

Unloading the driver

To unload the driver, enter the following commands:

# modprobe –r lpfcmpl

NOTE: The command modprobe –r lpfcmpl is for MultiPulse configuration only.

NOTE: The command modprobe –r lpfcdfc is for RHEL 4 Ux and SLES 9 SPx.

# modprobe –r lpfcdfc

# modprobe –r lpfc

Installing HBAnyware on Linux

To install HBAnyware on a Linux system:

  1. Download the file HP_ElxApps-<Kernel Version>-<HBAnyware Version>-<Driver Version>.zip to the target system.

    Example:HP_ElxApps-26-3.2a16-8.1.10.11.zip

    NOTE: For information about HBAnyware and driver versions, see Linux support. Use kernel Version 26 for 2.6 kernels and kernel Version 24 for 2.4 kernels.

  2. Unzip the file on the target system.

    Example:# unzip HP_ElxApps-26-3.2a16-8.1.10.11.zip

  3. Make the file executable under Linux.

    Example:# chmod +x HP_ElxApps-26-3.2a16-8.1.10.11.bin

  4. Install the application.

    Example: #./HP_ElxApps-26-3.2a16-8.1.10.11.bin

  5. Launch the application.

    Example: # HBAnyware or # /usr/sbin/hbanyware/hbanyware

    NOTE: For more information, see the HBAnyware online help.

    HBAnyware 3.4a16 has a known presentation issue with the 8.0.16.40 driver and the AJ762A and AJ763A HBAs. The link speed is not displayed. This will be corrected in a future release.

Determining the CNA/HBA driver and firmware versions in Linux

You can use OneCommand Manager or HBAnyware to view a list of CNAs/HBAs driver and firmware information.

This section describes CNA/HBA support for Windows.

CNAs/HBAs/LOMs are supported on ProLiant servers with Enterprise, Standard, Storage Server, and Datacenter versions of the following:

  • CNAs/LOMs on Windows 2003:

  • HBAs on Windows 2003:

    • Windows Server 2003 x86 – SP1, R2, SP2 (32-bit) (STORport and SCSIport)

    • Windows Server 2003 x64 – SP1, R2, SP2 (64-bit) (STORport only)

  • Windows Server 2008 W32 – SP2

  • Windows Server 2008 x64 – SP2, R2

HP offers a bundle for small businesses running Windows XP Professional. Table 4, “Supported configuration for Windows XP Professional (32-bit)” lists the contents of the bundle.

Table 4 Supported configuration for Windows XP Professional (32-bit)

Windows driver, workstation, switch, storage array, and utility requirements

HBA

HP StorageWorks FC2142SR (product number A8002A)

HBA firmware/BIOS

2.72a2 /1.71a0 (distributed in Universal Boot Image 5.02a1)

Windows driver

SCSIport miniport 5.30a2

Workstations

XW8400, XW9300

FC switch

Cisco 8-port MDS 9124

Storage array

EVA4000

HBAnyware

3.0a16_winxp

Restrictions

Single path only. BFS is not supported.

HP supports the use of Linux and Windows as a guest on VMware ESX Versions 4.x and 3.x. When running VMware, Fibre Channel HBAs and CNAs are supported by in-box drivers supplied with VMware ESX. Linux Fibre Channel HBA drivers are not supported on the Virtual OS (VOS).

NOTE: You are not required to install the Emulex driver because it is shipped with the ESX server.

To ensure that your HBA/CNA is supported by HP and VMware, see the VMware Compatibility Guide at:

For information about boot from SAN (BFS) on VMware, see HP StorageWorks Fibre Channel Host Bus Adapters Software Guide for Linux, available at:

HP supports the Citrix hypervisor. For more information, see the HP Virtualization with Citrix website: http://www.hp.com/go/citrix

This section describes important notes and workarounds for issues for Emulex CNA/HBA adapters running Linux and Windows.

When using a C-series Converged Network Switch (HP Nexus 5000) along with the HP Virtual Connect FlexFabric 10-Gb/24-port module, NPIV must be enabled on the C-series switch.

The CN1000E maximum supported Ethernet Jumbo Packet frame size is 8192 bytes.

The CN1000E maximum supported optical cable length is 40 meters.

DL16x and DL18x Servers require extra time to boot from SAN.

When the CN1000E adapter is used as the boot device in a DL16x or DL18x server, the server may pause for approximately 90 seconds when it is expected to start booting from the hard disk. After this delay, the boot process resumes as expected.

Update DL/SL100-series BIOS before installing CN1000e

Before installing an HP CN1000e into a DL/SL100-series server, you must upgrade the server BIOS to 2010.02.04 or later. The BIOS is available for download from the HP Download Drivers and Software website:

HP recommends that you implement zoning by CNAs/HBAs, as described in the HP StorageWorks SAN Design Reference Guide, available at:

HP ProLiant DL380 (G4) servers must have System ROMPaq firmware 4.05 P51-08/16/2005 or later to be compatible with the FC2142SR and FC2242SR. Failure to use this ROMPaq version can cause the HBAs to hang during the power-on self-test (POST). For more information, see the HP website:

This section describes restrictions that apply to Linux and this release of the CNAs/HBAs:

  • Firmware download in SLES 10 SP3 can cause the system to hang.

    When downloading firmware to the CN1000E adapters in SLES 10 SP3 using the OneCommand Manager or hbacmd, the download may complete but cause the system to become unresponsive or hang. Though the firmware download is successful, a hard reboot of the server may be required to enable the new firmware.

  • HP and Novell are evaluating a report that Reiserfs filesystems display unexpected behavior under heavy load. Other filesystems such as xfs and ext3 are not affected by this behavior. HP recommends that you use either the xfs or ext3 filesystem. This is a high priority issue that is in the process of being resolved. When a resolution is found, a maintenance update will be available on the Novell website:

  • HP recommends that you use the ext3 filesystem in high availability (HA) environments. For information on how to use other Linux filesystems in an HA environment, see SLES 11 Administration Guide, available at the Novell website http://www.novell.com/documentation/sles11, and the Red Hat Deployment Guide, available at the Red Hat website http://www.redhat.com.

    For information on the differences between ext2 and ext3, see the operating system documentation.

  • SLES 10 SP2 has an issue displaying 8-Gb HBA speed. You can correct the problem using kernel Version 2.6.16.60-0.25.

  • BFS is not supported on the A8002A with RHEL 4 U3 and U4, IA64, or SLES 10 IA64.

  • Beginning with RHEL 6.0 and SLES 11, HP no longer supports XP128 or XP1024.

    Beginning with RHEL 5.3 and SLES 10 SP3, HP no longer supports MSA1000, MSA1500, EVA3000, or EVA5000.

  • For Modular Smart Arrays and Enterprise Virtual Array, active/passive storage arrays are supported in single-path mode only.

  • For the MSA2000 family of disk arrays only:

    • The minimum required firmware is J200P24-01.

    • Creating virtual disks (vdisks) online or offline without volumes during the virtual disk creation process is not supported. You must create at least one volume during the virtual disk creation.

    • MultiPulse is not supported. See the HP Device Mapper documentation for multipathing support.

    • BFS is not currently supported.

  • The Emulex MultiPulse 2.2.22, 2.2.38, 2.2.39, and 2.2.44 drivers support active/active storage arrays only.

  • If using MultiPulse 2.1.x, you can have a maximum of four physical paths to a LUN. More than four paths can cause a failure.

  • If using MultiPulse 2.2.x, you can have a maximum of eight physical paths to a LUN. More than eight paths can cause a failure.

  • MultiPulse can coexist with multipathing products such as the Emulex failover driver and Secure Path. However, MultiPulse works only with Emulex-based HBAs; it will not configure multiple paths for other HBAs in the system.

  • Because the order in which a switch reports Fibre Channel ports to a name server can vary, the order in which LUNs are discovered can vary between system boots.

    HP recommends that you use the udev utility to ensure that the name of a device does not change between system boots. For more information, see the udev website:

  • When using MultiPulse with SUSE Linux systems in BFS configurations, HP recommends that you use the udev utility to ensure that your system boots successfully. For more information about this procedure, see the HP StorageWorks Fibre Channel Host Bus Adapters Software Guide for Linux, available at the HP website:

  • If you are installing the Linux operating system for the first time, load the operating system before you download and install the supported Linux HBA driver from the HP website:

  • XP LUNs presented to Linux hosts must start with LUN 0.

  • HP recommends that you implement zoning by HBA, as described in the HP StorageWorks SAN Design Reference Guide, available on the website:

  • A maximum of 10 targets are supported in a BFS zone.

  • On an sx2000 system with the default logging level, a call trace may appear in the /var/log/messages file during failover events.

  • When running the scsi_info command on older XP arrays such as XP1024/128, you may see output similar to that shown in the following example. Ignore the error, and note that the XP array's WWN is not all zeros.

    The XP array returns inquiry data that differs slightly from that returned by EVA or MSA arrays.

    [root@coco /]# scsi_info /dev/sdal SCSI_ID='4,0,8,0':
    VENDOR='HP':MODEL='OPEN-

    E':FW_REV='5005':WWN='0000000000000000':LUN='5235303020303030-3130353930203030'

    [root@coco /]# scsi_info /dev/sdam

    SCSI_ID='4,0,8,1':VENDOR='HP':MODEL='OPEN-

    E':FW_REV='5005':WWN='0000000000000000':LUN='5235303020303030-3130353930203030'

    [root@coco /]# scsi_info /dev/sdan

    SCSI_ID='4,0,9,0':VENDOR='HP':MODEL='OPEN- 3':FW_REV='2114':WWN='03000000002018e9':LUN='5234353120303030-3330313033203030'

    [root@coco /]# scsi_info /dev/sdao SCSI_ID='4,0,9,1':VENDOR='HP':MODEL='OPEN-

    3':FW_REV='2114':WWN='0b00000000600000':LUN='5234353120303030-3330313033203030'

  • RHEL 5 U3 and SLES 10 SP3 do not support active/passive arrays.

  • Installing PSP 7.91/92 causes fibreutils to downgrade. Reinstall fibreutils rpm from the downloaded kit.

    Example:

    #rpm –fvh fibreutils.<version>.linux.<arch>.rpm

  • When an EVA4400 with embedded switch is configured in a heterogeneous SAN, HP recommends that you use a text editor to edit the HBA configuration file etc/modprobe.conf.

    options lpfcmpl mpl_hbeat_tmo_busy=0

    Save the file, and then run the make_initrd script.

    # /opt/hp/hp-lpfc/make_initrd

    Reboot your server with the correct initrd.

  • EVA4400 with embedded switch is not currently supported with SLES 9 SP4.

  • Dynamic LUN addition and removal are supported. However, the ability to dynamically add a new LUN (or a LUN that has been previously removed) using the LUN number of a previously removed LUN is not supported. Dynamic target addition, which is defined as adding a new Fibre Channel target (such as adding a new storage array) to a SAN, is also not supported. The ability to present the new target to a Fibre Channel HBA, and then prompt the operating system to do an online scan (such as using the hp_rescan utility that comes with fibreutils) is not supported with the Emulex failover driver (MultiPulse). If you add a new Fibre Channel target to a host server, you must reboot that server.

  • Emulex HBA driver 7.4.0.39 is required to support QLogic switch firmware 8.0.2.2.0.

This section describes information about using Windows and CNAs/HBAs.

Systems running Windows Server 2008/Windows Server 2008 Service Pack 2 require KB hotfix 976748 to be installed before installing Microsoft Device Specific Module (MSDSM) as a multipath solution. For more information, see the Microsoft Support website:

HP EVA MPIO DSM 4.00.00 prevents BFS on systems running Windows 2003 if there are three or more paths enabled.

Windows driver fails to log back into the Cisco Nexus 5000 switch after switch reboot.

On Windows 2003 and Windows 2008, the link is not reestablished when a Cisco Nexus 5000 switch is rebooted. The workaround is to use the Nexus Shutdown and No Shutdown CLI commands to bring the port back online.

STORport miniport driver installation restrictions

If you are upgrading to the STORport miniport driver, consider the following:

  • The STORport miniport driver is supported on Windows 2003 SP1 and later.

  • Microsoft hotfix KB932755 must be installed before installing Multipath software.

  • If you are running Secure Path for Windows, you must upgrade to Secure Path 4.0c SP2 or later for Windows. STORport is not supported with earlier versions of Secure Path.

Driver installation with HP Smart Component requires a minimum of Windows Server 2003 SP2 or SP1 with update KB932755. Apply the Microsoft STORport update (KB932755) before installing or upgrading to this version of the STORport driver. For boot installations, Windows Server 2003 SP2 install image is required, followed by the KB update.

Consider the following restrictions for HBAnyware:

  • You must manually uninstall any previous versions of HBAnyware before installing the drivers.

  • Before disabling or uninstalling an HBA using Device Manager, you must close HBAnyware.

  • In the presence of a failed path, HBAnyware can remove LUNs from the tree display. The display is corrected when the failed path is restored.

    Many such packages now exist, with more gradually making their way onto the market. Radio decoding software

  • The installation of HBAnyware on IA64 is included in the driver smart component. There is no separate IA64 smart component for HBAnyware.

  • To install HBAnyware for Windows XP:

    1. Download hbanyware_30a16_winxp.zip from the HP website:

    2. Unzip the zip file and run setupapps.exe.

  • When upgrading the x86 (W32) or x64 HBA STORport driver to 2.01a4, any existing HBAnyware installed on the server will uninstall during the driver installation. You must reinstall the latest version of HBAnyware to use the utility.

  • HBAnyware Version 4.1a35 for Integrity is limited to CLI only. There is no HBAnyware GUI version.

The 2.20.006 STORport driver is not supported on Integrity servers running WS2003.

Emulex 2-Gb HBAs and mezzanine cards are not supported with WS2008 R2.

The following Smart Component issues may be observed during driver installation:

  • When using the Smart Component to install drivers, if the following message appears during reboot, ignore it and continue with the reboot procedure. No known issues have been observed in connection with the display of this message.

    The application failed to initialize because the windows station is shutting down.

  • Downgrading to Version 2.0 or later STORport driver does not work when initiated via the Smart Component. To downgrade an HP-branded Emulex HBA:

    1. Run the Smart Component, containing the desired driver, to extract the contents to a folder.

    2. Run the STORport driver installer from the extracted folder using the default values. For example:

      storportminiportcorekit_2-01a4

      This will uninstall the current driver before downgrading to the specified driver version.

  • When using the Smart Component to install drivers, the following message may appear during reboot.

    There was a problem installing this hardware. This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)

    Uninstall and then reinstall your device.

    If the above message appears, click . Do not reply to Microsoft and continue with the reboot procedure. No known issues have been observed in connection with the display of this message.

With Secure Path 4.0c SP1, during a rolling driver upgrade, a blue-screen error may occur under any of the following conditions:

  • Secure Path is not supported on WS2008 or 8-Gb HBAs and 8-Gb mezzanine cards.

  • The server boots from a SAN.

  • All HBAs are accessing their LUNs in a single-path configuration.

  • The HBA is directly attached in a single path to its own MSA controller. If the blue-screen error occurs, reboot the server and inspect the driver revisions to verify that the upgrade is complete on all HBAs. Upgrading to Secure Path 4.0c SP2 corrects this problem.

On Windows Server 2003 systems, clients may be disconnected, generating Event ID 11 and Event ID 15 in the application log. This problem can occur under high-stress conditions due to a SCSIport miniport driver error. It can also cause network timeouts if remote computers are accessing data on drives that use the SCSIport driver on the Windows Server 2003 system.

To correct this problem, install the latest Microsoft hotfix from the website:

  • In a direct connect environment, BFS fails to boot after adding a second path to an EVA4000/6000/8000 running firmware 6.110.

  • BFS on c-Class blade servers fail to boot on an Active/Passive MSA1000/1500 running firmware 5.20.

  • In BFS configurations where there are more than two Emulex HBAs in the same zone as the boot HBA, a crash-dump may not be generated due to a time-out condition when the boot HBA interacts with the non-boot HBAs. A workaround is to reconfigure the zoning such that the boot instance (for each path) is in its own zone separate from the other non-boot HBAs. In some cases, this may also result in faster boot-up times.

  • When installing to storage attached to the 403621-B21 LPe1105 mezzanine card in a VC environment through a Brocade switch, both the target LUN and the WWN for the boot controller will not be visible in the zone, in the switch administrative tool. The workaround is to take note of the mezzanine card's WWN when installing it into the system, or get it from the VC manager or EFI utility. Then manually enter the WWN into the desired zone on the switch when configuring the zone. Scan for targets and continue with normal installation steps to boot from the mezzanine card.

  • EFI boot path configuration will not detect multiple controller ports connected to one HBA through McDATA fabric.

  • In a BFS configuration, the installed HBAs may display different names when viewed through the device manager. This is a cosmetic condition, not a functional issue.

  • The Emulex 81E and 82E HBAs (AJ762A and AJ763A) running the Universal Boot Image 5.03a0, does not support BFS on the DL160 G5 ProLiant server.

  • When the Load Driver option is selected during the operating system build of a Windows 2008 server in a BFS configuration, a multiple entry of the Emulex driver is displayed. If multiple types of HBAs are displayed, select the first entry before proceeding.

  • TFTP-type monitors cannot be used to install an operating system on Itanium servers. Instead, you must use a VGA-type monitor.

  • A direct connect environment is not supported with the EVA4400 or EVA4000/6000/8000 storage arrays (there is no FC switch between the HBA and the storage array).

  • VMware is not supported on the IA64 architecture.

  • Citrix is not supported on the IA64 architecture.

  • Citrix does not support MSA1000 or MSA1500.

November 2010

November 2010

Third edition

Part number: AA-RWQ7C-TE

Type:Firmware - Storage Fibre Channel and Fibre Channel Over Ethernet
Version:2.82x4(8 Mar 2011)
Operating System(s):
OS Independent

Description

Firmware for the FC2242 [A8003A] dual port 4Gb PCI-e Fibre Channel Host Bus Adapter and the Emulex LPe1105-HP 4Gb FC HBA for HP c-Class BladeSystem

Release Notes

End User License Agreements:
HPE Software License Agreement v1

HP StorageWorks Emulex Adapters Release Notes

Itanium® is a registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

Abstract

This document contains supplemental information for the Emulex Fibre Channel host bus adapters (HBAs) and converged network adapters (CNAs) for ProLiant and Integrity servers.

Product models
Supported CNA, HBA, and mezzanine product models
Devices supported
Operating systems
Linux support
Windows support
VMware support
Citrix operating system
Important notes and workarounds
General notes
CNA/HBA Linux notes
CNA/HBA with Windows notes
VMware notes
Citrix notes
Effective date

This section lists the HBAs and CNAs that are supported on ProLiant and Integrity servers.

Table 1, “Supported CNAs and Server LOMs” describes the CNAs and Server LOMs supported on servers running Linux, Windows, VMware, and Citrix operating systems.

Table 1 Supported CNAs and Server LOMs

Model

Windows Server 2003/2008

Linux

VMwareCitrix
CNA
HP StorageWorks CN1000E Dual Port Converged Network Adapter (AW520A)•••—
HP NC551m Dual-port FlexFabric 10-Gb Converged Network Adapter (580151-B21)•••—
Server LOM
Embedded BE2 LOM (AMD)—NC551i Dual-port FlexFabric 10-Gb Converged Network Adapter •••—
Embedded BE3 LOM (Intel)—NC553i Dual Port FlexFabric 10-Gb Converged Network Adapter •••—

NOTE: CNAs and Server LOMs are not supported on Integrity servers.

Table 2, “Supported 8-Gb and 4-Gb HBAs and mezzanine cards” describes the 8-Gb and 4-Gb HBAs and mezzanine cards supported on servers running Linux, Windows, VMware, and Citrix operating systems.

Table 2 Supported 8-Gb and 4-Gb HBAs and mezzanine cards

Model

Windows Server 2003/2008

Linux

VMwareCitrix
8-Gb HBAs and mezzanine cards
HP StorageWorks LPe1205–HP 8-Gb FC Mezzanine Card HBA (456972–B21)[1]••[2]••
HP StorageWorks 81E 8-Gb PCI-X HBA (AJ762A)••[2]••
HP StorageWorks 82E 8-Gb PCI-X Dual Channel HBA (AJ763A)••[2]••
HP PCIe 1-port 8-Gb Fibre Channel HBA (AH402A)•[3]———
HP PCI-e 2-port 8-Gb Fibre Channel HBA (AH403A)•[3]———
4-Gb HBAs and mezzanine cards
HP StorageWorks LPe1105–HP 4-Gb FC HBA for HP c-Class BladeSystem (403621- B21)••••
HP StorageWorks FC2142SR 4-Gb PCI-e FC HBA (A8002A)[4]••••
HP StorageWorks FC2242SR 4-Gb PCI-e dual port FC HBA (A8003A)••••
HP StorageWorks FC2143 4-Gb PCI-X FC HBA (AD167A)••••
HP StorageWorks FC2243 4-Gb PCI-X dual port FC HBA (AD168A)••••

Legend: • = supported; — = not supported

[1] The LPe1205 is supported with most G6 and later ProLiant blade servers with the exception of BL465G6 and BL495G6

[3] IA64 support only

[4] The FC2142 HBA is also supported on XW8400 and XW9300 workstations running Windows XP Professional (32-bit)

Table 3, “Supported 2-Gb HBAs and mezzanine cards” describes the 2-Gb HBAs and mezzanine cards supported on servers running Linux, Windows, VMware, and Citrix operating systems.

NOTE: The HBAs and mezzanine cards listed in Table 3, “Supported 2-Gb HBAs and mezzanine cards” are supported; however, they are no longer available for purchase.

Table 3 Supported 2-Gb HBAs and mezzanine cards

Model

Windows Server 2003/2008

Linux

VMwareCitrix
HP StorageWorks 1050EX 2-Gb PCI-e FC HBA (A7560A)•[1]———
HP StorageWorks A7388A 2-Gb PCI-X FC HBA (A7388A)•———
HP StorageWorks A7387A 2-Gb PCI-X dual port FC HBA (A7387A)•———
HP StorageWorks FCA2404DC 2-Gb PCI-X dual port FC HBA (323264-B21)•[1]———
HP StorageWorks FCA2404 2-Gb PCI-X FC HBA (305573-B21)•[1]———
HP Emulex-based BL20p 2-Gb PCI-X FC mezzanine card (394757-B21)•[1]———
HP Emulex-based BL25/30/35/45p PCI-X FC mezzanine card (394588-B21)•[1]———
HP StorageWorks AB467A 2-Gb 1-port FC HBA •[2]———
HP StorageWorks AB466A 2-Gb 2-port FC HBA •[2]———

Legend: • = supported; — = not supported

[2] Supported on Windows Server IA64 only

NOTE: For the latest information about storage array support, see the HP SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access.

Emulex CNAs, HBAs and LOMs are supported on HP Servers that:

  • Support the Linux, Windows, VMware, and Citrix operating systems listed on the HP website:

  • Support the servers listed on the HP website:

  • Support B-series, C-series, M-series, and H-series switch products. For the latest information, see the HP support website http://welcome.hp.com/country/us/en/support.html and the HP StorageWorks SAN Design Reference Guide at http://www.hp.com/go/sdgmanuals.

See the CNA QuickSpecs for information about the supported servers for the CNAs.

NOTE: The HP CNAs and LOMs are not currently supported on Citrix operating systems.

For more information about the NC551m FlexFabric Adapter, see the HP website:

http://h18004.www1.hp.com/products/blades/components/emulex/nc551m/index.html.

For the latest information about storage array support, see the HP SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access.

This section describes how you can obtain the latest information about supported operating systems and software.

For the latest information about supported HBAs, CNAs, LOMs, and mezzanine cards listed by operating systems, see the HP SPOCK website at: http://h20272.www2.hp.com/Pages/spock2Html.aspx?htmlFile=hw_hbas.html&lang=en&cc=US&

You must sign up for an HP Passport to enable access. From the web page, click HBA Software Support Matrix, and then select your operating system.

This section describes CNA and HBA support for Linux, including prerequisites and installation instructions.

Before you perform CNA or HBA updates, you must do the following:

  • Ensure that the system is running one of the operating system versions listed in HBA Software Support Matrices, available at the SPOCK website http://www.hp.com/storage/spock.

    You must sign up for an HP Passport to enable access.

  • See the HP server PCI slot specifications to determine if your server is compatible with the CNA or HBA.

  • If you are installing the Linux operating system for the first time, load the operating system before you download and install the Linux CNA/HBA/LOM driver from the HP website:

NOTE: Starting with RHEL 5 U3, SLES 10 SP3, and SLES 11; Fibre Channel HBAs and mezzanine cards are supported by Red Hat and Novell in-box drivers (included in the OS distribution), and multipath failover is handled by Device Mapper.

Starting with RHEL 5.5, CNAs are supported by Red Hat in-box drivers. However, SLES 10 and SLES 11 do not support CNAs with in-box drivers. CNA multipath failover is handled by Device Mapper.

NOTE: Do not install fibreutils on systems using CNAs.

For information on installing CNAs, see the HP StorageWorks Converged Network Adapter Installation Guide:

  1. Go to http://www.hp.com/go/support.

  2. Click .

  3. Using the HP model number as your guide, enter the CNA model number in the for product box.

  4. Select Manuals.

This section describes additional Linux installations required for HBAs.

IMPORTANT: If you have both CNAs and Fibre Channel HBAs installed in your system, you must load and use the CNA drivers.

Installing Linux using the in-box driver

Instructions on how to install Linux while using the in-box driver are available on the HP website:

From the website, search for device mapper + boot + san.

If you require multiple-path redundancy, you must install the HP-supplied Device Mapper Multipath Kit after you install the operating system. You can download the kit from the HP website:

You must also install the HP Fibre Channel Enablement Kit (hp-fc-enablement) after installing the operating system.

Installing the HP Fibre Channel Enablement Kit

The HP Fibre Channel Enablement Kit provides additional libraries and configuration utilities to enable HP StorageWorks Fibre Channel storage arrays to work with Linux. The kit is not required to use the lpfc and qla2xxx kernel modules; however, it provides configuration scripts that ensure that your configuration is set properly to work with HP StorageWorks Fibre Channel arrays. The Fibre Channel Enablement Kit also sets the correct lpfc and qla2xxx kernel module settings that are used with Device Mapper multipathing.

NOTE: If you are using any HP management applications, you will need the HBAAPI libraries that are included in the hp-fc-enablement kit.

To install the HP Fibre Channel Enablement Kit:

  1. Download the hp-fc-enablement-yyyy-mm-dd.tar.gz file for your operating system and copy it to the target server.

  2. Untar the enablement kit by executing the command to create the directory, hp-fc-enablement-yyyy-mm-dd:

    # tar zxvf hp-fc-enablement-yyyy-mm-dd.tar.gz

  3. Browse to the directory hp-fc-enablement-yyyy-mm-dd.

  4. Do one of the following to execute the install.sh script:

    • If you are not using Device Mapper multipathing, enter the following command:

      # ./install.sh -s

    • If you are using Device Mapper multipathing, enter the following command:

      # ./install.sh -m

  5. To verify the installation, enter the following commands:

    # rpm -q hp-fc-enablement

    # rpm -q fibreutils

Uninstalling the HP Fibre Channel Enablement Kit

To uninstall the Fibre Channel Enablement Kit, untar the kit as instructed in Step 1 through Step 3 (the section called “Installing the HP Fibre Channel Enablement Kit”), and then execute the install.sh script with the –u option:

# ./install.sh -u

To manually uninstall the enablement kit, enter the following commands:

# rpm -e hp-fc-enablement

# rpm -e fibreutils

Installing the Linux device driver using the HP kit (earlier than RHEL 5 U3)

HP does not support building the lpfc driver from source code. The driver versions for kernel-based distributions are as follows:

  • Driver 7.x.x for the 2.4 kernel

  • Driver 8.x.x.x for the 2.6 kernel

To install the device driver:

  1. Download the driver kit for your distribution. The driver kit file will be in the form of hp-lpfc-yyyy-mm-dd.tar.gz.

  2. Copy the driver kit to the target system.

  3. Uncompress and untar the driver kit by entering the following command:

    # tar zxvf hp-lpfc-yyyy-mm-dd.tar.gz

  4. Change the directory to hp-lpfc-yyyy-mm-dd.

  5. Do one of the following:

    • Enter the following command to install the Linux device driver:

      # ./INSTALL

      The command syntax varies depending on your configuration. Use the –h option of the command to list all supported options. If a driver kit is already installed, you can enter the command without any options, and then the script uses the current configuration.

    • Enter the following command to install the Linux device driver for SLES 10 SP1 only:

      #./INSTALL -p

      • Include the -m option to force the installation to failover mode.

        #./INSTALL –mp

      • Use the –s option to force the installation to single-path mode.

        #./INSTALL –s

        The INSTALL script installs the appropriate driver for your configuration and the appropriate fibreutils. When the script is finished, either reload the Emulex driver modules (lpfc, lpfcdfc, and lpfcmpl) or reboot your server.

Loading the driver

To load the driver, enter the following commands:

# modprobe lpfc

# modprobe lpfcdfc

NOTE: The command modprobe lpfcdfc is for RHEL 4 Ux and SLES 9 SPx.

# modprobe lpfcmpl

NOTE: The command modprobe lpfcmpl is for a MultiPulse configuration only.

Rebooting the server

To reboot the server, enter the following command:

# reboot

If your boot device is a SAN attached device, you must reboot your server.

Verifying the driver version

To verify the driver version, use the RPM command with the -q option.

# rpm -q hp-lpfc

# rpm -q hp-multipulse

For MultiPulse configuration only:

# rpm -q fibreutils

Unloading the driver

To unload the driver, enter the following commands:

# modprobe –r lpfcmpl

NOTE: The command modprobe –r lpfcmpl is for MultiPulse configuration only.

NOTE: The command modprobe –r lpfcdfc is for RHEL 4 Ux and SLES 9 SPx.

# modprobe –r lpfcdfc

# modprobe –r lpfc

Installing HBAnyware on Linux

To install HBAnyware on a Linux system:

  1. Download the file HP_ElxApps-<Kernel Version>-<HBAnyware Version>-<Driver Version>.zip to the target system.

    Example:HP_ElxApps-26-3.2a16-8.1.10.11.zip

    NOTE: For information about HBAnyware and driver versions, see Linux support. Use kernel Version 26 for 2.6 kernels and kernel Version 24 for 2.4 kernels.

  2. Unzip the file on the target system.

    Example:# unzip HP_ElxApps-26-3.2a16-8.1.10.11.zip

  3. Make the file executable under Linux.

    Example:# chmod +x HP_ElxApps-26-3.2a16-8.1.10.11.bin

  4. Install the application.

    Example: #./HP_ElxApps-26-3.2a16-8.1.10.11.bin

  5. Launch the application.

    Example: # HBAnyware or # /usr/sbin/hbanyware/hbanyware

    NOTE: For more information, see the HBAnyware online help.

    HBAnyware 3.4a16 has a known presentation issue with the 8.0.16.40 driver and the AJ762A and AJ763A HBAs. The link speed is not displayed. This will be corrected in a future release.

Determining the CNA/HBA driver and firmware versions in Linux

You can use OneCommand Manager or HBAnyware to view a list of CNAs/HBAs driver and firmware information.

This section describes CNA/HBA support for Windows.

CNAs/HBAs/LOMs are supported on ProLiant servers with Enterprise, Standard, Storage Server, and Datacenter versions of the following:

  • CNAs/LOMs on Windows 2003:

  • HBAs on Windows 2003:

    • Windows Server 2003 x86 – SP1, R2, SP2 (32-bit) (STORport and SCSIport)

    • Windows Server 2003 x64 – SP1, R2, SP2 (64-bit) (STORport only)

  • Windows Server 2008 W32 – SP2

  • Windows Server 2008 x64 – SP2, R2

HP offers a bundle for small businesses running Windows XP Professional. Table 4, “Supported configuration for Windows XP Professional (32-bit)” lists the contents of the bundle.

Table 4 Supported configuration for Windows XP Professional (32-bit)

Windows driver, workstation, switch, storage array, and utility requirements

HBA

HP StorageWorks FC2142SR (product number A8002A)

HBA firmware/BIOS

2.72a2 /1.71a0 (distributed in Universal Boot Image 5.02a1)

Windows driver

SCSIport miniport 5.30a2

Workstations

XW8400, XW9300

FC switch

Cisco 8-port MDS 9124

Storage array

EVA4000

HBAnyware

3.0a16_winxp

Restrictions

Single path only. BFS is not supported.

HP supports the use of Linux and Windows as a guest on VMware ESX Versions 4.x and 3.x. When running VMware, Fibre Channel HBAs and CNAs are supported by in-box drivers supplied with VMware ESX. Linux Fibre Channel HBA drivers are not supported on the Virtual OS (VOS).

NOTE: You are not required to install the Emulex driver because it is shipped with the ESX server.

To ensure that your HBA/CNA is supported by HP and VMware, see the VMware Compatibility Guide at:

For information about boot from SAN (BFS) on VMware, see HP StorageWorks Fibre Channel Host Bus Adapters Software Guide for Linux, available at:

HP supports the Citrix hypervisor. For more information, see the HP Virtualization with Citrix website: http://www.hp.com/go/citrix

This section describes important notes and workarounds for issues for Emulex CNA/HBA adapters running Linux and Windows.

When using a C-series Converged Network Switch (HP Nexus 5000) along with the HP Virtual Connect FlexFabric 10-Gb/24-port module, NPIV must be enabled on the C-series switch.

The CN1000E maximum supported Ethernet Jumbo Packet frame size is 8192 bytes.

The CN1000E maximum supported optical cable length is 40 meters.

DL16x and DL18x Servers require extra time to boot from SAN.

When the CN1000E adapter is used as the boot device in a DL16x or DL18x server, the server may pause for approximately 90 seconds when it is expected to start booting from the hard disk. After this delay, the boot process resumes as expected.

Update DL/SL100-series BIOS before installing CN1000e

Before installing an HP CN1000e into a DL/SL100-series server, you must upgrade the server BIOS to 2010.02.04 or later. The BIOS is available for download from the HP Download Drivers and Software website:

HP recommends that you implement zoning by CNAs/HBAs, as described in the HP StorageWorks SAN Design Reference Guide, available at:

HP ProLiant DL380 (G4) servers must have System ROMPaq firmware 4.05 P51-08/16/2005 or later to be compatible with the FC2142SR and FC2242SR. Failure to use this ROMPaq version can cause the HBAs to hang during the power-on self-test (POST). For more information, see the HP website:

This section describes restrictions that apply to Linux and this release of the CNAs/HBAs:

  • Firmware download in SLES 10 SP3 can cause the system to hang.

    When downloading firmware to the CN1000E adapters in SLES 10 SP3 using the OneCommand Manager or hbacmd, the download may complete but cause the system to become unresponsive or hang. Though the firmware download is successful, a hard reboot of the server may be required to enable the new firmware.

  • HP and Novell are evaluating a report that Reiserfs filesystems display unexpected behavior under heavy load. Other filesystems such as xfs and ext3 are not affected by this behavior. HP recommends that you use either the xfs or ext3 filesystem. This is a high priority issue that is in the process of being resolved. When a resolution is found, a maintenance update will be available on the Novell website:

  • HP recommends that you use the ext3 filesystem in high availability (HA) environments. For information on how to use other Linux filesystems in an HA environment, see SLES 11 Administration Guide, available at the Novell website http://www.novell.com/documentation/sles11, and the Red Hat Deployment Guide, available at the Red Hat website http://www.redhat.com.

    For information on the differences between ext2 and ext3, see the operating system documentation.

  • SLES 10 SP2 has an issue displaying 8-Gb HBA speed. You can correct the problem using kernel Version 2.6.16.60-0.25.

  • BFS is not supported on the A8002A with RHEL 4 U3 and U4, IA64, or SLES 10 IA64.

  • Beginning with RHEL 6.0 and SLES 11, HP no longer supports XP128 or XP1024.

    Beginning with RHEL 5.3 and SLES 10 SP3, HP no longer supports MSA1000, MSA1500, EVA3000, or EVA5000.

  • For Modular Smart Arrays and Enterprise Virtual Array, active/passive storage arrays are supported in single-path mode only.

  • For the MSA2000 family of disk arrays only:

    • The minimum required firmware is J200P24-01.

    • Creating virtual disks (vdisks) online or offline without volumes during the virtual disk creation process is not supported. You must create at least one volume during the virtual disk creation.

    • MultiPulse is not supported. See the HP Device Mapper documentation for multipathing support.

    • BFS is not currently supported.

  • The Emulex MultiPulse 2.2.22, 2.2.38, 2.2.39, and 2.2.44 drivers support active/active storage arrays only.

  • If using MultiPulse 2.1.x, you can have a maximum of four physical paths to a LUN. More than four paths can cause a failure.

  • If using MultiPulse 2.2.x, you can have a maximum of eight physical paths to a LUN. More than eight paths can cause a failure.

  • MultiPulse can coexist with multipathing products such as the Emulex failover driver and Secure Path. However, MultiPulse works only with Emulex-based HBAs; it will not configure multiple paths for other HBAs in the system.

  • Because the order in which a switch reports Fibre Channel ports to a name server can vary, the order in which LUNs are discovered can vary between system boots.

    HP recommends that you use the udev utility to ensure that the name of a device does not change between system boots. For more information, see the udev website:

  • When using MultiPulse with SUSE Linux systems in BFS configurations, HP recommends that you use the udev utility to ensure that your system boots successfully. For more information about this procedure, see the HP StorageWorks Fibre Channel Host Bus Adapters Software Guide for Linux, available at the HP website:

  • If you are installing the Linux operating system for the first time, load the operating system before you download and install the supported Linux HBA driver from the HP website:

  • XP LUNs presented to Linux hosts must start with LUN 0.

  • HP recommends that you implement zoning by HBA, as described in the HP StorageWorks SAN Design Reference Guide, available on the website:

  • A maximum of 10 targets are supported in a BFS zone.

  • On an sx2000 system with the default logging level, a call trace may appear in the /var/log/messages file during failover events.

  • When running the scsi_info command on older XP arrays such as XP1024/128, you may see output similar to that shown in the following example. Ignore the error, and note that the XP array's WWN is not all zeros.

    The XP array returns inquiry data that differs slightly from that returned by EVA or MSA arrays.

    [root@coco /]# scsi_info /dev/sdal SCSI_ID='4,0,8,0':
    VENDOR='HP':MODEL='OPEN-

    E':FW_REV='5005':WWN='0000000000000000':LUN='5235303020303030-3130353930203030'

    [root@coco /]# scsi_info /dev/sdam

    SCSI_ID='4,0,8,1':VENDOR='HP':MODEL='OPEN-

    E':FW_REV='5005':WWN='0000000000000000':LUN='5235303020303030-3130353930203030'

    [root@coco /]# scsi_info /dev/sdan

    SCSI_ID='4,0,9,0':VENDOR='HP':MODEL='OPEN- 3':FW_REV='2114':WWN='03000000002018e9':LUN='5234353120303030-3330313033203030'

    [root@coco /]# scsi_info /dev/sdao SCSI_ID='4,0,9,1':VENDOR='HP':MODEL='OPEN-

    3':FW_REV='2114':WWN='0b00000000600000':LUN='5234353120303030-3330313033203030'

  • RHEL 5 U3 and SLES 10 SP3 do not support active/passive arrays.

  • Installing PSP 7.91/92 causes fibreutils to downgrade. Reinstall fibreutils rpm from the downloaded kit.

    Example:

    #rpm –fvh fibreutils.<version>.linux.<arch>.rpm

  • When an EVA4400 with embedded switch is configured in a heterogeneous SAN, HP recommends that you use a text editor to edit the HBA configuration file etc/modprobe.conf.

    options lpfcmpl mpl_hbeat_tmo_busy=0

    Save the file, and then run the make_initrd script.

    # /opt/hp/hp-lpfc/make_initrd

    Reboot your server with the correct initrd.

  • EVA4400 with embedded switch is not currently supported with SLES 9 SP4.

  • Dynamic LUN addition and removal are supported. However, the ability to dynamically add a new LUN (or a LUN that has been previously removed) using the LUN number of a previously removed LUN is not supported. Dynamic target addition, which is defined as adding a new Fibre Channel target (such as adding a new storage array) to a SAN, is also not supported. The ability to present the new target to a Fibre Channel HBA, and then prompt the operating system to do an online scan (such as using the hp_rescan utility that comes with fibreutils) is not supported with the Emulex failover driver (MultiPulse). If you add a new Fibre Channel target to a host server, you must reboot that server.

  • Emulex HBA driver 7.4.0.39 is required to support QLogic switch firmware 8.0.2.2.0.

This section describes information about using Windows and CNAs/HBAs.

Systems running Windows Server 2008/Windows Server 2008 Service Pack 2 require KB hotfix 976748 to be installed before installing Microsoft Device Specific Module (MSDSM) as a multipath solution. For more information, see the Microsoft Support website:

HP EVA MPIO DSM 4.00.00 prevents BFS on systems running Windows 2003 if there are three or more paths enabled.

Windows driver fails to log back into the Cisco Nexus 5000 switch after switch reboot.

On Windows 2003 and Windows 2008, the link is not reestablished when a Cisco Nexus 5000 switch is rebooted. The workaround is to use the Nexus Shutdown and No Shutdown CLI commands to bring the port back online.

STORport miniport driver installation restrictions

If you are upgrading to the STORport miniport driver, consider the following:

  • The STORport miniport driver is supported on Windows 2003 SP1 and later.

  • Microsoft hotfix KB932755 must be installed before installing Multipath software.

  • If you are running Secure Path for Windows, you must upgrade to Secure Path 4.0c SP2 or later for Windows. STORport is not supported with earlier versions of Secure Path.

Driver installation with HP Smart Component requires a minimum of Windows Server 2003 SP2 or SP1 with update KB932755. Apply the Microsoft STORport update (KB932755) before installing or upgrading to this version of the STORport driver. For boot installations, Windows Server 2003 SP2 install image is required, followed by the KB update.

Consider the following restrictions for HBAnyware:

  • You must manually uninstall any previous versions of HBAnyware before installing the drivers.

  • Before disabling or uninstalling an HBA using Device Manager, you must close HBAnyware.

  • In the presence of a failed path, HBAnyware can remove LUNs from the tree display. The display is corrected when the failed path is restored.

  • The installation of HBAnyware on IA64 is included in the driver smart component. There is no separate IA64 smart component for HBAnyware.

  • To install HBAnyware for Windows XP:

    1. Download hbanyware_30a16_winxp.zip from the HP website:

    2. Unzip the zip file and run setupapps.exe.

  • When upgrading the x86 (W32) or x64 HBA STORport driver to 2.01a4, any existing HBAnyware installed on the server will uninstall during the driver installation. You must reinstall the latest version of HBAnyware to use the utility.

  • HBAnyware Version 4.1a35 for Integrity is limited to CLI only. There is no HBAnyware GUI version.

The 2.20.006 STORport driver is not supported on Integrity servers running WS2003.

Emulex 2-Gb HBAs and mezzanine cards are not supported with WS2008 R2.

The following Smart Component issues may be observed during driver installation:

  • When using the Smart Component to install drivers, if the following message appears during reboot, ignore it and continue with the reboot procedure. No known issues have been observed in connection with the display of this message.

    The application failed to initialize because the windows station is shutting down.

  • Downgrading to Version 2.0 or later STORport driver does not work when initiated via the Smart Component. To downgrade an HP-branded Emulex HBA:

    1. Run the Smart Component, containing the desired driver, to extract the contents to a folder.

    2. Run the STORport driver installer from the extracted folder using the default values. For example:

      storportminiportcorekit_2-01a4

      This will uninstall the current driver before downgrading to the specified driver version.

  • When using the Smart Component to install drivers, the following message may appear during reboot.

    There was a problem installing this hardware. This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)

    Uninstall and then reinstall your device.

    If the above message appears, click . Do not reply to Microsoft and continue with the reboot procedure. No known issues have been observed in connection with the display of this message.

With Secure Path 4.0c SP1, during a rolling driver upgrade, a blue-screen error may occur under any of the following conditions:

  • Secure Path is not supported on WS2008 or 8-Gb HBAs and 8-Gb mezzanine cards.

  • The server boots from a SAN.

  • All HBAs are accessing their LUNs in a single-path configuration.

  • The HBA is directly attached in a single path to its own MSA controller. If the blue-screen error occurs, reboot the server and inspect the driver revisions to verify that the upgrade is complete on all HBAs. Upgrading to Secure Path 4.0c SP2 corrects this problem.

On Windows Server 2003 systems, clients may be disconnected, generating Event ID 11 and Event ID 15 in the application log. This problem can occur under high-stress conditions due to a SCSIport miniport driver error. It can also cause network timeouts if remote computers are accessing data on drives that use the SCSIport driver on the Windows Server 2003 system.

To correct this problem, install the latest Microsoft hotfix from the website:

  • In a direct connect environment, BFS fails to boot after adding a second path to an EVA4000/6000/8000 running firmware 6.110.

  • BFS on c-Class blade servers fail to boot on an Active/Passive MSA1000/1500 running firmware 5.20.

  • In BFS configurations where there are more than two Emulex HBAs in the same zone as the boot HBA, a crash-dump may not be generated due to a time-out condition when the boot HBA interacts with the non-boot HBAs. A workaround is to reconfigure the zoning such that the boot instance (for each path) is in its own zone separate from the other non-boot HBAs. In some cases, this may also result in faster boot-up times.

  • When installing to storage attached to the 403621-B21 LPe1105 mezzanine card in a VC environment through a Brocade switch, both the target LUN and the WWN for the boot controller will not be visible in the zone, in the switch administrative tool. The workaround is to take note of the mezzanine card's WWN when installing it into the system, or get it from the VC manager or EFI utility. Then manually enter the WWN into the desired zone on the switch when configuring the zone. Scan for targets and continue with normal installation steps to boot from the mezzanine card.

  • EFI boot path configuration will not detect multiple controller ports connected to one HBA through McDATA fabric.

  • In a BFS configuration, the installed HBAs may display different names when viewed through the device manager. This is a cosmetic condition, not a functional issue.

  • The Emulex 81E and 82E HBAs (AJ762A and AJ763A) running the Universal Boot Image 5.03a0, does not support BFS on the DL160 G5 ProLiant server.

  • When the Load Driver option is selected during the operating system build of a Windows 2008 server in a BFS configuration, a multiple entry of the Emulex driver is displayed. If multiple types of HBAs are displayed, select the first entry before proceeding.

  • TFTP-type monitors cannot be used to install an operating system on Itanium servers. Instead, you must use a VGA-type monitor.

  • A direct connect environment is not supported with the EVA4400 or EVA4000/6000/8000 storage arrays (there is no FC switch between the HBA and the storage array).

  • VMware is not supported on the IA64 architecture.

  • Citrix is not supported on the IA64 architecture.

  • Citrix does not support MSA1000 or MSA1500.

November 2010

November 2010

Third edition

Part number: AA-RWQ7C-TE

Revision History

Legal Disclaimer: Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models.

HP maintains the SPOCK website as the primary source of detailed information about HP storage product configurations, including operating system, software, and firmware version support. For the latest information about storage array support, see the HP SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access.

Some HBA/CNA download kits include a readme.txt file that may contain additional information about installing firmware and drivers, plus enhancements and fixes in the current release. Information in the readme.txt file supersedes this and other HP Emulex documents.

This section lists the HBAs and CNAs that are supported on ProLiant and Integrity servers. Although CNAs have FCoE, NIC, and iSCSI functionality, this document addresses FCoE functionality only.

Table 1, “Supported CNAs and server LOMs” describes the CNAs and server LOMs (LAN on motherboard) supported on servers running Windows, Linux, VMware, and Citrix operating systems.

NOTE: The Restriction of Hazardous Substances Directive (RoHS) is a European Union directive that restricts the use of certain hazardous materials in the manufacture of electronic and electrical equipment.

Table 1 Supported CNAs and server LOMs

Model Windows Server 2003Windows Server 2008Windows Server 2012LinuxVMwareCitrix[1]
CNA
HP CN1100E Dual Port Converged Network Adapter (BK835A)••••••
HP CN1000E Dual Port Converged Network Adapter (AW520A/AW520B)[2]••••••
HP NC551m Dual-port FlexFabric 10-Gb Converged Network Adapter (580151-B21)••••••
HP NC553m Dual-port FlexFabric 10-Gb Converged Network Adapter (613431-B21)••••••
HP FlexFabric 10Gb 2-port 554M Adapter (647590-B21) —•••••
Server LOM
Embedded NC551i Dual-port FlexFabric 10-Gb Converged Network Adapter ••••••
Embedded NC553i Dual Port FlexFabric 10-Gb Converged Network Adapter ••••••
HP FlexFabric 10Gb 2-port 554FLB Adapter (647586-B21) —•••••
HP FlexFabric 10Gb 2-port 554FLR-SFP+ Adapter (629142-B21) —•••••

Legend: • = supported; — = not supported

[1] Support is limited to Citrix XenServer 5.6 with lpfc driver 2.102.485 and 8.2.8.47.7p driver disk. For more information or to download the driver update, see the Citrix Knowledge Center website at http://support.citrix.com/article/CTX128028.

[2] The AW520B is the new RoHS-compliant CNA that replaces the AW520A. These models are functionally equivalent and interchangeable.

Table 2, “Supported HBAs and mezzanine cards” describes the HBAs and mezzanine cards supported on servers running Windows, Linux, VMware, and Citrix operating systems.

Table 2 Supported HBAs and mezzanine cards

Model Windows Server 2003Windows Server 2008Windows Server 2012LinuxVMwareCitrix
16-Gb HBAs
HP SN1000E 16Gb Fibre Channel Host Bus Adapter—single port (QR558A)—•••••
HP SN1000E 16Gb Fibre Channel Host Bus Adapter—dual port (QR559A)—•••••
8-Gb HBAs and mezzanine cards
HP LPe1205A 8Gb FC HBA for BladeSystem c-Class (659818-B21)[1]—•••••
HP StorageWorks LPe1205–HP 8-Gb FC Mezzanine Card HBA (456972–B21)[2]••••[3]••
HP 81E 8-Gb PCI-X HBA (AJ762A/AJ762B)[3][4]••••••
HP StorageWorks 82E 8-Gb PCI-X Dual Channel HBA (AJ763A/AJ763B)[3][5]••••••
HP PCIe 1-port 8-Gb Fibre Channel HBA (AH402A)•[6]•[6]————
HP PCIe 2-port 8-Gb Fibre Channel HBA (AH403A)•[6]•[6]————
4-Gb HBAs and mezzanine cards
HP StorageWorks LPe1105–HP 4-Gb FC HBA for HP c-Class BladeSystem (40362-B21)••••••
HP FC2142SR 4-Gb PCIe FC HBA (A8002A/A8002B)[7][8]••••••
HP FC2242SR 4-Gb PCIe dual port FC HBA (A8003A/A8003B)[9]••••••

Legend: • = supported; — = not supported

[1] The HP LPe1205A is supported in Gen8 blade servers only.

[2] The LPe1205 is supported with most G6 and later ProLiant blade servers with the exception of BL465G6 and BL495G6.

[4] The AJ762B is the new RoHS-compliant HBA that replaces the AJ762A. These models are functionally equivalent and interchangeable.

[5] The AJ763B is the new RoHS-compliant HBA that replaces the AJ763A. These models are functionally equivalent and interchangeable.

[7] The FC2142 HBA is also supported on XW8400 and XW9300 workstations running Windows XP Professional (32-bit).

[8] The A8002B is the new RoHS-compliant HBA that replaces the A8002A. These models are functionally equivalent and interchangeable.

[9] The A8003B is the new RoHS-compliant HBA that replaces the A8003A. These models are functionally equivalent and interchangeable.

Table 3, “Supported legacy HBAs and mezzanine cards” describes the Legacy HBAs and mezzanine cards supported on servers running Windows, Linux, VMware, and Citrix operating systems.

NOTE: The HBAs and mezzanine cards listed in Table 3, “Supported legacy HBAs and mezzanine cards” are supported; however, they are no longer available for purchase.

Table 3 Supported legacy HBAs and mezzanine cards

Model Windows Server 2003/2008LinuxVMwareCitrix
4-Gb HBAs
HP StorageWorks FC2143 4-Gb PCI-X FC HBA (AD167A)••••
HP StorageWorks FC2243 4-Gb PCI-X dual port FC HBA (AD168A)••••
2-Gb HBAs and mezzanine cards
HP StorageWorks 1050EX 2-Gb PCIe FC HBA (A7560A)•[1]———
HP StorageWorks A7388A 2-Gb PCI-X FC HBA (A7388A)•———
HP StorageWorks A7387A 2-Gb PCI-X dual port FC HBA (A7387A)•———
HP StorageWorks FCA2404DC 2-Gb PCI-X dual port FC HBA (323264-B21)•[1]———
HP StorageWorks FCA2404 2-Gb PCI-X FC HBA (305573-B21)•[1]———
HP Emulex-based BL20p 2-Gb PCI-X FC mezzanine card (394757-B21)•[1]———
HP Emulex-based BL25/30/35/45p PCI-X FC mezzanine card (394588-B21)•[1]———
HP StorageWorks AB467A 2-Gb 1-port FC HBA •[2]———
HP StorageWorks AB466A 2-Gb 2-port FC HBA •[2]———

Legend: • = supported; — = not supported

[2] Supported on Windows Integrity servers only

Emulex CNAs, HBAs, and LOMs are supported on HP servers that:

  • Support the Linux, Windows, VMware, and Citrix operating systems listed on the HP website:

  • Support the servers listed on the HP website:

  • Support B-series, C-series, M-series/McDATA, and H-series switch products. For the latest information, see the HP support website at http://welcome.hp.com/country/us/en/support.html and the HP SAN Design Reference Guide at http://www.hp.com/go/sdgmanuals.

For information about the supported servers for the CNAs, see the CNA QuickSpecs.

Before you perform CNA or HBA updates, you must do the following:

  • Ensure that the system is running one of the operating system versions listed in HBA Software Support Matrices, available at the SPOCK website http://www.hp.com/storage/spock.

    You must sign up for an HP Passport to enable access.

  • See the HP server PCI slot specifications to determine if your server is compatible with the CNA or HBA.

  • If you are installing the Linux operating system for the first time, load the operating system before you download and install the Linux CNA/HBA/LOM driver from the HP website:

For information on installing CNAs, see HP Emulex Converged Network Adapter Installation Guide. For information on installing HBAs, see HP Emulex Fibre Channel Host Bus Adapter and Driver Installation Guide. To download either of these guides:

  1. Go to http://www.hp.com/support/manuals.

  2. Using the HP model number as your guide, enter the adapter model number in the Search products box, and then click >>.

IMPORTANT: If you have both CNAs and Fibre Channel HBAs installed in your Linux system, you must install and use the CNA drivers.

If you have both CNAs and Fibre Channel HBAs installed in your Windows system, you must install the FCoE CNA driver and the Fibre Channel HBA driver.

This section describes how you can obtain the latest information about supported operating systems and software.

For the latest information about supported HBAs, CNAs, LOMs, and mezzanine cards listed by operating systems, see the HP SPOCK website at:

You must sign up for an HP Passport to enable access. From the web page, click HBA Software Support Matrix, and then select your operating system.

This section contains information about CNA and HBA support for Linux.

For HBA Linux support information, see http://h18006.www1.hp.com/storage/saninfrastructure/hba.html.

For CNA Linux support information, see the HP Converged Network Adapters website at http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/12169-304608-4109633-4109633-4109633-4118472.html?dnr=1.

For more information, see the readme.txt file packaged with the kit.

Determining the CNA/HBA driver and firmware versions in Linux

You can use OneCommand Manager or HBAnyware to view a list of CNA/HBA driver and firmware information.

NOTE: Newer versions of the HBA driver use Emulex OneCommand software for HBA management and older versions of the driver use Emulex HBAnyware software. To determine the HBA management software needs for your configuration, see HBA Software Support Matrix available on the HP SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access.

This section describes CNA/HBA support for Windows.

CNAs/HBAs/LOMs are supported on ProLiant servers with Enterprise, Standard, Storage Server, and Datacenter versions of the following:

  • CNAs/LOMs on Windows:

    • Windows Server 2003 x86, x64 – R2 SP2

    • Windows Server 2008 W32 – SP2 and Windows Server 2008 x64 – SP2, R2: SP2

    • Windows Server 2012

  • HBAs on Windows:

    • Windows Server 2003 x86 – SP1, R2, SP2 (32-bit) (STORport and SCSIport)

    • Windows Server 2003 x64 – SP1, R2, SP2 (64-bit) (STORport only)

    • Windows Server 2003, IA64 – SP1, SP2

    • Windows Server 2008 W32 – SP2

    • Windows Server 2008 x64 – SP2, R2

    • Windows Server 2008, IA64 – SP2, R2

    • Windows Server 2012

HP supports the use of Windows and Linux as a guest operating system on VMware ESX versions 4.x and 5.x. For information on VMware driver support, see the HP Server Virtualization website at https://h20392.www2.hp.com/portal/swdepot/displayProductsList.do?category=SVIRTUAL. Windows and Linux Fibre Channel HBA drivers are not used on the virtual operating system.

To ensure that your HBA/CNA is supported by HP and VMware, see VMware Compatibility Guide at:

NOTE: VMware is not supported on the IA64 architecture.

HP supports the Citrix Hypervisor. For more information, see the HP Virtualization with Citrix website:

NOTE: HP does not support HP Emulex Fibre Channel or CNA FCoE products on Citrix XenServer 5.6 FP1. HP Emulex CNAs only support NIC functionality of Citrix XenServer 5.6 FP1. For more information, see the Citrix Knowledge Center article at:

For Fibre Channel and FCoE support, you must upgrade to Citrix XenServer 5.6 SP2 or later.

This section describes restrictions, notes, and issue workarounds for Emulex CNA/HBA adapters.

The notes in this section apply to all operating systems.

HP Emulex CNA connected to ports on HP P9500 or XP20000/24000 storage arrays can result in channel adapter (front-end port) blockades

This blocked condition results in a loss of access to storage by the paths provided through the channel adapter (CHA) to all connected hosts. This issue can occur with HP Emulex CNA firmware earlier than 4.1.450.14. To prevent this issue, you must ensure that the HP Emulex CNA firmware version is 4.1.450.14 or later. HP recommends that you install HP Emulex CNA firmware 4.1.450.16 or later.

When updating firmware on an Emulex adapter, all Emulex adapters installed in the server must be enabled. One or more disabled adapters or adapter ports will cause the firmware update to fail.

The HP LPe1205A BIOS does not auto-negotiate to the highest possible speed when the adapter installed in a BL465 Gen8 server. When searching for targets, the Boot BIOS negotiates to the next-highest speed (4 Gb for 8 Gb connections or 2 Gb for 4 Gb connections). When the operating system driver comes online, the link re-negotiates to the expected speed.

The SN1000E 16 Gb HBA does not support 2 Mb transfer sizes.

You can use the server ROM-Based Setup Utility (RSBU) to view or change the CNA personality (iSCSI or FCoE).

When a CNA is configured for FCoE, you must enable the network boot on all NIC ports in order to detect LUNs. Use the server RBSU Embedded NICs menu to enable the network boot. In a blade environment, if you configure FCoE with Vitual Connect, VC enables network boot in the RBSU automatically.

HP Fibre Channel Enablement Kit and OneCommand Manager Application interoperability

The HP Fibre Channel Enablement Kit and OneCommand Manager both install API libraries and can be used individually. For those configurations using both kits, HP recommends that you install the Enablement Kit before you install OneCommand Manager. When uninstalling, HP recommends that you remove OneCommand Manager before you remove the Enablement Kit.

Emulex Lpe12000 Driver Vmware

The CN1000E maximum supported Ethernet Jumbo Packet frame size is 8192 bytes.

The CN1000E maximum supported optical cable length is 40 meters.

When using a C-series Converged Network Switch (HP Nexus 5000) with the HP Virtual Connect FlexFabric 10-Gb/24-port module, NPIV must be enabled on the C-series switch.

DL16x and DL18x Servers require extra time to boot from SAN.

When the CN1000E is used as the boot device in a DL16x or DL18x server, the server can pause for approximately 90 seconds when it is expected to start booting from the hard disk. After this delay, the boot process resumes as expected.

Update DL/SL100-series BIOS before installing CN1000E

Before installing an HP CN1000E into a DL/SL100-series server, you must upgrade the server BIOS to 2010.02.04 or later. The BIOS is available for download from the HP Download Drivers and Software website:

HP recommends that you implement zoning by CNAs/HBAs, as described in the HP SAN Design Reference Guide, available at:

Emulex Driver Download

HP ProLiant DL380 (G4) servers must have System ROMPaq firmware 4.05 P51-08/16/2005 or later to be compatible with the FC2142SR and FC2242SR. Failure to use this ROMPaq version can cause the HBAs to hang during the power-on self-test (POST). For more information, see the HP website:

This section provides information about Linux and CNAs/HBAs.

RHEL6.4 Inbox online firmware update for CNAs using ethtools

You must use ethtools to perform an online CNA firmware update while running RHEL6.4 Inbox. To do this:

Emulex Lightpulse Hba Driver

  1. Copy the latest firmware image (.ufi) from http://www.hp.com/support/downloads to the /lib/firmware directory:

    # cp oc1x-4.x.xxx.xx.ufi /lib/firmware

  2. Start the update process:

    # ethtool -f eth<X> oc1x-4.x.xxx.xx 0

  3. Reboot the system to enable the new firmware image to take effect.

There is no management support for CNAs using the OneCommand Management Utility for RHEL6.4 Inbox at this time.

Fibre Channel HBAs do support OneCommand for RHEL6.4 Inbox.

In a BFS configuration, a bindings file becomes out-of-sync between the copy in /var/lib/multipath and a copy in the initrd image the server uses during boot.

A workaround is documented in the Native Linux Device-Mapper Multipath for HP Storage Disk Arrays reference guide, available at http://spock.corp.hp.com/utility/document.aspx?docurl=Shared%20Documents/an/solutions_linux/Device_Mapper_Multipath_RG_2012_02_21.pdf

SCSI reset status incorrectly reported in /var/log/messages

An SLES 11 SP1 x64 system with an lpfc driver 8.5.3.44 can incorrectly report SCSI resets status in /var/log/messages similar to the following:

Aug 9 12:01:12 xyz kernel: [ 6783.419080] lpfc 0000:a1:00.0: 4:(0):0714 SCSI layer issued Bus Reset Data: x0

You can ignore this message.

Firmware download in SLES 10 SP3 can cause the system to hang.

When downloading firmware to the CNA in SLES 10 SP3 using OneCommand Manager or hbacmd, the download may complete but cause the system to become unresponsive or hang. Though the firmware download is successful, a hard reboot of the server may be required to enable the new firmware.

ReiserFS file systems can exhibit unexpected behavior under heavy loads. HP recommends that you use either the xfs or ext3 file system. For up-to-date recommendations, see the Novell website:

HP recommends that you use the ext3 file system in high availability (HA) environments. For information on how to use other Linux file systems in an HA environment, see SLES 11 Administration Guide, available at the Novell website http://www.novell.com/documentation/sles11 and the Red Hat Deployment Guide, available at the Red Hat website http://www.redhat.com.

For information on the differences between ext2 and ext3, see the operating system documentation.

For the MSA2000 family of disk arrays:

  • The minimum required firmware is J200P24-01.

  • Creating virtual disks (vdisks) online or offline without volumes during the virtual disk creation process is not supported. You must create at least one volume during the virtual disk creation.

  • MultiPulse is not supported. For information about multipathing support, see the HP Device Mapper documentation.

  • The Emulex MultiPulse 2.2.22, 2.2.38, 2.2.39, and 2.2.44 drivers support active/active storage arrays only.

  • If using MultiPulse 2.2.x, you can have a maximum of eight physical paths to a LUN. More than eight paths can cause a failure.

  • MultiPulse can coexist with multipathing products such as the Emulex failover driver and Secure Path. However, MultiPulse works only with Emulex-based HBAs; it will not configure multiple paths for other HBAs in the system.

Because the order in which a switch reports Fibre Channel ports to a name server can vary, the order in which LUNs are discovered can vary between system boots.

HP recommends that you use the udev utility to ensure that the name of a device does not change between system boots. For more information, see the udev website:

XP LUNs presented to Linux hosts must start with LUN 0.

A maximum of 10 targets are supported in a BFS zone.

On an sx2000 system with the default logging level, a call trace may appear in the /var/log/messages file during failover events.

When running the scsi_info command on older XP arrays, such as XP1024/128, you may see output similar to that shown in the following example. Ignore the error, and note that the WWN is not all zeros.

The XP array returns inquiry data that differs slightly from that returned by EVA or MSA arrays.

[root@coco /]# scsi_info /dev/sdal SCSI_ID='4,0,8,0':
VENDOR='HP':MODEL='OPEN-

E':FW_REV='5005':WWN='0000000000000000':LUN='5235303020303030-3130353930203030'

[root@coco /]# scsi_info /dev/sdam

SCSI_ID='4,0,8,1':VENDOR='HP':MODEL='OPEN-

E':FW_REV='5005':WWN='0000000000000000':LUN='5235303020303030-3130353930203030'

[root@coco /]# scsi_info /dev/sdan

SCSI_ID='4,0,9,0':VENDOR='HP':MODEL='OPEN- 3':FW_REV='2114':WWN='03000000002018e9':LUN='5234353120303030-3330313033203030'

[root@coco /]# scsi_info /dev/sdao SCSI_ID='4,0,9,1':VENDOR='HP':MODEL='OPEN-

3':FW_REV='2114':WWN='0b00000000600000':LUN='5234353120303030-3330313033203030'

Installing PSP 7.91/92 causes fibreutils to downgrade. Reinstall fibreutils rpm from the downloaded kit.

Example:

#rpm –fvh fibreutils.<version>.linux.<arch>.rpm

When an EVA4400 with embedded switch is configured in a heterogeneous SAN, HP recommends that you use a text editor to edit the HBA configuration file etc/modprobe.conf.

options lpfcmpl mpl_hbeat_tmo_busy=0

Save the file, and then run the make_initrd script.

# /opt/hp/hp-lpfc/make_initrd

Reboot your server with the correct initrd.

Dynamic LUN addition and removal are supported. However, the ability to dynamically add a new LUN (or a LUN that has been previously removed) using the LUN number of a previously removed LUN is not supported. Dynamic target addition, which is defined as adding a new Fibre Channel target (such as adding a new storage array) to a SAN, is also not supported. The ability to present the new target to a Fibre Channel HBA, and then prompt the operating system to do an online scan (such as using the hp_rescan utility that comes with fibreutils) is not supported with the Emulex failover driver (MultiPulse). If you add a new Fibre Channel target to a host server, you must reboot that server.

This section describes information about using Windows and CNAs/HBAs.

Configuring Virtual Fibre Channel in Windows 2012 Hyper-V

When configuring Virtual Fibre Channel in Windows 2012 Hyper-V, all ports on the Converged Network Adapter must have NPIV enabled.

The 64 Bit DMA addressing feature is not supported in Emulex Windows FC/FCoE drivers at this time.

If the Windows operating system crashes on a Gen8 server, a memory.dmp file might not get written to disk due to a Windows driver issue.

Before you build a Windows 2003 SP2 operating system in a boot from SAN environment, you must install one of the following drivers:

  • For 64 bit systems, install 233008_BFS_x64_FCoE, available at:

  • For 32 bit systems, install 233008_BFS_x32_FCoE, available at:

After the operating system is built, install the Microsoft STORport storage driver available at http://support.microsoft.com/?id=932755, and then update to the latest driver supported by HP.

Systems running Windows Server 2008/Windows Server 2008 Service Pack 2 require KB hotfix 976748 to be installed before installing Microsoft Device Specific Module (MS DSM) as a multipath solution. For more information, see the Microsoft Support website:

HP EVA MPIO DSM 4.00.00 prevents BFS on systems running Windows 2003 if there are three or more paths enabled.

Windows driver fails to log back into the Cisco Nexus 5000 switch after switch reboot.

Emulex Lpe12000 Drivers License

On Windows 2003 and Windows 2008, the link is not re-established when a Cisco Nexus 5000 switch is rebooted. The workaround is to use the Nexus Shutdown and No Shutdown CLI commands to bring the port back online.

STORport miniport driver installation restrictions

If you are upgrading to the STORport miniport driver, consider the following:

  • The STORport miniport driver is supported on Windows 2003 SP1 and later.

  • Microsoft hotfix KB932755 must be installed before installing Multipath software.

  • If you are running Secure Path for Windows, you must upgrade to Secure Path 4.0c SP2 or later for Windows. STORport is not supported with earlier versions of Secure Path.

Integrity servers running WS2003 support Windows STORport driver 2.10x1 or earlier.

Emulex 2-Gb HBAs and mezzanine cards are not supported with WS2008 R2.

The following Smart Component issues may be observed during driver installation:

  • When using the Smart Component to install drivers, if the following message appears during reboot, ignore it and continue with the reboot procedure. No known issues have been observed in connection with the display of this message.

    The application failed to initialize because the windows station is shutting down.

  • Downgrading to STORport driver Version 2.0 or later does not work when initiated via the Smart Component. To downgrade an HP-branded Emulex HBA:

    1. Run the Smart Component containing the desired driver and extract the contents to a folder.

    2. Run the STORport driver installer from the extracted folder using the default values. For example:

      storportminiportcorekit_2-01a4

      This removes the current driver before downgrading to the specified driver version.

  • When using the Smart Component to install drivers, the following message may appear during reboot:

    There was a problem installing this hardware. This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)

    Uninstall and then reinstall your device.

    If the above message appears, click and continue with the reboot procedure. Do not reply to Microsoft. No known issues have been observed in connection with the display of this message.

  • In a direct connect environment, BFS fails after a second path is added to an EVA4000/6000/8000 running firmware 6.110.

  • BFS on c-Class blade servers fails on an active/passive MSA1000/1500 running firmware 5.20.

  • In BFS configurations where there are more than two Emulex HBAs in the same zone as the boot HBA, a crash-dump may not be generated due to a timeout condition when the boot HBA interacts with the non-boot HBAs. A workaround is to reconfigure the zoning such that the boot instance (for each path) is in its own zone separate from the other non-boot HBAs. In some cases, this also results in faster boot-up times.

  • When installing the OS to attached storage of the 403621-B21 LPe1105 mezzanine card in a VC environment through a Brocade switch, neither the target LUN nor the WWN for the boot controller are visible in the zone via the switch administrative tool. The workaround is to take note of the mezzanine card WWN when installing it into the system, or retrive it from the VC manager or EFI utility. Then manually enter the WWN into the desired zone on the switch when configuring the zone. Scan for targets and continue with normal installation steps to boot from the mezzanine card.

  • In a BFS configuration, the installed HBAs can display different names when viewed through the device manager. This is a cosmetic condition, not a functional issue.

  • When you select the Load Driver option during the operating system build of a Windows 2008 server in a BFS configuration, a multiple entry of the Emulex driver is displayed. If multiple types of HBAs are displayed, select the first entry before proceeding.

  • See FCoE BFS build requirement.

This section describes information about using VMware and CNAs/HBAs.

OCM GUI on ESX COS servers does not display all SAN storage arrays

The OCM GUI on ESX COS servers does not display all SAN storage arrays due to an issue with the communication path between the OCM GUI and ESX COS server.

Emulex Drivers For Windows

If this occurs, delete the affected server from the host inventory, and then add the server with CIM credentials (as a CIM server).

There is an issue when loading and running the elxcomcore rpm on ESX COS servers. If you attempt to add the ESX host using the CIM interface via the Windows OCM GUI, the Windows OCM is unable to connect to SFCB server.

To avoid this issue, install the Emulex VMware COM provider on the ESX COS (4.1) server, and then use the Windows OCM GUI CIM interface to add the server.

Downloading CIM Provider for ESXi 5.0 and ESXi 5.1

Use the following links to download CIM Provider.

Emulex Lpe12000 Driver Download

  • ESXi 5.1—http:www.emulex.com/downloads/emulex/vmware/vsphere-51/management.html

  • ESXi 5.0—http:www.emulex.com/downloads/emulex/vmware/vsphere-50/management.html

HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.

February 2013