<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="DRVVM-RN1261-100.css" type="text/css" charset="UTF-8"?>
<ROOT>
<TITLE> </TITLE><Heading-1>
<A ID="pgfId-324686"></A>
Emulex Drivers for VMware ESXi
Release	ESXi 6.7 12.6.182.2
<A ID="pgfId-324686"></A>
Purpose and Contact Information</Heading-1>
<AP-Body>
<A ID="pgfId-351672"></A>
These release notes describe the new feature components, supported adapters, change history, resolved issues, known issues/limitations with the current release, technical tips, supported upgrade versions, and related KB-articles associated with the EmulexB. drivers for VMware releases. </AP-Body>
<AP-Body>
<A ID="pgfId-352189"></A>
For the latest product documentation, go to <Website>
<A href="https://www.broadcom.com" xml:link="simple" show="replace" actuate="user" CLASS="URL">www.broadcom.com</A></Website>
. If you have questions or require additional information, contact an authorized Broadcom<Superscript>
B.</Superscript>
 Technical Support representative at <Website>
<A href="mailto:ecd-tech.support@broadcom.com" xml:link="simple" show="replace" actuate="user" CLASS="URL">ecd-tech.support@broadcom.com</A></Website>
.</AP-Body>
<Heading-1>
<A ID="pgfId-351639"></A>
New Feature Components </Heading-1>
<StepList>
<Step>
<A ID="pgfId-380876"></A>
Adds support for loop topology on LPe31000-series and LPe32000-series adapters. </Step>
<Step>
<A ID="pgfId-380892"></A>
The format of <CodeFont>
esxcli elxmgmt</CodeFont>
 commands has been modified to comply with VMware CLI formatting. For the new format of commands and newly added namespaces, refer to the Emulex Drivers for VMware ESXi User Guide Release 12.6. Deprecated commands are no longer supported. </Step>
<Note>
<A ID="pgfId-381401"></A>
The Emulex OneCommand<Superscript>
B.</Superscript>
 Manager application has been renamed as the Emulex HBA Manager application.</Note>
</StepList>
<Heading-1>
<A ID="pgfId-382285"></A>
Supported Adapters</Heading-1>
<Body>
<A ID="pgfId-382286"></A>
The following HBAs are supported by the ESXi 6.7 FC drivers:</Body>
<BulletList>
<Bullet>
<A ID="pgfId-382287"></A>
LPe12000-series adapters</Bullet>
<Bullet>
<A ID="pgfId-382288"></A>
LPe16000-series adapters</Bullet>
<Bullet>
<A ID="pgfId-382289"></A>
LPe32000-series adapters</Bullet>
<Bullet>
<A ID="pgfId-382281"></A>
LPe35000-series adapters</Bullet>
</BulletList>
<Heading-1>
<A ID="pgfId-382324"></A>
Change History</Heading-1>
<Body>
<A ID="pgfId-382350"></A>
There are no changes in this release.</Body>
<Body>
<A ID="pgfId-382326"></A>
</Body>
<Body>
<A ID="pgfId-382328"></A>
</Body>
<Body>
<A ID="pgfId-382330"></A>
</Body>
<Heading-1>
<A ID="pgfId-381654"></A>
Resolved Issues</Heading-1>
<Body>
<A ID="pgfId-381797"></A>
On Brocade switches that use LPe35000-series adapters with two-lane or four-lane trunking enabled, the issue of port speed in FDIM Port attributes being incorrectly displayed is fixed. </Body>
<Heading-1>
<A ID="pgfId-370724"></A>
Known Issues/Limitations with the Current Release</Heading-1>
<Step-First-List>
<Step-First->
<A ID="pgfId-351693"></A>
Known issue related to software migration.</Step-First->
</Step-First-List>
<Indent>
<A ID="pgfId-351694"></A>
Beginning with software release 11.2, FC HBAs and OneConnectB. adapters have independent software kits. Before updating earlier drivers and applications to the software in release 12.6.1, refer to the <Emphasis>
Emulex Software Kit Migration User Guide</Emphasis>
 for special instructions and considerations for using the 11.2 and later software kits for FC HBAs and OneConnect adapters.</Indent>
