| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Total_phy_cpu_available |
The aggregated CPU resources of all hosts in the cluster |
Mhz |
|
| Effective_cpu_to_cluster |
The effective CPU resources currently available to run virtual machines |
Mhz |
This is the aggregated effective resource level from all running hosts. Hosts that are in maintenance mode or unresponsive are not counted. Resources used by VMware Service console are not included in the aggregate. This value represents the amount of resources available for the root resource pool for running virtual machines. |
| Cluster_cpu_usage |
The current physical CPU usage of the VMs in the cluster in Mhz |
Mhz |
|
| Physical_cpu_used |
The percentage of physical CPU resources utilized by the VMs in the cluster |
Percent |
Ideally, a cluster should use only a small percentage of the aggregated physical CPU resources of all the hosts within. High CPU usage by one/more hosts in a cluster could drain the physical resources of other hosts in the cluster, thereby affecting the performance of the applications executing on their VMs.
In the event of excessive CPU usage by a cluster, it is therefore imperative that you quickly identify which hosts in the cluster, and which VMs on those hosts are responsible for the CPU drain. For this purpose, you can use the detailed diagnosis of this measure, which reveals the VMs in the cluster and the CPU usage of each VM; this way, you can rapidly isolate resource-intensive VMs.
|
| Effective_cpu_available |
The unused CPU currently available with the cluster |
Mhz |
This is the difference between the effective CPU resources available with the cluster for running VMs and the effective CPU resources used by the cluster. Ideally, the value of this measure should be high. A very low value or a value that consistently sinks could be a cause for concern, as it could indicate a CPU resource contention on the cluster. |
| Physical_machine_memory |
The aggregated memory resources of all hosts in the cluster |
MB |
|
| Effective_memory_to_cluster |
The effective memory resources currently available to run virtual machines |
MB |
This is the aggregated effective resource level from all running hosts. Hosts that are in maintenance mode or unresponsive are not counted. Resources used by VMware Service console are not included in the aggregate. This value represents the amount of resources available for the root resource pool for running virtual machines. |
| Memory_in_use_by_vms |
The amount of host memory currently used by the VMs in the cluster |
MB |
|
| Physical_memory_used |
The percentage of physical memory resources utilized by the cluster |
Percent |
Ideally, a cluster should use only a small percentage of the aggregated physical memory resources of all the hosts within. High memory usage by one/more hosts in a cluster could drain the physical resources of other hosts in the cluster, thereby affecting the performance of the applications executing on their VMs. |
| Cpu_cores |
The number of physical cpu cores currently within the cluster; these are the processes contained by the CPU package. |
Number |
|
| Effective_hosts |
The total number of effective hosts in the cluster, currently |
Number |
|
| Physical_Hosts_in_cluster |
The total number of physical hosts in the cluster, currently |
Number |
The detailed diagnosis of this measure, if enabled, reveals the name and IP address of the physical hosts in the cluster. |
| Vms_in_cluster |
The total number of VMs in the cluster, currently |
Number |
The detailed diagnosis of this measure, if enabled, reveals the name of the VM, the ESX server on which the VM is executing, and and IP address of the ESX server. |
| Vms_on |
The total number of VMs that are currently powered-on in the cluster |
Number |
The detailed diagnosis of this measure, if enabled, reveals the details of the powered-on VMs. |
| Vms_off |
The total number of VMs that are currently powered-off in the cluster |
Number |
|
| Vms_suspended |
The total number of VMs that are currently in a suspended state in the cluster |
Number |
|
| Effective_cpu_reserved |
The total amount of CPU resources that have been used to satisfy the reservation requirements of child resource pool and VMs |
Mhz |
|
| Effective_cpu_available |
The amount of effective CPU resources with the cluster that are currently unused |
Mhz |
Ideally, the value of this measure should be high. |
| Cpu_reserved_by_vms |
The total amount of CPU reserved for VMs in the cluster |
Mhz |
Use the detailed diagnosis of this measure to figure out how much CPU has been reserved for each of the VMs in the cluster. |
| Cpu_reserved_by_rps |
The total amount of CPU resources reserved by the direct pools in the cluster |
Mhz |
Use the detailed diagnosis of this measure to figure out how much CPU has been reserved by each of the direct pools in the cluster. |
| Cpu_used_by_rps |
The amount of CPU currently used by direct pools in the cluster |
Mhz |
In the event of abnormal CPU usage at the pool-level, use the detailed diagnosis of this measure to identify which direct pool is consuming CPU excessively. |
| Effective_mem_reserved |
The total amount of memory resources that have been used to satisfy the reservation requirements of child resource pool and VMs |
MB |
|
| Effective_mem_available |
The amount of effective memory resources with the cluster that are currently unused |
MB |
Ideally, the value of this measure should be high. |
| Mem_reserved_by_vms |
The total amount of memory reserved for VMs in the cluster |
MB |
Use the detailed diagnosis of this measure to figure out how much memory has been reserved for each of the VMs in the cluster. |
| Mem_reserved_by_rps |
The total amount of memory resources reserved by the direct pools in the cluster |
MB |
Use the detailed diagnosis of this measure to figure out how much memory has been reserved by each of the direct pools in the cluster. |
| Mem_consumed_by_rps |
The amount of memory currently used by direct pools in the cluster |
MB |
A high value is indicative of excessive memory usage by the direct pools in the cluster. In such circumstances, take the help of the detailed diagnosis capability of this measure to quickly zero-in on that direct pool that consumes maximum memory. |
| Mem_consumed_by_cluster |
The total amount of memory currently consumed by the VMs in the cluster |
MB |
A high value is indicative of excessive memory usage by the VMs in the cluster. In such circumstances, take the help of the detailed diagnosis capability of this measure to quickly zero-in on that VM that consumes maximum memory. |
| Total_migration |
The total number of migrations with VMotion that have been done internal to this cluster |
Number |
|
| Usage_on_effective_cpu |
Indicates the percentage of effective CPU resources currently available to run the virtual machines. |
Percent |
A high value is desired for this measure. |
| Usage_on_effective_Memory |
Indicates the percentage of effective memory resources currently available to run the virtual machines. |
Percent |
A high value is desired for this measure. |
| HA_enabled |
Indicates whether/not this cluster is HA-enabled. |
|
If vSphere HA (High Availability) is enabled on a cluster, then vSphere will provide high availability for virtual machines on the cluster. Hosts in the cluster are monitored and in the event of a failure, the virtual machines on a failed host are restarted on alternate hosts.
If vSphere HA is enabled on a cluster, then the value of this measure will be Yes. If not, then this measure will report the value No.
The numeric values that correspond to these measure values are discussed in the table below:
| Measure Value |
Numeric Value |
| Yes |
1 |
| No |
0 |
Note:
By default, this measure reports the Measure Values listed in the table above. In the graph of this measure however, the vSphere HA state is represented using the corresponding numeric equivalents only.
|
| Dpm_enabled |
Indicates whether/not the DPM service is enabled for this cluster. |
|
VMware® Distributed Power Management (VMware DPM) provides additional power savings by dynamically right-sizing cluster capacity according to workload demands. VMware DPM recommends the evacuation and powering off of ESX hosts when both CPU and memory resources are lightly utilized. VMware DPM recommends powering ESX hosts back on when either CPU or memory resource utilization increases appropriately or additional host resources are needed to meet VMware HA or user-specified constraints. VMware DPM executes VMware DRS in a what-if mode to ensure its host power recommendations are consistent with the cluster constraints and objectives being managed by VMware DRS.
Since VMware DPM works in conjunction with VMware DRS, this measure will report a value only if the ‘DRS enabled’ measure reports the value Yes.
If DPM is enabled for a cluster, then the value of this measure will be Yes. If not, then the measure will report the value No.
The numeric values that correspond to these measure values are discussed in the table below:
| Measure Value |
Numeric Value |
| Healthy |
1 |
| Unhealthy |
0 |
Note:
By default, this measure reports the Measure Values listed in the table above. In the graph of this measure however, the vSphere DPM state is represented using the corresponding numeric equivalents only.
|
| Drs_enabled |
Indicates whether/not the DRS service is enabled for this cluster. |
|
DRS (Dynamic Resource Scheduler) is a powerful feature that enables your virtual environment to automatically balance itself across your ESX host servers in an effort to eliminate resource contention. It utilizes the VMotion feature to provide automated resource optimization through automatic migration of VMs across hosts in a cluster. DRS also provides automatic initial VM placement on any of the hosts in the cluster, and makes automatic resource relocation and optimization decisions as hosts or VMs are added to or removed from the cluster. You can also configure DRS for manual control so that it only provides recommendations that you can review and carry out.
DRS works by utilizing resource pools and clusters that combine the resources of multiple hosts into a single entity. When a VM experiences increased load, DRS first evaluates its priority against the established resource allocation rules and then, if justified, redistributes VMs among the physical servers to try to eliminate contention for resources. VMotion will then handle the live migration of the VM to a different ESX host with complete transparency to end users. The dynamic resource allocation ensures that capacity is preferentially dedicated to the highest-priority applications, while at the same time maximizing overall resource utilization.
If DRS is enabled for a cluster, then the value of this measure will be Yes. If not, then the measure will report the value No.
The numeric values that correspond to these measure values are discussed in the table below:
| Measure Value |
Numeric Value |
| Yes |
1 |
| No |
0 |
Note:
By default, this measure reports the Measure Values listed in the table above. In the graph of this measure however, the vSphere DRS state is represented using the corresponding numeric equivalents only.
|
| Vsan_enabled |
Indicates whether/not the vSAN service is enabled for this cluster. |
|
Virtual SAN virtualizes local physical storage resources of vSphere hosts and turns them into pools of storage that can be carved up and assigned to virtual machines and applications according to their quality of service requirements.
You can activate Virtual SAN when you create host clusters or enable Virtual SAN on existing clusters. When enabled, Virtual SAN aggregates all local storage disks available on the hosts into a single datastore shared by all hosts. You can later expand the datastore by adding storage devices or hosts to the cluster.
If vSAN is not enabled for a cluster, then the value of this measure will be No. If vSAN is enabled, then the value of this measure will be Yes. The numeric values that correspond to these measure values are discussed in the table below:
| Measure Value |
Numeric Value |
| Yes |
1 |
| No |
0 |
Note:
By default, this measure reports the Measure Values listed in the table above. In the graph of this measure however, the state of the vSAN is represented using the corresponding numeric equivalents only.
|