5.7
Table Of Contents
- VMware vCenter Operations Manager Getting Started Guide
- Contents
- VMware vCenter Operations Manager Getting Started Guide
- Introducing Key Features and Concepts
- Beginning to Monitor the Virtual Environment
- Object Type Icons in the Inventory Pane
- Badge Concepts for vCenter Operations Manager
- Major Badges in vCenter Operations Manager
- Working with Metrics and Charts on the All Metrics Tab
- Viewing Members and Relationships in the Monitored Environment
- Check the Performance of Your Virtual Environment
- Balancing the Resources in Your Virtual Environment
- Find an ESX Host that Has Resources for More Virtual Machines
- Find a Cluster that Has Resources Available for More Virtual Machines
- Ranking the Health, Risk, and Efficiency Scores
- View the Compliance Details
- View a List of Members
- Overview of Relationships
- Troubleshooting with vCenter Operations Manager
- Troubleshooting Overview
- Troubleshooting a Help Desk Problem
- Troubleshooting an Alert
- Finding Problems in the Virtual Environment
- Finding the Cause of the Problem
- Determine Whether the Environment Operates as Expected
- Identify the Source of Performance Degradation
- Identify the Underlying Memory Resource Problem for a Virtual Machine
- Identify the Underlying Memory Resource Problem for Clusters and Hosts
- Identify the Top Resource Consumers
- Identify Events that Occurred when an Object Experienced Performance Degradation
- Determine the Extent of a Performance Degradation
- Determine the Timeframe and Nature of a Health Issue
- Determine the Cause of a Problem with a Specific Object
- Fix the Cause of the Problem
- Assessing Risk and Efficiency in vCenter Operations Manager
- Analyzing Data for Capacity Risk
- Determine When an Object Might Run Out of Resources
- Identify Clusters with the Space for Virtual Machines
- Investigating Abnormal Host Health
- Identify Datastores with Space for Virtual Machines
- Identify Datastores with Wasted Space
- Address a Problem with a Specific Virtual Machine
- Identify the Virtual Machines with Resource Waste Across Datastores
- Address a Problem with a Specific Datastore
- Identify the Host and Datastore with the Highest Latency
- Optimizing Data for Capacity
- Determine How Efficiently You Use the Virtual Infrastructure
- Identify the Consolidation Ratio Trend for a Datacenter or Cluster
- Determine Reclaimable Resources from Underused Objects
- Assess Virtual Machine Capacity Use
- Assess Virtual Machine Optimization Data
- Identify Powered-Off Virtual Machines to Optimize Data
- Identify Idle Virtual Machines to Optimize Capacity
- Identify Oversized Virtual Machines to Optimize Data
- Determine the Trend of Waste for a Virtual Machine
- Forecasting Data for Capacity Risk
- Create Capacity Scenarios for Virtual Machines With New Profiles
- Create Capacity Scenarios for Virtual Machines With Existing Profiles
- Create a Hardware Change Scenario
- Create a What-If Scenario to Remove Virtual Machines
- Combine the Results of What-If Scenarios
- Compare the Results of What-If Scenarios
- Delete a Scenario from the What-If Scenarios List
- Analyzing Data for Capacity Risk
- Working with Faults and Alerts
- Working with Groups
- Set How Data Appears in vCenter Operations Manager
- Create a New Policy
- Set the General Parameters of a Policy
- Associate a Policy with One or More Groups
- Customize Badge Thresholds for Infrastructure Objects
- Customize Badge Thresholds for Virtual Machine Objects
- Customize the Badge Thresholds for Groups
- Modify Capacity and Time Remaining Settings
- Modify Usable Capacity Settings
- Modify Usage Calculation Settings
- Modify the Criteria for Powered-Off and Idle Virtual Machine State
- Modify the Criteria for Oversized and Undersized Virtual Machines
- Modify the Criteria for Underused and Stressed Capacity
- Select Which Badges Generate Alerts
- Modify Trend and Forecast Analysis Settings
- Modify an Existing Policy
- Modify Summary, Views, and Reports Settings
- Create a New Policy
- Monitor the Performance of vCenter Operations Manager
- Index
3 Click 4a Powered off and idle VMs and change the settings for powered-off and idle virtual machines.
Option Description
% Time Powered-off threshold
Percentage of time during which the virtual machine is powered off.
A virtual machine is considered as powered off by using the following
calculation.
The number of hours that vm is powered off in non-trend view
interval
/ number of hours set in non-trend view >= %time powered off
threshold
Idle VM Detection Rules
% Time Idle threshold
Percentage of time during which the virtual machine is powered on but
inactive, so that you identify the virtual machine as idle.
For a given hour, a virtual machine passes the idle detection criteria for that
hour if it satisfies the resource threshold for all/any specified enabled
resource.
A virtual machine is considered idle by using the followinf calculation.
Number of hours that virtual machine passes the idle
detection criteria in non-trend view interval
/ number of hours in non-trend view >= %time idle threshold
Detection based on any of the
thresholds
If any of the selected counters falls below the minimum threshold, the virtual
machine is considered to be idle.
Detection based on all of the
thresholds
All selected counters must fall below the minimum threshold for the virtual
machine to be considered idle.
Average Resource Usage Criteria
You can select the minimum usage of CPU, Disk I/O, and network resources
to determine the idle detection criteria. vCenter Operations Manager uses
these criteria to determine if the virtual machine is idle, based on the % Time
Idle threshold that you set.
4 Click OK or Finish to save your settings, or select another option to configure.
5 Click Done to close the Configuration dialog box.
The settings for powered off and idle virtual machines are reconfigured.
Modify the Criteria for Oversized and Undersized Virtual Machines
You can select the level of activity that constitutes an oversized or undersized virtual machine.
An administrator can modify any policy in vCenter Operations Manager at any time. The changes that the
administrator applies affect all users. Therefore, the administrator must notify the users who are working with
vCenter Operations Manager about any new settings that are applied to the policies.
IMPORTANT Oversizing and undersizing refers to the amount of capacity that a virtual machine has available,
not the amount of work being performed. An undersized virtual machine has less capacity than is needed to
perform work. An oversized virtual machine has more capacity than is needed to perform work.
Prerequisites
Verify that you are logged in to a vSphere Client as an administrator, and vCenter Operations Manager is open.
Procedure
1 Click the Configuration link on the main vCenter Operations Manager page.
Chapter 8 Set How Data Appears in vCenter Operations Manager
VMware, Inc. 99