<StepList>
<Step>
<A ID="pgfId-351695"></A>
The adapter model name and description do not match the vendor brand name field. </Step>
</StepList>
<Indent>
<A ID="pgfId-357088"></A>
The VMware vSphere client shows only the adapter family model names with a single port. </Indent>
<Indent>
<A ID="pgfId-357089"></A>
For example:</Indent>
<Indent>
<A ID="pgfId-357090"></A>
An LPe31000-series and LPe31000-series adapter is shown as the <CodeFont>
Emulex LightPulse LPe32000 PCIe Fibre Channel Adapter</CodeFont>
.</Indent>
<Indent>
<A ID="pgfId-357091"></A>
An LPe35000-series adapter is shown as the <CodeFont>
Emulex LightPulse LPe36000 Fibre Channel Adapter</CodeFont>
.</Indent>
<Indent>
<A ID="pgfId-357092"></A>
This issue occurs with the <CodeFont>
lspci</CodeFont>
 native tool 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.</Indent>
<Indent>
<A ID="pgfId-357093"></A>
<Bold>
Workaround</Bold>
</Indent>
<Indent>
<A ID="pgfId-357094"></A>
To show all available Key Value (KV) instances, use the following command:</Indent>
<Indent>
<A ID="pgfId-357095"></A>
<CodeFont>
/usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -d</CodeFont>
</Indent>
<Indent>
<A ID="pgfId-357096"></A>
For storage adapters, look for <CodeFont>
vmhbaX/Emulex</CodeFont>
.</Indent>
<StepList>
<Step>
<A ID="pgfId-356944"></A>
Some inbox drivers do not support LPe35000-series adapters, as described in the following table.</Step>
</StepList>
<Anchor>
<A ID="pgfId-356963"></A>
</Anchor>
<TABLE>
<CAPTION>
<Caption-Table>
<A ID="pgfId-356948"></A>
<A ID="27548"></A>
Operating System and Support for LPe35000-Series Adapters</Caption-Table>
</CAPTION>
<ROW>
<TH ROWSPAN="1" COLSPAN="1">
<Table-Head>
<A ID="pgfId-356952"></A>
Operating System</Table-Head>
</TH>
<TH ROWSPAN="1" COLSPAN="1">
<Table-Head>
<A ID="pgfId-356954"></A>
Support for LPe35000-Series Adapters</Table-Head>
</TH>
</ROW>
<ROW>
<CELL ROWSPAN="1" COLSPAN="1">
<Table-Text>
<A ID="pgfId-356960"></A>
ESXi 6.7</Table-Text>
</CELL>
<CELL ROWSPAN="1" COLSPAN="1">
<Table-Text>
<A ID="pgfId-356962"></A>
No; use the latest IOVP certified driver.</Table-Text>
</CELL>
</ROW>
</TABLE>
<Indent>
<A ID="pgfId-351849"></A>
<Bold>
Workaround</Bold>
</Indent>
<Indent>
<A ID="pgfId-351717"></A>
Follow the guidelines in <A href="DRVVM-RN1261-100.xml#id(27548)" xml:link="simple" show="replace" actuate="user" CLASS="XRef"><Cross-Ref>
Table 1</Cross-Ref>
</A>.</Indent>
<StepList>
<Step>
<A ID="pgfId-366695"></A>
Revision A of the FOIT AFCT-57F3TMZ-ELX (16GFC longwave optic transceiver) does not support D_Port (also called ClearLink) for BrocadeB. switches and MDS Diagnostic for Cisco switches. </Step>
</StepList>
<Indent>
<A ID="pgfId-366696"></A>
<Bold>
Workaround</Bold>
</Indent>
<Indent>
<A ID="pgfId-366697"></A>
None.</Indent>
<StepList>
<Step>
<A ID="pgfId-366698"></A>
Neither Revision A nor Revision B of the FOIT AFCT-57F3TMZ-ELX (16GFC longwave optic transceiver) or AFCT-57G5MZ-ELX (32GFC longwave optic transceiver) supports D_Port for Brocade switches. </Step>
</StepList>
<Indent>
<A ID="pgfId-366699"></A>
<Bold>
Workaround</Bold>
</Indent>
<Indent>
<A ID="pgfId-366700"></A>
None.</Indent>
<StepList>
<Step>
<A ID="pgfId-359333"></A>
Boot from SAN is not supported if FC-SP-2 authentication (DHCHAP) is enabled.</Step>
</StepList>
<Indent>
<A ID="pgfId-365436"></A>
<Bold>
Workaround</Bold>
</Indent>
<Indent>
<A ID="pgfId-365437"></A>
None.</Indent>
<StepList>
<Step>
<A ID="pgfId-361432"></A>
Brocade switches that use Fabric Operating System (FOS) version 8.2.1B and earlier might encounter the following issues with DHCHAP authentication:</Step>
<BulletSub-dash->
<A ID="pgfId-361434"></A>
You might not be able to configure the secret pair between the switch and the HBA. When authentication is enabled on the switch, and authentication is disabled on the HBA, the switch disables the port, but it does not issue the expected status messages. </BulletSub-dash->
<BulletSub-dash->
<A ID="pgfId-361435"></A>
The Brocade switch authenticates the HBA port when authentication is disabled on the switch or when a frame is dropped.</BulletSub-dash->
</StepList>
<Indent>
<A ID="pgfId-365351"></A>
<Bold>
Workaround</Bold>
</Indent>
<Indent>
<A ID="pgfId-365352"></A>
None.</Indent>
<StepList>
<Step>
<A ID="pgfId-364701"></A>
The trunking speed is incorrectly displayed as 0 when you execute the <CodeFont>
esxcli storage san fc list</CodeFont>
 command.</Step>
