2V0-621 · Question #170
An administrator tries to run esxtop to troubleshoot CPU performance issues, but no output is displayed. How can the issue be resolved?
The correct answer is B. In esxtop, press f and place an asterisk next to each field that should be displayed.. When esxtop displays no output, it is because no fields are currently selected for display, and pressing 'f' allows the administrator to toggle fields on by marking them with an asterisk.
Question
An administrator tries to run esxtop to troubleshoot CPU performance issues, but no output is displayed. How can the issue be resolved?
Options
- Aesxtop is deprecated in vSphere 6.x, resxtop must be used to produce the desired output.
- BIn esxtop, press f and place an asterisk next to each field that should be displayed.
- Csudo should be run in front of esxtop to give the administrator the proper permissions.
- DThe esxtop command must be run from the /proc directory to produce output.
How the community answered
(38 responses)- A3% (1)
- B87% (33)
- C8% (3)
- D3% (1)
Why each option
When esxtop displays no output, it is because no fields are currently selected for display, and pressing 'f' allows the administrator to toggle fields on by marking them with an asterisk.
esxtop is not deprecated in vSphere 6.x and remains the primary real-time performance monitoring tool accessible from the ESXi shell; resxtop is a remote equivalent, not a replacement.
The esxtop interface is fully customizable, and all display columns can be toggled off, resulting in a blank screen with no data rows. Pressing 'f' opens the field selector where an asterisk marks a field as visible, restoring output once at least one field is enabled.
ESXi does not use sudo because the shell operates as root by default, so privilege escalation is not the cause of missing output.
esxtop is a standalone binary that does not require execution from the /proc directory and will run from any working directory on the ESXi host.
Concept tested: esxtop field display configuration and customization
Source: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.monitoring.doc/GUID-A89D6B26-6064-4B12-95E6-8F0F7D1E8B5B.html
Topics
Community Discussion
No community discussion yet for this question.