Page tree
Skip to end of metadata
Go to start of metadata

The Clusters page in the vSphere Infrastructure view enables you to identify the number of additional VMs that can be added to each cluster, the total and available resources in the cluster, and manages the resources of all the hosts it contains. The page displays details about VMs that are currently powered on and running, their CPU and memory utilization, how many additional VMs can be added to each cluster depending on the spare cluster capacity, among other details. You can revise the calculation of the spare VM basis for an average VM by modifying the spare VM basis settings from this page.

The data displayed in the page provides a complete picture of cluster memory usage and contention using Memory metrics, and helps answer critical questions related to subsystems, such as the follows:

  • Is vSphere memory management working right in my environment?
  • Is vSphere page sharing mechanism used effectively in my environment? How much memory is shared?
  • How much memory is over-committed?

To access the page, in the TrueSight console navigation pane, click Capacity Views > Virtualization > vSphere > Infrastructure, and in the vSphere Infrastructure page, click the Clusters tab.

The data in the page is categorized based on different subsystems and grouped under separate tabs. Click a tab to view the metrics for that subsystem: 

SubsystemDescription
CapacityDisplays consolidated trend and saturation related metrics for the three subsystems: CPU, Memory and Storage. Also displays VM, Spare VM and bottleneck-related data.
CPUDisplays CPU related metrics for clusters.
MemoryDisplays memory related metrics, including Ballooning, Swap Rate and Granted memory for clusters.
StorageDisplays storage related data for vSphere clusters.

Metrics per cluster are displayed in a tabular format.

By default, some columns are hidden. You can show or hide columns using the action menuthat is located next to the table title.

This topic contains the following sections:

Capacity metrics

Capacity metrics are displayed in the Capacity page. The Capacity tab is displayed by default, each time you access the Clusters page.

Each row in the table represents a cluster and displays the following metrics:


Column

Description

Statistical
Type 
 Metrics

Cluster

Name of the the vSphere cluster.

Not applicable 
LocationLocation site of the cluster.Last valueLOCATION_SITE
Data CenterName of the data center associated with the cluster.Last valueRelationship DC_CONTAINS_VHC is used to get the NAME of the data center
vCenterName of the vCenter associated with the cluster.Last valueVIRTUALCENTER_NAME
CPU [MHz]Total CPU available/configured on the the cluster.Last valueCPU_TOTAL_MHZ

CPU Util [%]

CPU utilization of the cluster computed by scaling the CPU MHz usage of the cluster by the effective CPU MHz available to the cluster.95th percentileCPU_UTIL 
CPU Pressure1 

A value between 0 and 100, calculated using CPU Util and CPU ready time. This value must always be greater than or equal to CPU Util %. If this is much higher than CPU Util %, then it indicates that some VMs in the cluster are starved for CPU (high CPU ready time). See Watchlist page in the vSphere Virtual Machines view to identify them.

For more information, see Computation details for VMware metrics.

95th percentileIND_CPU_PRESSURE

CPU Trend [MHz]

Daily growth rate of CPU utilization of the vSphere cluster, measured in MHz/day.

TrendComputed using CPU_UTIL_MHZ over time
CPU Days To SaturationEstimated number of days before the CPU capacity of the cluster breaches the configured threshold. If the value is greater than 30 days, it is not displayed.  Not ApplicableIND_DAYS_TO_SATURATION[CPU] 
Memory [GB]Total physical memory configured for the cluster, measured in GB.Last valueTOTAL_REAL_MEM

Memory Util [%]

Percentage of total memory utilized by the vSphere cluster (average value).

95th percentileMEM_UTIL
Composite Memory Util [%]1

Consumed memory of a vSphere host or cluster is too high, while Active memory gives too low a picture of usage. The Composite memory consumption is a more realistic estimate of the amount of memory that is effectively in use in the host or cluster. It considers both Active and Consumed memory numbers reported by vSphere, and adjusts these using memory pressure due to contention, as measured by swapping, ballooning, and the total memory over-commitment in the host/cluster. Composite Memory Util [%] is a percentage calculated over the total memory of the host or cluster.

95th percentileIND_COMPOSITE_MEMORY_UTILIZATION
Memory Trend [GB]

Daily growth rate of memory utilization of the vSphere cluster per the current trend, measured in GB/day.

