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
30
Emulex Drivers for VMware ESXi User Guide
3.2.13 Adjusting the LUN Queue Depth
Inadequate queue depth is one of the reasons for low performance. If you are using VVols and you experience low
performance, you might want to adjust the queue depth.
To change the LUN queue depth, perform the following steps:
1. Find the LUN queue depth by typing the following command:
/usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -i vmhba5/Emulex -k param -g | grep lun-queue-depth
Information similar to the following is displayed :
lun-queue-depth 1 fe 1e 1f Max number of FCP commands we can queue to a specific LUN
where 1f is the queue depth in hexadecimal. Equivalent decimal value is 31.
2. Change the existing queue depth by typing the following command:
/usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -i vmhba5/Emulex -k param -s "lun-queue-depth 0xfe"
3. Verify if the queue depth has changed by typing the following command:
/usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -i vmhba5/Emulex -k param -g | grep lun-queue-depth
Information similar to the following is displayed :
lun-queue-depth 1 fe 1e fe Max number of FCP commands we can queue to a specific LUN
where fe is the new queue depth in hexadecimal. Equivalent decimal value is 254.
4. Get a list of existing LUNs by typing the following command:
esxcli storage core device list
5. Change the number of outstanding I/Os for each LUN by typing the following command:
esxcli storage core device set -d <device name> -m 250 -O 250
6. Verify if the number of outstanding I/Os has changed for each specific LUN by typing the following command:
esxcli storage core device list -d <device name>
The sample output would look like the following:
Device Max Queue Depth: 250
No of outstanding IOs with competing worlds: 250
3.3 Configuring NVMe over FC on a NetApp Target
This section describes how to configure NVMe over FC on a NetApp target. For instructions on configuring NVMe over FC
on other targets, contact the target vendor.
The following variables are used in the commands provided in this section:
<vserver_name> is the name of the virtual server.
<lif1_name> is the name of LIF 1.
<node_name> is name of the LIF home node.
<home_port> is the home port of the LIF.
<volume_name> is the name you want to assign to the volume.
<aggregate_name> is an aggregate identified in the Aggregate column.
<aggregate_size> is the size of the aggregate.
<namespace_path> is the path of the namespace.
<namespace_size> is the namespace size. You can specify the size in bytes, KB, MB, GB, TB, or PB. For example, a
4-GB namespace can be indicated as 4GB.
<subsystem_name> is the name of the subsystem.
<host_nqn> is the NQN information that identifies the host.