Open topic with navigation
Defining Thresholds
On the Thresholds tab, you can define the VM sizing thresholds and VM activity thresholds. Additionally, you can define the size of the reference VM.
Thresholds
SHO displays the VM sizing and activity summary based on the utilization and deviation thresholds defined in this section.
Deviation threshold is the percentage of extra utilization that can be accepted without impacting service levels. This threshold is the tolerance level beyond which the utilization is not acceptable. The default value is provided by SHO.
Note: The values defined for the utilization and deviation threshold must be between 0 to 100.
Recommended VM Size Based On
Select the type of data to be considered to calculate the recommended VM size and to discover undersized and oversized VMs. The options available in the Recommended VM Size Based On drop-down list are:
- Peak
- 95th Percentile
- Average
Based on the thresholds defined in this section, SHO determines whether a VM resource is undersized or oversized. Additionally, you can define the default headroom to be considered while recommending the ideal VM size.
Undersized
Field |
Description |
CPU Utilization |
The minimum CPU utilization percentage beyond which the CPU is classified as over utilized.
|
CPU Deviation |
The minimum deviation threshold percentage beyond which the CPU is classified as undersized. |
Memory Utilization |
The minimum memory utilization percentage beyond which the memory is classified as over utilized.
|
Memory Deviation |
The minimum deviation threshold percentage beyond which the memory is classified as undersized. |
Oversized
Field |
Description |
CPU Utilization |
The maximum CPU utilization percentage below which the CPU is classified as underutilized. |
CPU Deviation |
The minimum deviation threshold percentage beyond which the CPU is classified as oversized. |
Memory Utilization |
The maximum memory utilization percentage below which the memory is classified as underutilized. |
Memory Deviation |
The minimum deviation threshold percentage beyond which the memory is classified as oversized. |
Headroom
Field |
Description |
CPU Headroom |
The percentage of CPU headroom to be allocated while recommending the VM size. The headroom defined here is used to calculate the recommended size displayed on the Inventory screen. Additionally, the CPU headroom is used to calculate the optimization opportunity ratings on the Executive Summary and Detailed views. |
Memory Headroom |
The percentage of memory headroom to be allocated while recommending the VM size. The headroom defined here is used to calculate the recommended size displayed on the Inventory screen. Additionally, the memory headroom is used to calculate the optimization opportunity ratings on the Executive Summary and Detailed views. |
Based on the thresholds defined in this section, SHO determines whether a VM resource is idle or switched off.
Idle
Field |
Description |
CPU Utilization |
The maximum CPU utilization percentage below which the CPU is classified as underutilized. |
CPU Deviation |
The minimum deviation threshold percentage beyond which the CPU is classified as idle. |
Off
Field |
Description |
Off |
The minimum percentage of time for which a VM has to be powered off for it to be considered in the off state. |
Based on the thresholds defined in this section, SHO determines whether a Datastore resource is undersized or oversized. Additionally, you can define the default headroom to be considered while recommending the ideal Datastore size.
Undersized
Field |
Description |
Datastore Utilization |
The minimum Datastore allocation percentage beyond which the Datastore is classified as over utilized.
|
Oversized
Field |
Description |
Datastore Utilization |
The maximum Datastore allocation percentage below which the Datastore is classified as underutilized.
|
Number of days for oversized analysis |
The number of days for which the Datastore allocation must be below the maximum Datastore allocation percentage for the Datastore to be labeled as oversized. |
Data Quality
You can define the threshold for the minimum amount of data available for each VM for the VM to be considered for analysis.
Additionally, you can define the acceptable data gaps in the data of the VM for it to be considered for VM activity, VM sizing, and VM placement analysis.
Inventory - VM Size and VM Activity Analysis
- In the Acceptable data gaps field, define the maximum acceptable data gaps.
- In the Minimum data required field, define the minimum number of days for which valid data must be available for a VM.
If a VM fails to satisfy both the thresholds, it will not be considered for VM sizing and VM activity analysis. Also, it will be classified under VMs with Insufficient Data on the VM Activity pie chart.
Optimization Scenario
The thresholds that you define in this section are applicable if you select VM placement based on utilization data on the Scenario Planning page.
- In the first text box, define the percentage of configured capacity to be considered as the required VM size in case the optimization analysis takes place based on the configured capacity of the VMs due to insufficient data.
-
In the second text box, define the threshold percentage of analysis period below which VM Placement is done based on configured capacity.
For a VM, if the resource data is available for less than the specified threshold percentage of the defined analysis period, SHO ignores resource usage data and does VM placement based on the configured capacity. A pop-up window appears with the names of such VMs when you open the scenario planning page.
Aging
SHO marks those hosts as deleted which have no data for the number of days that you specify in this field.
Forecast
Define the threshold value for the resource capacity violation analysis. A default value is specified by SHO.
Click Save to save the changes that you made on this tab or click Cancel to discard the changes.
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to docfeedback@hp.com.
Help Topic ID:
Product:
Topic Title:
Feedback:
© 2011-2012 Hewlett-Packard Development Company, L.P.