TrendComputed using MEM_CONSUMED over time
Memory Days To SaturationEstimated number of days before the memory of the cluster breaches the configured threshold; if the value is greater than 30 days, it is not displayed.  Not ApplicableIND_DAYS_TO_SATURATION[MEMORY] 
Datastore [GB]Total storage configured for the datastores in the cluster, measured in GB.Last valueTOTAL_DSTORE_SIZE
Datastore  Util [%]

Percentage of total datastore space utilized by the vSphere cluster.

95th percentileTOTAL_DSTORE_UTIL
Datastore Trend [GB]Daily growth rate of datastore utilization in the cluster.TrendComputed using TOTAL_DSTORE_USED over time
Storage Days to Saturation

Estimated number of days before the storage of the cluster breaches the configured warning threshold.

Not applicableIND_DAYS_TO_SATURATION[STORAGE] 
Host CountThe total number of hosts configured in the cluster.Last valueHOST_NUM
Powered ON VMs

Total number of VMs currently powered on in the vSphere cluster.

Average

GM_ON_NUM
VMs On TrendDaily growth rate of powered-on VMs.TrendComputed using VM_POWERON_NUM over time
Spare VMs

Estimated number of additional VMs that can be placed in the cluster.

Computed metric:

  • 95th percentile values are used for CPU Used at cluster and VM level
  • Last value is used for cluster total capacity
  • Only currently powered on VMs are considered
IND_SPARE_VM[GLOBAL]
Spare VM basis

Specifies the basis for calculating the number of additional VMs that can be placed in the cluster: TYPICAL or CUSTOM. The calculation also factors in Datastore Utilization (Storage) to calculate Spare VMs. For more information, see Spare VM calculation in
see Recalculating the spare VM basis.

Not applicable 
Limiting Resource

The resource that limits the number of additional VMs that can be placed in the cluster. It is the least available of the three resources – CPU, MEMORY, and STORAGE. The value MANY is displayed if all the three resources are limiting. The value might not necessarily exceed the threshold.

Computed using 95th percentile valuesResource with lowest Spare VMs among  IND_SPARE_VM[CPU], IND_SPARE_VM[MEMORY], IND_SPARE_VM[STORAGE]
Total Spec RatingThe total SPEC benchmark performance rating of the cluster based on the CPU model and number of CPU cores.Last value BYBENCHMARK_VALUE[SPECINTRATE2006]
Unused Spec RatingUnused SPEC rating of the cluster, based on CPU utilization and the total SPEC rating.95th percentileComputed using CPU_UTILMHZ, CPU_TOTAL_MHZ and BYBENCHMARK_VALUE[SPECINTRATE2006]

1 - The metric value is incomplete if you have explicitly excluded (blacklisted) or included (whitelisted) virtual machines or hosts while configuring the VMware vCenter Extractor ETL.

Notes

  • For more information about VMware metrics, see Metrics collected by VMware ETLs.
  • For more information about the Days to Saturation and other indicator parameters used for metric computations in this view, see Indicators.

CPU metrics

CPU metrics are displayed in the CPU page. Click the CPU tab in the Clusters page to access the metrics.

Each row in the table represents a cluster and its corresponding vCenter and displays the following metrics:

Column

Description

Statistical
Type
Metrics 

Cluster

Name of the vSphere cluster

Not applicable 

vCenter

Name of the vCenter on which the vSphere cluster is configured.

Not applicable 
Data CenterName of the data center associated with the cluster.Not applicableRelationship DC_CONTAINS_VHC is used to get the NAME of the data center

CPU Util [%]

CPU utilization of the cluster computed by scaling the CPU MHz usage of the cluster by the effective CPU MHz available to the cluster.

95th percentileCPU_UTIL 
CPU Pressure1

A value between 0 and 100, calculated using CPU Util and CPU ready time. This value must always be greater than or equal to CPU Util %. If this is much higher than CPU Util %, then it indicates that some VMs in the cluster are starved for CPU (high CPU ready time). See Watchlist page in the vSphere Virtual Machines view to identify them.

For more information, see Computation details for VMware metrics.

95th percentileIND_CPU_PRESSURE
CPU [MHz]Total processing capacity available to the vSphere cluster.Last value

CPU_TOTAL_MHZ

CPU [Cores]

Total number of physical CPU cores available to the vSphere cluster.

Last value

CPU_NUM

