Emulex® Drivers for VMware ESXi for LightPulse® Adapters Release Notes
Versions: ESXi 5.5 FC driver: 11.2.156.14
Systems: ESXi 5.5 and updates

Purpose and Contact Information
These release notes describe the new features, resolved issues, known issues, and technical tips associated with these Emulex® drivers for VMware releases.
For the latest product documentation, go to www.broadcom.com. If you have questions or require additional information, contact an authorized Broadcom® technical support representative at ecd-tech.support@broadcom.com or request assistance online at https://oemsupportportal.emulex.com/web2tech/ecd.html


New Features
1. Beginning with software release 11.2, LightPulse® adapters and OneConnect® adapters have independent software kits. Special instructions and considerations for using the driver kits for LightPulse and OneConnect adapters are provided in the Emulex SoftwareKit Migration User Guide. Refer to that document before updating existing drivers and applications to the drivers and applications in release 11.2.Documnets are available at https://www.broadcom.com/support/download-search 
2 VMware ESXi 5.5  operating system does not support new features in this release: VMware ESXi 5.5 
  
Resolved Issues
1. An issue in which the MBrd value in iostats displayed 0 when traffic flow was available has been resolved.  (BZ 195979)
2. A port on which setportEnabled was set to 0 is no longer reported as operational.(BZ 193747)

Known Issues
All Versions, Known Issues
1. The adapter model name and description do not match the vendor brand name field.
The VMware vSphere client only shows adapter family model names with a single port. For example, it shows the LightPulse LPe32002 host bus adapter (HBA) as the Emulex LightPulse LPe32000 PCIe Fibre Channel Adapter. This issue occurs with the native tool lspci as well. The vSphere client gets the adapter model name and description from the XML package files installed with the operating system or with an out-of-box kit rather than from the adapter vital product data (VPD). 
Other native tools work in a similar manner.

Workaround
To show all available KV instances, use the following command: /usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -d
For storage adapters, look for vmhbaX/Emulex.

2. Issues exist with boot from SAN support on Emulex LPe12000-series adapters. 
Boot from SAN can experience issues on Emulex LPe12000-series adapters. Issues include not finding the boot LUN or not successfully booting from the boot LUN.

Workaround
Boot from SAN support on Emulex LPe12000-series adapters requires the Broadcom Emulex Universal Boot Code 5.12a2 or later and firmware version 2.01a4 or later.


3. Concurrent firmware upgrades performed on the same ESXi host might not be fully copied. (BZ_149917)
If a firmware upgrade is attempted using the HTTP protocol, the firmware file is copied to the /filesystem of the ESXi system. This file is deleted after the firmware upgrade is complete. Therefore, if concurrent firmware upgrades are performed on the same ESXi host, due to space constraints, the firmware file may not be copied fully, and the firmware upgrades might fail with an error.
Workaround
None.


4. Certain inbox drivers do not support LPe31000-series and LPe32000-series adapters, as described in the following below.
Operating System Support for LPe31000-Series and LPe32000-Series Adapters
ESXi 5.5 No; use IOVP
Follow the guidelines as above.

5. On an LPe12002 system, loop-only topology does not work with an 8 Gb Brocade switch.
Workaround
None.


ESXi 5.5 Known Issues
1. Disabling MultiQueue (MQ) might seriously impact performance of the LPFC driver.(BZ_147852)
Workaround
Do not disable MQ.

2. VPort NDLP state does not transition to unused after receiving an unsolicited port login (PLOGI) from an initiator.
Workaround
None.

3. An errant NULL print string write to console log might occur. 
Workaround
None.

4. A system hang might occur on servers with more than eight CPU sockets. 
Workaround
None. The driver and adapter must be installed on servers with eight CPU sockets or less. 


5. Direct-attached configurations in a point-to-point topology do not connect. (No BZ)
Workaround
Use the driver default topology (loop).


6. With N_Port ID Virtualization (NPIV) enabled, the server hangs during reboot after executing bus, lun, and target reset on vPorts. (BZ 187999)
Workaround
Shut down all guests, power off all VMs, and then reboot. This action allows the reboot to work cleanly.

7. I/O does not resume on vports after the vport is disabled and then re-enabled. (BZ185932)
When virtual ports on a single physical port are set to round robin, and they are disabled and re-enabled one at a time, I/O does not resume properly on the re-enabled vports. I/O continues on the physical port.
Workaround
None.


Technical Tips
1. A max_multiq parameter has been added to the ESXi 5.5 native mode FC drivers. This parameter determines how many IO channel (MSI-X vector/EQ/CQ tuples) are used in parallel to Fibre Channel Protocol (FCP) 10. The disable_mq and
fcp_io_channels driver parameters have been removed from the ESXi 5.5 and ESXi 6.0 native mode FC drivers. For more information, refer to the Emulex Drivers for VMware ESXi for LightPulse Adapters User Guide. (BZ_176576)

2. The server must be in ESXi maintenance mode to safely change the firmware in flash memory.
For operations, such as firmware download, bring the server into ESXi maintenance mode prior to flashing the firmware.

3. For ESXi hosts, the Emulex OneCapture utility should be used to retrieve dumps instead of the Emulex OneCommand Manager application remote dump. (BZ_173273) For more information on the OneCapture utility, refer to the Emulex OneCapture for LightPulse Adapters User Guide at https://www.broadcom.com/support/download-search .

