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 Configuration Methods for FC Driver Parameters
- 3.2.2 Emulex ExpressLane Support
- 3.2.3 FC-SP-2 Authentication (DH-CHAP) Support
- 3.2.4 Trunking Support
- 3.2.5 Dynamically Adding LUNs
- 3.2.6 Dynamically Adding Targets
- 3.2.7 FC Driver Module Parameters
- 3.2.8 Creating an FC Remote Boot Disk
- 3.2.9 Managing Devices through the CIM Interface
- 3.2.10 Installing the Emulex CIM Provider
- 3.2.11 Creating, Deleting, and Displaying vPorts
- 3.2.12 Configuring VVols
- 3.2.13 Adjusting the LUN Queue Depth
- 3.3 Configuring NVMe over FC on a NetApp Target
- 3.4 Configuring NVMe over FC on an Initiator System
- Chapter 4: Troubleshooting the FC Driver
- Chapter 5: Troubleshooting the NVMe Driver
- 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: NPIV Configuration
- Appendix F: License Notices
Broadcom DRVVM-UG128-100
90
Emulex Drivers for VMware ESXi User Guide
5.2 Using VMware Commands
This section provides information about VMware commands that you can use in troubleshooting NVMe issues.
5.2.1 Checking the Status of an NVMe Controller
To check the status of an NVMe controller, perform the following steps:
1. If necessary, determine the mapping between an NVMe namespace and an NVMe controller by typing the following
command:
esxcli nvme namespace list
Information similar to the following is displayed:
You can obtain the NVMe controller number for the specific namespace from the displayed information.
NOTE: If the desired namespace is not listed, verify that the controller is connected (see the next step), the target is
connected (see Section 5.2.2, Verifying that NVMe Target Ports Are Discovered), and NVMe is configured properly
(Section 5.2.3, Listing NVMe Adapters on an ESXi Host).
A newly added NVMe controller is not visible.
Stale entries cannot be removed by a rescan.
Perform an initiator port link reset. For example, you can issue a LIP to an initiator
port by typing the following command:
/usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -i <vmhba>/
Emulex -k adapter -s lip
where <vmhba> is the HBA number.
Name Controller Number Namespace ID Block Size Capacity in MB
--------------------------------------- ------------------ -------------- ---------- -------------
uuid.cfb11df2e43a49779293f41319de4fb0 259 1 512 5120
uuid.cfb11df2e43a49779293f41319de4fb1 259 2 512 5120
uuid.cfb11df2e43a49779293f41319de4fb2 259 3 512 5120
uuid.cfb11df2e43a49779293f41319de4fb3 259 4 512 5120
uuid.cfb11df2e43a49779293f41319de4fb4 259 5 512 5120
uuid.cfb11df2e43a49779293f41319de4fb5 259 6 512 5120
uuid.cfb11df2e43a49779293f41319de4fb6 259 7 512 5120
uuid.cfb11df2e43a49779293f41319de4fb7 261 1 512 5120
uuid.cfb11df2e43a49779293f41319de4fb8 259 8 512 102400
uuid.cfb11df2e43a49779293f41319de4fb9 261 2 512 5120
uuid.cfb11df2e43a49779293f41319de4fba 261 3 512 5120
uuid.cfb11df2e43a49779293f41319de4fdb 259 9 512 5120
Table 9: Troubleshooting the NVMe Driver (Continued)
Situation Resolution