Emulex® Drivers for VMware ESXi for LightPulse® Adapters Release Notes
Versions: ESXi 6.0 FC driver: 12.0.193.14
Systems: ESXi 6.0, 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

Bug Fixed


1.	An unrecoverable operating system fault no longer occurs during VM migration to another ESXi host. 
2.	An unrecoverable operating system fault no longer occurs during driver unload or reboot. 

Known Issues
All Versions, Known Issues

1.	Known issues related to software migration.

Beginning with software release 11.2, LightPulse® adapters and OneConnect® adapters have independent software kits. Before updating earlier drivers and applications to the software in release 12.0, refer to the Emulex Software Kit Migration User Guide for special instructions and considerations for using the 11.2 and later software kits for LightPulse and OneConnect adapters.

2.	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 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.

3.	Concurrent firmware upgrades performed on the same ESXi host might not be fully copied. 
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 might 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 below.
Operating System and Support for LPe31000-Series and LPe32000-Series Adapters:
ESXi 6.0 No; use IOVP
ESXi 6.5 Yes

5. When the Priority Tagging feature is used in an ESX environment with ESX mobility (vMotion),
the Priority Tagging strings may not be available from the operating system on the backup
server (the server to which vMotion moved) for 10–20 minutes. During this time, the
Priority Tagging strings are not available for registration on the fabric switch. 

Workaround
After the vMotion action, wait until the operating system settles and the Priority Tagging strings
are available.

6.	With VMID enabled, warning messages are generated even if no issue is present. 

Workaround

No workaround is available for the currently released ESXi versions. However, VMware is planning the following new operating system releases, which might address this issue. (Check with VMware to be sure this issue was addressed before upgrading the operating system.)
–  ESXi 6.0 P06/U3c (and Emulex RT 11.4 driver)

–  ESXi 6.5 U1 (and Emulex RT 11.4 driver)

–  ESXi 6.7 (including the inbox driver)

Technical Tips

Technical Tips
1. ESXi servers can appear to have the same Priority Tagging Application ID. The Priority Tagging is the
combination of the Application ID appended to the end of the N_Port ID, which provides
uniqueness within the fabric.

2. To see Priority Tagging information on all VMs in a multipathing configuration, set the path policy
to Round Robin.

3. 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.

4. Install an offline bundle locally on an ESXi server using the esxcli command.
Install an offline bundle on a VMware ESXi 6.0 server locally using the esxcli
command.
[root@testmachine ~]# esxcli software vib install --maintenance-mode -d
<offline-bundle.zip>
Where <offline-bundle.zip> is the file name of the offline bundle to be installed.

5. For ESXi hosts, the Emulex OneCapture™ utility should be used to retrieve dumps instead
of the Emulex OneCommand® Manager application remote dump. 
For more information on the OneCapture utility, refer to the Emulex OneCapture for LightPulse Adapters User Guide.