Unused CoresNumber of unused CPU coresComputed metric- Based on 95th Percentile of CPU usageComputed using CPU_UTIL and CPU_NUM

vCPUs

Total number of virtual CPU cores available to the vSphere cluster.

Last valueVCPU_NUM

#vCPU ON

Total number vCPUs that are currently powered on in the vSphere cluster.

Last valueVCPU_ON_NUM

#vCPU/host

Total number of vCPUs available to each host in the vSphere cluster.

Last valueComputed using VCPU_NUM and HOST_NUM

vCPU density

Total vCPU density, that is, total number of vCPUs per physical core in the vSphere cluster.

Computed metric - uses average value for VCPU_NUM and CPU_NUMComputed using VCPU_NUM and CPU_NUM
Small VMs1Number of VMs in the vSphere cluster that have 1 vCPU.Last valueComputed using VM.CPU_NUM
Medium VMs1Number of VMs in the vSphere cluster that have 2 vCPUs.Last valueComputed using VM.CPU_NUM
Large VMs1Number of VMs in the vSphere cluster with more than 2 vCPUs.Last valueComputed using VM.CPU_NU

1 - The metric value is incomplete if you have explicitly excluded (blacklisted) or included (whitelisted) virtual machines or hosts while configuring the VMware vCenter Extractor ETL.

Memory metrics

Memory metrics are displayed in the Memory page. Click the Memory tab in the Clusters page to access the metrics.

Each row in the table represents a cluster and its corresponding vCenter and displays the following metrics:

Column

Description

Statistical
Type
 Metrics

Cluster

Name of the vSphere cluster

Not applicable 

vCenter

Name of the vCenter on which the vSphere cluster is configured.

Not applicableVIRTUALCENTER_NAME 
Data CenterName of the data center on which the vSphere cluster resides.Not applicableRelationship DC_CONTAINS_VHC is used to get the NAME of the data center

Total Memory [GB]

Total amount of memory available to the vSphere cluster.

Last valueTOTAL_REAL_MEM
Over-commitment [%]1

Sum of memory configured for all the VMs in the cluster divided by the total memory of the cluster expressed as a percentage. If this number is over 100%, then the memory is over-committed. Numbers over 100% are not necessarily an indication of a problem, it indicates efficient use of virtualized resources. However, extremely high memory overcommitment could result is performance problems. The amount of over-commitment can vary in each environment based on the nature of applications and staggering of applications running on the VMs. The default low and high thresholds are 100% and 120%. 

Computed metric - based on Last valueComputed using SUM(VM.TOTAL_REAL_MEM) and Cluster.TOTAL_REAL_MEM

Util [%]

Memory usage scaled by total memory of the cluster. Usage is based on consumed memory.

95th percentile MEM_UTIL
Composite Util [%]1

Consumed memory of a vSphere host or cluster is too high, while Active memory gives too low a picture of usage. The Composite memory consumption is a more realistic estimate of the amount of memory that is effectively in use in the host or cluster. It considers both Active and Consumed memory numbers reported by vSphere, and adjusts these using memory pressure due to contention, as measured by swapping, ballooning, and the total memory over-commitment in the host/cluster.

This metric is a percentage calculated over the total memory of the host or cluster.

For more information, see Computation details for VMware metrics.

95th percentileIND_COMPOSITE_MEMORY_UTILIZATION 

Active [%]

Sum of active memory for all powered-on virtual machines. Active memory of the virtual machine is the amount of memory that is actively used, as estimated by VMkernel based on recently touched memory pages.

95th percentileComputed using ACTIVE_MEMORY and TOTAL_REAL_MEM 

Balloon [%]

The sum of balloon memory of all powered-on virtual machines. Balloon memory of a virtual machine is the amount of physical memory reclaimed through ballooning.

95th percentileComputed using BALLOONING_MEMORY and TOTAL_REAL_MEM 

Granted [%]

The percentage of machine memory that the VMkernel has given to the vSphere cluster based on its memory demand.

95th percentileComputed using GRANTED_MEMORY and TOTAL_REAL_MEM 

Shared [%]

Sum of all shared metrics for all powered-on virtual machines. For a VM, it is the amount of “physical” memory shared with other virtual machines through the VMkernel’s transparent page-sharing mechanism.

