Virtual Resource Monitoring with ESXTOP

Virtual Resource Monitoring : The resxtop and esxtop command-line utilities provide a detailed look at how ESX/ESXi uses resources in real time. The fundamental difference between resxtop and esxtop is that you can use resxtop remotely (or locally), whereas esxtop can be started only through the service console of a local ESX host. Sometimes we need a quick set of statistics to see what is going on inside a vSphere host. Its same like Windows task manager.
We will discuss here about   few option in ESXTOP such as,   c: CPU,  i:interrupt,  m: memory, n:network, d: disk adapter, u: disk device, v:disk VM and p: power mgmt.
1. Monitoring CPU Usage:  When you run ESXTOP, by default the CPU view. If you are having performance problems with a VM and you want to see whether it’s due to the pCPU resources that have not been made available to the VM, you can check %RDY.
Other useful statistics include (host or VM-based statistics) the following:
• CPU load average: This gives the average utilization of all pCPUs in the host. A reading of 1.0 in the host means you are fully utilized, 0.5 means 50 percent utilized, 0.02 means two percent utilized, and so on.
• PCPU USED (%): This is the percent of all CPUs used by the host.
• %RUN: This is the amount of vCPUs utilized by the VM. This setting takes into account all vCPUs that are assigned. So, a value of 100 percent with one vCPU means that the vCPU is fully utilized. A value of 150 percent for a VM with two vCPUs means that it is roughly 75 percent utilized if you are looking within the guest OS (VM).
• %WAIT: This refers to how long the VM is waiting for other processes managed by ESXi to complete, such as I/O (VM).
To get more column that is not visible by default, perform the following actions during any resource monitoring:
1. Hit the “F” key on your keyboard.
2. Hit the “J” key on your keyboard to select MCTL.
3. Hit Esc and you will be returned to the ESXTOP statistics view with the
2.  Monitoring memory usage: There are sevral way to monitor memory. When you run ESXTOP, by default the CPU view. To switch to memory statistics, just press “M” on your keyboard and the view will change.You have probably noticed there are three values of 0.00, 0.00, and 0.00 returned in the preceding screenshot. These are the averages over a 1, 5, and 15 minute window.
The other statistics that you should make note of are as follows:
• PSHARE: This is a count of the number of shared pages and memory saving due to TPS.
• SWAP: This is the total amount of memory being swapped to the disk. This will most likely cause noticeable performance problems and should relate to a high MEM overcommit avg. Consider adding more memory or reducing the number of VMs on the host if this is consistently high.
• MEMCTL: This shows how much memory has been reclaimed by the balloon driver. A consistently high value here could lead to future disk swapping; however, this is a valid memory overcommitment management feature. You should also consider monitoring your individual VM OS for swapping if this value is high, to ensure VM performance is optimal.
In deep: Memory screen (m)
PMEB(MB) – Machine memory statistics.
Total – you knew it, total.
COS – Amount allocated to the service console.
VMK – Machine memory being used by the ESX(i) VMkernel.
Other – Everything else.
Free – Machine memory free
VMKMEM(MB) – Statistics for VMkernel in MB.
Managed – Total amount.
Min free – Minimum amount of machine memory VMKernel aims to keep free.
RSVD – Reserved by resource pools.
USVD – Total unreserved.
State – Values are high, soft, hard, low. (Pressure states)
COSMEM(MB) – Statistics as reported by the service console.
Free – Amount of idle memory.
Swap_t – Total swap configured.
Swap_f – Swap free.
r/s is – Rate at which memory is swapped in from disk.
w/s – Rate at which memory is swapped to disk.
NUMA(MB) – Only if running on a NUMA server.
PSHARE (MB) – Page sharing.
shared – Shared memory.
common – Across all worlds.
saving – Saved due to transparent page sharing.
curr – Current.
target – What the ESX(i) system expects the swap usage to be.
r/s – swapped from disk.
w/s – swapped to disk.
MEM CTL(MB) – Balloon statistics.
curr – Amount reclaimed.
target – Host attempt reclaims using the balloon driver, vmmemctl.
max – Maximum amount the host can reclaim using vmmemctl.
3. Monitoring storage : To access disk statistics, hit “v” on your keyboard while in ESXTOP and  this will be strictly VM-focused. The following counters are focused specifically on VMs:
• READS/s: This is the number of reads per second
• WRITES/s: This is the number of writes per second
Storage Panels selection :
de>d de>- disk adapter.
de>u de>- disk device. (also includes NFS if ESX(i) host is 4.0 Update 2 or later)
de>v de>- disk VM.
4. Monitoring storage adapter:  To view storage adapter-related statistics, press the “d” key on your keyboard while in ESXTOP. The statistics to monitor include the following:
• GAVG: This is a measure of the round trip latency seen by the VM.
• KAVG: This is the latency related to the ESXi kernel.
• DAVG: This is the latency seen at the device driver level. It includes the roundtrip time between the HBA and the storage.
This group of counters report latency values.  These are under the labels GAVG, KAVG and DAVG.  GAVG is the sum of DAVG and KAVG.
5. Monitoring network connectivity: you need to monitor networking select the “n” key.  Esxtop gives you great real-time.
You can see typical data transmission statistics; in the case of ESXTOP, this is tracked in MegaBits sent and received per second in the MbTX/s (transmitted/sent) and MbRX/s (received).
Two statistics that can immediately show whether a physical NIC is overcommitted or even connected to a faulty physical switch port or cable is %DRPTX and %DRPRX. On a physical NIC, you should expect these values to be at or near 0.00.
The statistics to monitor include the following:
PORT-ID – Port ID.
UPLINK – Uplink enabled.(Y or N)
UP – Guess what.
SPEED – Link in MB.
FDUPLX – Full duplex.
USED-BY – VM device port user.
DTYP – Virtual network device type. (H=hub, S=switch)
DNAME – Device name.
6.  To kill a running virtual machine process: Yes as we know that we can do this with the kill command: “kill -9 PID” …or you can do it in ESXTOP!
2. press “c” to open the CPU view
3. press “f” to add/remove fields
4. press “c” to add the field LWID Leader World Id (World Group ID)
5. press “k” to open the kill prompt:
6. Type in the LWID from the target virtual machine
8. wait 30 seconds and take care that the process is no longer listed

More info @

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s