| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Total_no_of_esx_servers |
Indicates the number of ESX servers that are currently managed by VC. |
Number |
Use the detailed diagnosis of this measure, if enabled, to know which ESX servers are being managed by VC.
|
| Added_esx_servers |
Indicates the number of ESX servers that were added to VC during this measurement period. |
Number |
Use the detailed diagnosis of this measure, if enabled, to know which ESX servers were recently added to VC. |
| Removed_esx_servers |
Indicates the number of ESX servers that were removed from VC during this measurement period. |
Number |
Use the detailed diagnosis of this measure, if enabled, to know which ESX servers were removed from VC. |
| Connected_esx_servers |
Indicates the number of ESX servers that are currently connected to VC. |
Number |
Use the detailed diagnosis of this measure, if enabled, to know which ESX servers are connected to VC. |
| Newly_Connected_esx_server |
Indicates the number of ESX servers that connected to VC during this measurement period. |
Number |
Use the detailed diagnosis of this measure, if enabled, to know which ESX servers recently connected to VC. |
| Disconnected_esx_servers |
Indicates the number of ESX servers that are currently disconnected from VC. |
Number |
Use the detailed diagnosis of this measure, if enabled, to know which ESX servers disconnected from VC. |
| Newly_disconnected_esx_servers |
Indicates the number of ESX servers that disconnected from VC during this measurement period. |
Number |
Use the detailed diagnosis of this measure, if enabled, to know which ESX servers recently disconnected from VC. |
| Notresponding_esx_servers |
Indicates the number of ESX servers that are currently not responding to VC. |
Number |
Ideally, the value of this measure should be low. A high value could indicate a problem in the network connection between the ESX server and VC.
Use the detailed diagnosis of this measure, if enabled, to know which ESX servers are not responding to VC.
|
| Newly_notresponding_esx_servers |
Indicates the number of ESX servers that have been marked as 'unresponsive' during this measurement period. |
Number |
Use the detailed diagnosis of this measure, if enabled, to know which ESX servers were marked as 'not responding' during this measurement period. |
| Total_no_of_vms |
Indicates the number of VMs that are currently executing on all ESX servers managed by this VC. |
Number |
Use the detailed diagnosis of this measure to view the names of the VMs, the names of the ESX hosts on which the VMs have been configured, and the IP address of the hosts. |
| Template_vms |
Indicates the total number of template VMs that currently exist on all ESX servers managed by VC. |
Number |
A template is a "golden" copy of a virtual machine (VM) organized by folders and managed with permissions. They are useful because they act as a protected version of a model VM which can be used to create new VMs. As a template is the original and perfect image of a particular VM, it cannot be powered on or run.
You can use the detailed diagnosis of this measure to view the names and IP addresses of the template VMs.
|
| Orphaned_vms |
Indicates the total number of orphaned vms that have been currently detected on all ESX servers managed by VC. |
Number |
An orphan virtual machine is one that exists in the vCenter database but is no longer present on the ESX Server host. A virtual machine also shows as orphaned if it exists on a different ESX Server host than the ESX Server host expected by vCenter.
A virtual machine can become orphaned, in any of the following situations:
After a VMotion or VMware DRS Migration;
After a VMware HA host failure occurs or after the ESX Server host comes out of maintenance mode;
If you delete a virtual machine outside of vCenter - say, through the VMware Management Interface while VC is down, or through the Virtual Infrastructure (VI) client directly connected to an ESX server host;
If vCenter is restarted while a migration is in progress; this is a temporary situation though;
If you schedule too many virtual machines to be relocated at the same time;
To know the names of the orphaned VMs, use the detailed diagnosis of this measure, if enabled.
|
| Disconnected_vms |
Indicates the number of VMs that are currently disconnected from the ESX server. |
Number |
|
| Invalid_vms |
Indicates the number of VMs that are currently invalid. |
Number |
|
| Inaccess_vms |
Indicates the number of VMs that are currently inaccessible. |
Number |
When an ESX Server machine is rebooted or a host agent is restarted, it needs to reload the host agent configuration of each registered virtual machine. If the .vmx file is inaccessible, ESX Server is unable to read the configured name of the virtual machine, and it defaults to "Unknown VM." This is a problem only during restarts. Temporarily losing access to storage does not cause a virtual machine's name to be set to "Unknown VM". The workaround is to rename the virtual machines that have gotten into this state, after they become available again.
|