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
Cause
You submied the action to change the CPU or memory reservation or limit value to a value greater than the
value supported by vCenter Server, or the submied reservation value is greater than the limit.
Solution
u
Run the action using a lower value.
Troubleshooting Set Memory Resources When the Value is Not Evenly Divisible by
1024
If you run the Set Memory Resources action with a value that cannot convert from kilobytes to megabytes,
the task fails and an error appears in the Recent Task messages.
Problem
The Recent Tasks list indicates that a Set Memory Resource action has a state of Failed. When you evaluate
the Messages list for the selected task, you see a message similar to the following example.
Parameter validation;[newLimitKB] failed conversion to (MB, (KB)[2000] not evenly divisible by
1024
Cause
Because vCenter Server manages memory reservations and limit values in megabytes, but
vRealize Operations Manager calculates and reports on memory in kilobytes, you must provide a value in
kilobytes that is directly convertible to megabytes. To do that, the value must be evenly divisible by 1024.
Solution
u
Run the action where the reservation and limit values are congured with supported values.
The supported values for reservation include 0 or a value greater than 0 that is evenly divisible by 1024.
The supported values for a limit include -1, 0, or a value greater than 0 that is evenly divisible by 1024.
Troubleshooting Failed Shut Down VM Action Status
A shut down VM action task has a Failed status in the Recent Task list.
Problem
The Shut Down VM action did not run successfully.
The Recent Tasks list indicates that a Shut Down VM action has a task status of Failed. When you evaluate
the Messages list for the selected job, you see Failure: Shut down confirmation timeout.
Cause
The shut down process involves shuing down the guest operating system and powering o the virtual
machine. The wait time is 120 seconds to shut down the guest operating system. If the guest operating
system does not shut down in this time, the action fails because the shut down action is not conrmed.
Solution
u
Check the status of the guest operating system in vCenter Server to determine why is did not shut
down in the alloed time.
Chapter 1 Monitoring Objects in Your Managed Environment by Using vRealize Operations Manager
VMware, Inc. 75