95th percentileComputed using SHARED_MEMORY and TOTAL_REAL_MEM  
Overhead [%]Total of all overhead metrics for powered-on virtual machines. For a VM, it is the amount of machine memory used by the VMkernel to run the virtual machine.95th percentileComputed using OVERHEAD_MEMORY and TOTAL_REAL_MEM  
Swap Rate [MB/s]Sum of the rate at which memory is being swapped out from active memory to disk and swapped in from disk into active memory. It is measured in MB/second.Computed metric - based on 95th percentileComputed using MEM_SWAP_IN_BYTE_RATE, MEM_SWAP_OUT_BYTE_RATE

1 - The metric value is incomplete if you have explicitly excluded (blacklisted) or included (whitelisted) virtual machines or hosts while configuring the VMware vCenter Extractor ETL.

Storage metrics

Storage metrics are displayed in the Storage page. Click the Storage tab in the Clusters page to access the metrics.

Each row in the table represents a cluster and its corresponding vCenter and displays the following metrics:

Column

Description

Statistical
Type
Metrics 

Cluster

Name of the vSphere cluster.

Not applicable 

vCenter

Name of the vCenter on which the vSphere cluster is configured.

Not applicable 
Data CenterName of the data center on which the vSphere cluster resides.Last valueRelationship DC_CONTAINS_VHC is used to get the NAME of the data center

Datastore Count

Total number of datastores present in the vSphere cluster.

MAXComputed based on the count of datastore entities associated with the cluster

Capacity [TB]

Total storage capacity of the datastore, measured in terabytes.

Last valueTOTAL_DSTORE_SIZE

Util [%]

Usage of all the datastores in the cluster scaled by the storage capacity of the cluster, expressed in percentage.

95th percentileTOTAL_DSTORE_UTIL

Used [TB]

Total storage space used by the datastore, measured in terabytes.

95th percentileTOTAL_DSTORE_USED1

Free [TB]

Free storage capacity of the cluster.

95th percentileTOTAL_DSTORE_FREE1

Provisioned [TB]

Sum of the storage provisioned for all the datastores in the cluster. Just as memory storage can be over-provisioned, a small amount of over-provisioning indicates efficient use of resources. Excessive over-provisioning can cause the cluster to run out of storage resources.

Last valueTOTAL_DSTORE_PROVISIONED1

1Metrics are available only for clusters that have shared datastores in them.


To view details for a specific vSphere cluster

To view the details page for a particular vSphere cluster, click its (hyper-linked) name under the Cluster column. You can use the sorting and filtering options on the page to find a specific cluster. 

The Cluster details page displays information for the selected cluster under the following sections or panels:

Section or PanelDescription
Summary page

A quick graphical summary of the CPU, memory, and datastore utilization, and network I/O rate of the cluster. Core metrics for the selected entity are displayed as analysis charts, depending on available data. At the bottom of each chart is a link that takes you to the Data Explorer view for the specific resource type, and displays charts and information for a larger set of metrics.

The data displayed in Data Explorer view charts for any resource part of this view category, is based on the time filter that is applied to the primary view in this tab. You can select other time filter options to view charts over a different time resolution

For more information, see Cluster page in the vSphere Data Explorer view.

Configuration Details pageConfiguration information about the cluster.
Related Information panel

Links to detailed pages for thresholds, host details, and VM details. For more information, see Viewing related information.

Recommendations panelAll available recommendations for the cluster. For more information, see Recommendations page in the vSphere Infrastructure view.
Tags panelList of tags that are associated with the cluster. You can assign or remove tags by using the Edit Tags option from the Tags action menu.

To view related information

The Related Information panel located at the top of the view, next to the Recommendations panel in the cluster details page contains the following links:

LinkDescription
ThresholdsOpens the Thresholds page in the TrueSight Capacity Optimization console. Using the Thresholds page, you can view and manage threshold settings for the selected vSphere cluster. For more information, see Adding and viewing thresholds.
Host detailsOpens the Hosts page in the vSphere Infrastructure view that displays information about all configured hosts in the selected vSphere cluster.
VM detailsOpens the All VMs page in the vSphere Virtual Machines view that displays information about all the VMs in the selected vSphere cluster.

To find a specific cluster

Use the sorting and filtering options on the page to find a specific cluster. For more information, see Sorting tables in views in the TrueSight console and Using filtering options in views in the TrueSight console.

 

1 Comment

  1.