Skip to main content

ESXTOP not displaying properly?

 

ESXTOP not displaying properly?


I’ve seen quite a few posts lately about ESXTOP not displaying properly. Long story short, esxtop does not display the interactive UI and displays the CSV output instead.

If your esxtop looks like this, then you need to change the terminal declaration to something like xterm. Notice here (red rectangle), how the terminal is set to xterm-256color.

xterm-256color

 

You can change the terminal declaration from the cli, but this is not persistent through sessions.

To do this simply type “TERM=xterm“.

To display the current terminal declaration type “echo $TERM”

termxterm

 

 

This will display esxtop interface properly.

esxtop

 

 

 

 

 

 

 

If you want this change to persist, just change your favorite terminal settings to xterm from its current setting. For example, I use my Mac’s terminal to ssh into my lab, the terminal is set to xterm-256color, which causes the display issue. So, I just opened the terminal preferences and changed the declaration to xterm. By default, putty identifies itself as xterm(1), so no need to change that. If putty is set to something else, then you can change the terminal-type string from the Connection>Data section.

term_declaration

 










Original post from greatwhitetec.com

Comments

Post a Comment

Popular posts from this blog

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.
Post a Comment
Read more

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...
Post a Comment
Read more

Recreating a VMFS-3 or VMFS-5 partition table in ESXi 5.x

For this kind of issues you need to engage VMware support on this, following any part of this article could lead to more complex situation if not ran by an expert.   Symptoms Datastore does not mount because of a lost or overwritten partition table.   Purpose When a VMFS partition is created in ESX 3.x or ESX 4.x, it has a Master Boot Record (MBR) partition map. The MBR is written to the first 512 B block (LBA0) and contains the information where the (VMFS) partition starts and ends. ESXi 5.0 introduced VMFS-5, which uses a GUID partition table (GPT) for new datastores. When a VMFS-3 partition is created in ESXi 5.x and is later updated to VMFS-5, the original partition map (MBR) is maintained. If the partition information of a VMFS datastore is deleted or overwritten (for example, by a Windows system with direct access to the same disks), it is impossible to determine if the partition map was GPT or MBR. The only time you can be sure that a GPT partition map was used is if th...
Post a Comment
Read more