</StepList>
<Indent>
<A ID="pgfId-364688"></A>
<Bold>
Workaround</Bold>
</Indent>
<Indent>
<A ID="pgfId-364723"></A>
To view the correct trunking speed, use any of the following options:</Indent>
<BulletSub-dash-List>
<BulletSub-dash->
<A ID="pgfId-364725"></A>
Execute the following <CodeFont>
keyval</CodeFont>
 command:</BulletSub-dash->
</BulletSub-dash-List>
<Code-Indent->
<A ID="pgfId-364830"></A>
/usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval  -i vmhba&lt;port instance&gt;/Emulex  -g -k port</Code-Indent->
<BulletSub-dash-List>
<BulletSub-dash->
<A ID="pgfId-364726"></A>
Execute the following <CodeFont>
esxcli elxmgmt</CodeFont>
 command:</BulletSub-dash->
</BulletSub-dash-List>
<Code-Indent->
<A ID="pgfId-364914"></A>
<CodeFont>
esxcli elxmgmt portattributes -w &lt;wwpn&gt;</CodeFont>
</Code-Indent->
<BulletSub-dash-List>
<BulletSub-dash->
<A ID="pgfId-364727"></A>
Execute the following <CodeFont>
hbacmd</CodeFont>
 CLI command:</BulletSub-dash->
</BulletSub-dash-List>
<Code-Indent->
<A ID="pgfId-364860"></A>
HbaCmd.exe h=&lt;ESXi Host IP&gt; m=cim portattributes &lt;wwpn&gt;</Code-Indent->
<BulletSub-dash-List>
<BulletSub-dash->
<A ID="pgfId-364689"></A>
Use the Emulex HBA Manager GUI. </BulletSub-dash->
<Step>
<A ID="pgfId-368207"></A>
Dependency errors might occur when you use the esxcli command to upgrade from release 12.4 elxfccli or elxmgmt VIB to release 12.6 or later elxfccli or elxmgmt VIB. </Step>
</BulletSub-dash-List>
<Indent>
<A ID="pgfId-368267"></A>
<Bold>
Workaround</Bold>
</Indent>
<Indent>
<A ID="pgfId-368211"></A>
Remove the existing release 12.4 VIB and install the release 12.6 or later VIB. </Indent>
<StepList>
<Step>
<A ID="pgfId-381235"></A>
Delay in processing ELS commands might be observed if <CodeFont>
enable_mds_diags</CodeFont>
 module parameter is enabled. </Step>
