Users Guide
Table Of Contents
- Table of Contents
- Chapter 1: Introduction
- Chapter 2: Installation
- Chapter 3: Configuration
- 3.1 ESXi Command Line Tool Transition
- 3.2 FC Driver Configuration
- 3.2.1 FC Driver Parameters Configuration Methods
- 3.2.2 FC-SP-2 Authentication (DHCHAP) Support
- 3.2.3 Trunking Support
- 3.2.4 Dynamically Adding LUNs
- 3.2.5 Dynamically Adding Targets
- 3.2.6 FC Driver Configuration Parameters
- 3.2.7 Creating an FC Remote Boot Disk
- 3.2.8 Managing Devices through the CIM Interface
- 3.2.9 Installing the Emulex CIM Provider
- 3.2.10 Creating, Deleting, and Displaying vPorts
- 3.2.11 Configuring VVols in ESXi 6.5 and 6.7
- Chapter 4: Troubleshooting
- Appendix A: esxcli Management Tool
- Appendix B: lpfc Driver BlockGuard Functionality
- Appendix C: Using the VMID Feature on a Brocade Switch
- Appendix D: Using the VMID Feature on a Cisco Switch
- Appendix E: License Notices
Broadcom DRVVM-LPe-UG124-100
26
Emulex Drivers for VMware ESXi User Guide
Instead of OneCommand Manager for Windows, use the OneCommand Manager for VMware CLI (elxvcpcmd) or the
esxcli elxmgmt utilities to manage HBAs installed on ESXi 6.7 Update 1.
3.2.8.2 Using the OneCommand Manager Application for VMware vCenter
The OneCommand Manager for VMware vCenter Server application uses the standard CIM interface to manage the
adapters and supports CIM-based device and adapter management. The OneCommand Manager for VMware vCenter
Server application also supports existing adapter management functionality based on its proprietary management stack and
the standard HBA API interface. To manage adapters (including updating the firmware) on an ESXi 6.5 or 6.7 host using the
OneCommand Manager for VMware vCenter Server application, you must install the out-of-box Emulex CIM Provider on the
host.
For more information on installing the OneCommand Manager for VMware vCenter Server application and enabling the CIM
Provider, refer to the Emulex OneCommand Manager for VMware vCenter User Guide.
NOTE:
For the ESXi 6.7 vSphere Web client, flex is not supported, so you must use the vSphere client, HTML.
Currently the vSphere client, HTML supports only limited functionality.
For LPe35000-series adapters only:
In some cases, a firmware update requires either a firmware reset or a basic PCIe reset, depending on the
features available in the new firmware. A firmware reset is performed automatically if it is needed, regardless
of the operating system. In some cases, a full reboot is required to activate new firmware or to enable a new
feature. In that case, a message similar to one of the following messages appears after the firmware download
is complete:
Download successfully completed. Please reboot the system to activate new
firmware.
Download completed. Some features require an optional reboot. Refer to the
Adapter's Firmware and Boot Code Release Notes for details.
For a list of features that require a reboot to be enabled, refer to the Emulex LPe35000-Series HBA Firmware
and Boot Code Release Notes.
3.2.9 Installing the Emulex CIM Provider
Refer to the Emulex CIM Provider Installation Guide for instructions on installing the Emulex CIM Provider.
3.2.10 Creating, Deleting, and Displaying vPorts
The Emulex driver for VMware supports NPIV by default. ESXi provides the only management API for creating and deleting
a vPort and creating an NPIV-enabled VM. vPorts in the driver discover the fabric just like physical ports do, and are subject
to the same SAN delays. As the number of vPorts increases, the amount of time it takes to complete remote port discovery
increases because the vPorts are created sequentially and each vPort executes discovery synchronously. If your
NPIV-enabled virtual machines power-on automatically, powering on could take longer than usual. This behavior is normal
for NPIV virtual machines.