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?
A.
esxcli system module parameters
B.
esxcli storage core device
C.
esxcli system module set
D.
esxcli storage core adapter
Explanation:
http://www.virten.net/2016/11/vmware-esxi-6-5-esxcli-command-reference/
A
https://kb.vmware.com/s/article/1267
5
0
A is correct.
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.troubleshooting.doc/GUID-9A0D1A30-D931-4914-8B06-8C13FB553EF3.html
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.storage.doc/GUID-6E59F461-F1BF-4A7A-BEB2-449B450D20CB.html
2
0
A is correct
https://kb.vmware.com/s/article/1267
1
0
its A
2
0
Correct A
https://kb.vmware.com/s/article/1267
3
0
Nope – it is B.
Search for the term “Depth” on this link
http://pubs.vmware.com/vsphere-6-5/topic/com.vmware.vcli.ref.doc/esxcli_storage.html
storage core device set –max-queue-depth | -m
5
5
Agree. It seems correct ans is B . Ref : http://pubs.vmware.com/vsphere-6-5/index.jsp?topic=%2Fcom.vmware.vcli.ref.doc%2Fesxcli_storage.html
http://www.virten.net/2016/11/vmware-esxi-6-5-esxcli-command-reference/
Ans A is incorrect because
KB article doesn’t discusses for vSphere 6.5 – https://kb.vmware.com/s/article/1267
0
3
A is correct (https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.troubleshooting.doc/GUID-9A0D1A30-D931-4914-8B06-8C13FB553EF3.html)
B is for SCSI queue depths and not HBA (as written on the website you posted)
1
0
https://blog.docbert.org/vmware-queue-depths-and-conflicting-worlds/
Yet another DOGDY question @ vmware…aaaargh … someone please shoot the examiners !! GET YOUR FACTS STRAIGHT VMWARE !!
and
http://it-stories.com/?p=191
1
0
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.troubleshooting.doc/GUID-9A0D1A30-D931-4914-8B06-8C13FB553EF3.html
OPTION C for 6.5 !!
Now this makes you wonder if the examiners have updated for 6.5 nor NOT 🙁 WTF!
0
0
clarity
this sets queue depth :
esxcli system module parameters set
this sets outstanding IO’s
esxcli storage core device set
some extra info https://sp.ts.fujitsu.com/dmsp/Publications/public/P3AM-3412-EN.pdf
1
0
So is it this :
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.troubleshooting.doc/GUID-9A0D1A30-D931-4914-8B06-8C13FB553EF3.html
or as per VMWAN here pointed out :
”
Nope – it is B.
Search for the term “Depth” on this link
http://pubs.vmware.com/vsphere-6-5/topic/com.vmware.vcli.ref.doc/esxcli_storage.html
storage core device set –max-queue-depth | -m
“
0
0
WTF indeed
0
0
http://it-stories.com/?p=191
https://www.settlersoman.com/what-is-storage-queue-depth-qd-and-why-is-it-so-important/
0
0
A https://www.codyhosterman.com/2017/02/understanding-vmware-esxi-queuing-and-the-flasharray/
1
0
It’s A
esxcli –server=server_name system module parameters set -p parameter=value -m module
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.troubleshooting.doc/GUID-9A0D1A30-D931-4914-8B06-8C13FB553EF3.html
1
0
It’s A
esxcli storage core device – changes SCSI State not FC
0
0