6.3
Table Of Contents
- vRealize Operations Manager Customization and Administration Guide
- Contents
- About Customization and Administration
- Configuring Users and Groups
- Customizing How vRealize Operations Manager Displays Your Data
- Customizing How vRealize Operations Manager Monitors Your Environment
- Defining Alerts in vRealize Operations Manager
- Object Relationship Hierarchies for Alert Definitions
- Alert Definition Best Practices
- Understanding Negative Symptoms for Alerts
- Create an Alert Definition for Department Objects
- Add Description and Base Object to Alert Definition
- Add a Virtual Machine CPU Usage Symptom to the Alert Definition
- Add a Host Memory Usage Symptom to the Alert Definition
- Add Recommendations to the Alert Definition
- Create a Custom Accounting Department Group
- Create a Policy for the Accounting Alert
- Configure Notifications for the Department Alert
- Create a Dashboard to Monitor Department Objects
- Defining Symptoms for Alerts
- Viewing Actions
- Defining Recommendations for Alert Definitions
- Creating and Managing Alert Notifications
- List of Outbound Plug-Ins
- Add Outbound Notification Plug-Ins
- Add a Standard Email Plug-In for Outbound Alerts
- Add a REST Plug-In for Outbound Alerts
- Add a Log File Plug-In for Outbound Alerts
- Add a Network Share Plug-In for vRealize Operations Manager Reports
- Add an SNMP Trap Plug-In for Outbound Alerts
- Add a Smarts Service Assurance Manager Notification Plug-In for Outbound Alerts
- Filtering Log File Outbound Messages With the TextFilter.xml File
- Configuring Notifications
- Defining Compliance Standards
- Operational Policies
- Managing and Administering Policies for vRealize Operations Manager
- Policy Decisions and Objectives
- Default Policy in vRealize Operations Manager
- Custom Policies
- Policies Provided with vRealize Operations Manager
- User Scenario: Create a Custom Operational Policy for a vSphere Production Environment
- User Scenario: Create an Operational Policy for Production vCenter Server Datastore Objects
- Create a Group Type for Your Datastore Objects
- Create an Object Group for Your Datastore Objects
- Create Your Policy and Select a Base Policy
- Override the Analysis Settings for the Datastore Objects
- Enable Disk Space Attributes for Datastore Objects
- Override Alert and Symptom Definitions for Datastore Objects
- Apply Your Datastore Policy to Your Datastore Objects Group
- Create a Dashboard for Disk Use of Your Datastore Objects
- Using the Monitoring Policy Workspace to Create and Modify Operational Policies
- Policy Workspace in vRealize Operations Manager
- Super Metrics in vRealize Operations Manager
- Customizing Icons
- Managing Objects in Your Environment
- Configuring Object Relationships
- Customizing How Endpoint Operations Management Monitors Operating Systems
- Modifying Global Settings
- Defining Alerts in vRealize Operations Manager
- Maintaining and Expanding vRealize Operations Manager
- Cluster and Node Maintenance
- Logging
- Passwords and Certificates
- How To Preserve Customized Content
- Backup and Restore
- OPS-CLI Command-Line Tool
- Index
6 In the following conguration les, use a text editor to replace all instances of the old IP address with
the new IP address.
n
/usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/data/roleState.properties.
n
/usr/lib/vmware-vcops/user/conf/gemfire.properties.
n
/usr/lib/vmware-vcops/user/conf/gemfire.locator.properties. This conguration le only runs
on the master node. Edit the locater parameter.
n
/usr/lib/vmware-vcops/user/conf/gemfire.native.properties.
n
/usr/lib/vmware-vcops/user/conf/persistence/persistence.properties.
7 Navigate to the /usr/lib/vmware-vcops/user/conf/cassandra/ directory, and edit the cassandra.yaml
le so that the seeds parameter points to the new IP address of the master node, and the
listen_address and broadcast_rpc_address point to the IP addresses of the data nodes.
8 Log in to the vRealize Operations Manager administration interface, and bring the cluster online.
Manual Backup Procedure Appears to Stall
When you run a backup job manually by using vSphere Data Protection, the progress of the job might reach
92% and stall. It appears as though the job has stopped running.
Problem
The task details in the Running tab of the Recent Tasks pane might show that the job has stopped running
when it reaches 92%. Often, the job might still be running in the background. The status of the backup job
can be veried in the vSphere Data Protection Appliance.
Solution
1 Use SSH to log in to vSphere Data Protection appliance.
2 Run mccli activity show to view a list of backup jobs and their status.
3 In the Client column, search for the ID of the backup job, and the corresponding virtual machines.
4 In the Status column, verify that the job is still running.
Chapter 4 Maintaining and Expanding vRealize Operations Manager
VMware, Inc. 139