ESXTOP Command overview...

For changing to the different views type:

m Memory i Interrupts v Disk VM
c CPU d Disk Adapter p Power states
n Network u Disk Device
f for add/remove fields
V show only virtual machine instances
2 highlight a row scrolling down
8 highlight a row scrolling up
spacebar: refresh screen
s 2: refresh screen every two seconds
vSphere 5.5 ESXTOP quick Overview for Troubleshooting
Memory Status:
high enough free memory available
soft < 4% free memory: Host reclaim memory by balloon driver
hard < 2% free memory: Host starts to swap, you will see performance troubles
low < 1% free memory: ESX stop the VMs to allocate more RAM
CACHEUSD: Memory (in MB) compressed by ESXi Host
ZIP/s: Values larger 0 indicate that the host is
actively compressing memory.
UNZIP/s: Values larger 0 indicate that the
host is accessing compressed memory.
Reason for this behaviour is memory
overcommitment.
1
1
Disk d Fields: A B G J
NUMA m (change to memory view) Fields: D G
MCTLSZ: Amount of guest physical memory (MB) the ESXi Host is
reclaiming by balloon driver. A reason for this is memory
overcommitment.
1
SWR/s, SWW/s: Rate at which the ESXi Host is writing to or reading from swapped memory. Possible
cause: memory overcommitment. 1
DAVG: Latency at the device driver level
Indicator for storage performance
troubles
>25
ABRTS/s: Commands aborted per second
If the storage system has not responded within 60 seconds VMs with an
Windows Operating System will issue an abort. 1
Resets/s: number of commands reset per second
1
KAVG: Latency caused by VMKernel
Possible cause: Queuing (wrong queue depth
parameter or wrong failover policy)
3
N%L: Percentage of VM Memory located at the local NUMA Node. If this
value is less than 80 Percent the VM will experience performance issues. <80
NMN: Numa Node where the VM is located
NRMEM: VM Memory (in MB)
located at remote Node
NLMEM: VM Memory (in MB) located at local Node
%USED: CPU Core cycles used by a VM. High values are an indicator
for VMs causing performance problems on ESXi Hosts.
%SWPWT: Counter showing how long a VM has to wait for swapped
pages read from disk. A reason for this could be memory
overcommitment. Pay attention if %SWPWT is >5!
5
%MLMTD: Counter showing percentage of time a ready to run vCPU
was not scheduled because of a CPU limit setting. Remove the limit for
better performance.
1
%CSTP: This value is interesting if you are using vSMP virtual
machines. It shows the percentage of time a ready to run VM has spent
in co-deschedule state.
If value is >3 decrease the number of vCPUs from the VM concerned.
3
%RDY: Percentage of time a VM was waiting to be scheduled.If you note values between
five and ten percent take care.
Possible reasons: too many vCPUs, too many vSMP VMs or a CPU limit setting (check
%MLMTD)
>10
Copyright 2012-2013 running-system.com | Designed By: Andi Lesslhumer | Version 1.1
CPU c Fields: D F
CPU load average for the last one, five and
15 minutes
Memory m Fields: B D J K Q
average memory overcommitment for the last
one, five and 15 minutes
SWCUR: Memory (in MB) that has been swapped by VMKernel.
Possible cause: memory overcommitment.
1
GAVG: GAVG = DAVG + KAVG
>25
%DRPTX, %DRPRX: Dropped Packages transmitted/Dropped Packages received.
Values larger 0 are a sign for high network utilization
1
Network n Fields: A B C D E F K L
Used-by/Team-PNIC: provide information what
physical NIC a VM is actually using.
%VMWAIT: percentage of time a VM was waiting for some VMkernel activity to complete (such as I/O) before it
can continue. Includes %SWPWT and "blocked", but not IDLE Time (as %WAIT does).
Possible cause: Storage performance issue | latency to a device in the VM configuration eg. USB device, serial
pass-through device or parallel pass-through device
100
%SYS: Percentage of time spent by system to process interrupts
and to perform other system activities on behalf of the world.
Possible cause: maybe caused by high I/O VM
>20
running-system.com
@lessi001