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. 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: Some software requires a valid warranty, current Hewlett Packard. VMware vSphere 5.5 and vSphere 6.0 FC/FCoE Driver kit for HP Emulex CNAs, 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: 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. 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, and the Red Hat Deployment Guide, available at the Red Hat website. 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 scsiinfo 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 /# scsiinfo /dev/sdal SCSIID='4,0,8,0': VENDOR='HP':MODEL='OPEN- E':FWREV='5005':WWN='000000':LUN='330' root@coco /# scsiinfo /dev/sdam SCSIID='4,0,8,1':VENDOR='HP':MODEL='OPEN- E':FWREV='5005':WWN='000000':LUN='330' root@coco /# scsiinfo /dev/sdan SCSIID='4,0,9,0':VENDOR='HP':MODEL='OPEN- 3':FWREV='2114':WWN='2018e9':LUN='330' root@coco /# scsiinfo /dev/sdao SCSIID='4,0,9,1':VENDOR='HP':MODEL='OPEN- 3':FWREV='2114':WWN='0b0000':LUN='330'. 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.linux.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 mplhbeattmobusy=0 Save the file, and then run the makeinitrd script. # /opt/hp/hp-lpfc/makeinitrd 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 hprescan 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. 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. 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.
Run the Smart Component, containing the desired driver, to extract the contents to a folder. Run the STORport driver installer from the extracted folder using the default values. For example: storportminiportcorekit2-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 Finish. 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. 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. 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. 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.
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: 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.
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, and the Red Hat Deployment Guide, available at the Red Hat website. 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 scsiinfo 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 /# scsiinfo /dev/sdal SCSIID='4,0,8,0': VENDOR='HP':MODEL='OPEN- E':FWREV='5005':WWN='000000':LUN='330' root@coco /# scsiinfo /dev/sdam SCSIID='4,0,8,1':VENDOR='HP':MODEL='OPEN- E':FWREV='5005':WWN='000000':LUN='330' root@coco /# scsiinfo /dev/sdan SCSIID='4,0,9,0':VENDOR='HP':MODEL='OPEN- 3':FWREV='2114':WWN='2018e9':LUN='330' root@coco /# scsiinfo /dev/sdao SCSIID='4,0,9,1':VENDOR='HP':MODEL='OPEN- 3':FWREV='2114':WWN='0b0000':LUN='330'. 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.linux.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 mplhbeattmobusy=0 Save the file, and then run the makeinitrd script. # /opt/hp/hp-lpfc/makeinitrd 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 hprescan 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.
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. 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. Run the Smart Component, containing the desired driver, to extract the contents to a folder. Run the STORport driver installer from the extracted folder using the default values.
For example: storportminiportcorekit2-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 Finish.
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. 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.