</StepList>
<Indent>
<A ID="pgfId-381236"></A>
<Bold>
Workaround</Bold>
</Indent>
<Indent>
<A ID="pgfId-381237"></A>
Disable <CodeFont>
enable_mds_diags</CodeFont>
. This parameter must be enabled only when attempting a Cisco MDS diagnostic test. </Indent>
<Heading-1>
<A ID="pgfId-379248"></A>
Technical Tips</Heading-1>
<Step-First-List>
<Step-First->
<A ID="pgfId-370190"></A>
When the Virtual Machine Identifier (VMID) feature is used in an ESXi environment with ESXi mobility (vMotion), the VMID strings might not be available from the operating system on the backup server (the server to which vMotion moved) for 10 to 20 minutes. During this time, the VMID strings are not available for registration on the fabric switch. </Step-First->
</Step-First-List>
<Indent>
<A ID="pgfId-370225"></A>
<Bold>
Workaround</Bold>
</Indent>
<Indent>
<A ID="pgfId-370182"></A>
After the vMotion action, wait until the operating system settles and the VMID strings are available.</Indent>
<StepList>
<Step>
<A ID="pgfId-351760"></A>
ESXi servers can appear to have the same VMID Application ID. The VMID is the combination of the Application ID appended to the end of the N_Port ID, which provides uniqueness within the fabric.</Step>
<Step>
<A ID="pgfId-351761"></A>
To view VMID information on all VMs in a multipathing configuration, set the path policy to <CodeFont>
Round Robin</CodeFont>
.</Step>
<Step>
<A ID="pgfId-351763"></A>
The server must be in ESXi maintenance mode to safely change the firmware in flash memory.</Step>
</StepList>
<Indent>
<A ID="pgfId-351764"></A>
For operations, such as firmware download, bring the server into ESXi maintenance mode prior to flashing the firmware.</Indent>
<StepList>
<Step>
<A ID="pgfId-351765"></A>
Install an offline bundle locally on an ESXi server using the <CodeFont>
esxcli</CodeFont>
 command.</Step>
</StepList>
<Indent>
<A ID="pgfId-351766"></A>
Install an offline bundle on a VMware ESXi server locally using the <CodeFont>
esxcli</CodeFont>
 command. </Indent>
<Code-Indent->
<A ID="pgfId-351767"></A>
<CodeFont>
[root@testmachine ~]# esxcli software vib install --maintenance-mode -d &lt;</CodeFont>
<Emphasis>
offline-bundle.zip</Emphasis>
<CodeFont>
&gt;</CodeFont>
</Code-Indent->
<Code-Indent->
<A ID="pgfId-351773"></A>
Where <CodeFont>
&lt;</CodeFont>
<Emphasis>
offline-bundle.zip</Emphasis>
<CodeFont>
&gt;</CodeFont>
 is the file name of the offline bundle to be installed.</Code-Indent->
<StepList>
<Step>
<A ID="pgfId-381698"></A>
Dynamic D_Port is enabled by default and cannot be simultaneously enabled with FA-PWWN or DHCHAP. </Step>
</StepList>
<Indent>
<A ID="pgfId-381699"></A>
<Bold>
Workaround</Bold>
</Indent>
<Indent>
<A ID="pgfId-381700"></A>
To enable FA-PWWN or DHCHAP, disable Dynamic D_Port first using the Emulex HBA Manager application. You can disable DHCHAP using the <CodeFont>
lpfc_enable_auth</CodeFont>
 parameter.</Indent>
<Heading-1>
<A ID="pgfId-382401"></A>
Supported Upgrade Versions</Heading-1>
<Body>
<A ID="pgfId-382418"></A>
There are no specific upgrade restrictions for moving from inbox to out-of-box.</Body>
<Heading-1>
<A ID="pgfId-382422"></A>
Related KB-Articles</Heading-1>
<AP-Body>
<A ID="pgfId-360220"></A>
There are no related KB-articles in this release.</AP-Body>
<AP-Body>
<A ID="pgfId-360228"></A>
</AP-Body>
</ROOT>
