6.4
Table Of Contents
- vRealize Operations Manager User Guide
- Contents
- About This User Guide
- Monitoring Objects in Your Managed Environment
- What to Do When...
- User Scenario: A User Calls With a Problem
- User Scenario: An Alert Arrives in Your Inbox
- Respond to an Alert in Your Email
- Evaluate Other Triggered Symptoms for the Affected Data Store
- Compare Alerts and Events Over Time in Response to a Datastore Alert
- View the Affected Datastore in Relation to Other Objects
- Construct Metric Charts to Investigate the Cause of the Data Store Alert
- Run a Recommendation On a Datastore to Resolve an Alert
- User Scenario: You See Problems as You Monitor the State of Your Objects
- Monitoring and Responding to Alerts
- Monitoring and Responding to Problems
- Evaluating Object Summary Information
- Investigating Object Alerts
- Evaluating Metric Information
- Analyzing the Resources in Your Environment
- Using Troubleshooting Tools to Resolve Problems
- Creating and Using Object Details
- Examining Relationships in Your Environment
- User Scenario: Investigate the Root Cause a Problem Using Troubleshooting Tab Options
- Running Actions from vRealize Operations Manager
- List of vRealize Operations Manager Actions
- Working With Actions That Use Power Off Allowed
- Actions Supported for Automation
- Integration of Actions with vRealize Automation
- Run Actions From Toolbars in vRealize Operations Manager
- Troubleshoot Actions in vRealize Operations Manager
- Monitor Recent Task Status
- Troubleshoot Failed Tasks
- Determine If a Recent Task Failed
- Troubleshooting Maximum Time Reached Task Status
- Troubleshooting Set CPU or Set Memory Failed Tasks
- Troubleshooting Set CPU Count or Set Memory with Powered Off Allowed
- Troubleshooting Set CPU Count and Memory When Values Not Supported
- Troubleshooting Set CPU Resources or Set Memory Resources When the Value is Not Supported
- Troubleshooting Set CPU Resources or Set Memory Resources When the Value is Too High
- Troubleshooting Set Memory Resources When the Value is Not Evenly Divisible by 1024
- Troubleshooting Failed Shut Down VM Action Status
- Troubleshooting VMware Tools Not Running for a Shut Down VM Action Status
- Troubleshooting Failed Delete Unused Snapshots Action Status
- Viewing Your Inventory
- What to Do When...
- Planning the Capacity for Your Managed Environment
- Index
If you select Power O Allowed, and the machine is running, the action veries whether VMware Tools is
installed and running.
n
If VMware Tools are installed and running, the virtual machine is shut down before completing the
action.
n
If VMware Tools are not running or not installed, the virtual machine is powered o without regard for
the state of the operating system.
If you do not select Power O Allowed and you are decreasing the CPU count or memory, or the hot plug is
not enabled for increasing the CPU count or memory, the action does not run and the failure is reported in
Recent Tasks.
Power Off Allowed When Changing CPU Count or Memory
When you run the actions that change the CPU count and the amount of memory, you must consider several
factors to determine if you want to use the Power O Allowed option. These factors include whether you are
increasing or decreasing the CPU or memory and whether the target virtual machines are powered on. If
you increasing the CPU or memory values, whether hot plug is enabled also aects how you apply the
option when you run the action.
How you use Power O Allowed when you are decreasing the CPU count or the amount of memory
depends on the power state of the target virtual machines.
Table 1‑6. Decreasing CPU Count and Memory Behavior Based On Options
Virtual Machine Power State Power Off Allowed Selected Results
On Yes If VMware Tools is installed and
running, the action shuts down the
virtual machine, decreases the CPU or
memory, and powers the machine back
on.
If VMware Tools is not installed, the
action powers o the virtual machine,
decreases the CPU or memory, and
powers the machine back on.
On No The action does not run on the virtual
machine.
O Not applicable. The virtual machine
is powered o.
The action decreases the value and
leaves the virtual machine in a
powered o state.
How you use Power O Allowed when you are increasing the CPU count or the amount of memory
depends on several factors, including the state of the target virtual machine and whether hot plug is
enabled. Use the following information to determine which scenario applies to your target objects.
If you are increasing the CPU count, you must consider the power state of the virtual machine and whether
CPU Hot Plug is enabled when determining whether to apply Power O Allowed.
vRealize Operations Manager User Guide
62 VMware, Inc.