2V0-622 · Question #382
The storage vendor recommends adjusting the Fibre Channel HBA queue depth to resolve a performance problem. Which esxcli namespace can a vSphere Administrator use to adjust the queue depth?
The correct answer is B. esxcli storage core device. The esxcli storage core device namespace provides subcommands to configure device-level queue depth settings for Fibre Channel storage devices in vSphere.
Question
The storage vendor recommends adjusting the Fibre Channel HBA queue depth to resolve a performance problem. Which esxcli namespace can a vSphere Administrator use to adjust the queue depth?
Options
- Aesxcli system module parameters
- Besxcli storage core device
- Cesxcli system module set
- Desxcli storage core adapter
How the community answered
(23 responses)- A9% (2)
- B83% (19)
- C4% (1)
- D4% (1)
Why each option
The esxcli storage core device namespace provides subcommands to configure device-level queue depth settings for Fibre Channel storage devices in vSphere.
The 'esxcli system module parameters' namespace is used to list existing kernel module parameters, not to set device-level storage queue depth values.
The 'esxcli storage core device set' command allows administrators to configure device queue depth parameters such as queue-full-threshold and queue-full-sample-size on a per-device basis. Storage vendors commonly direct administrators to tune these device-level settings to resolve I/O saturation and performance bottlenecks on FC targets. This namespace is the correct location for device queue depth adjustments in the esxcli hierarchy.
'esxcli system module set' is not a valid esxcli namespace and does not exist as a command for adjusting storage queue depth.
The 'esxcli storage core adapter' namespace manages adapter-level operations such as rescanning, and does not expose queue depth configuration for individual storage devices.
Concept tested: esxcli storage core device queue depth configuration
Source: https://kb.vmware.com/s/article/1027901
Topics
Community Discussion
No community discussion yet for this question.