Vrealize Operations Manager 60 Vapp Deploy Guide

8/9/2019 Vrealize Operations Manager 60 Vapp Deploy Guide

1/88

vRealize Operations Manager vAppDeployment and Configuration Guide

vRealize Operations Manager 6.0

This document supports the version of each product listed and

supports all subsequent versions until the document isreplaced by a new edition. To check for more recent editions

of this document, see http://www.vmware.com/support/pubs.

EN-001601-01
http://www.vmware.com/support/pubs


2/88

vRealize Operations Manager vApp Deployment and Configuration Guide

2 VMware, Inc.

You can find the most up-to-date technical documentation on the VMware Web site at:

http://www.vmware.com/support/

The VMware Web site also provides the latest product updates.

If you have comments about this documentation, submit your feedback to:

[email protected]

Copyright 2014 VMware, Inc. All rights reserved. Copyright and trademark information.

VMware, Inc.

3401 Hillview Ave.Palo Alto, CA 94304www.vmware.com
http://pubs.vmware.com/copyright-trademark.htmlmailto:[email protected]://www.vmware.com/support/


3/88

Contents

Updated Information 5

About vApp Deployment and Configuration 7

1 Preparing for vRealize Operations Manager Installation 9

About vRealize Operations Manager Virtual Application Installation 10

Complexity of Your Environment 11

About vRealize Operations Manager Nodes 13

Create a Node by Deploying an OVF 15

2 Creating the vRealize Operations Manager Master Node 19About the vRealize Operations Manager Master Node 19

Run the Setup Wizard to Create the Master Node 19

3 Scaling vRealize Operations Manager Out by Adding a Data Node 23

About vRealize Operations Manager Data Nodes 23

Run the Setup Wizard to Add a Data Node 23

4 Adding High Availability to vRealize Operations Manager 25

About vRealize Operations Manager High Availability 25

Run the Setup Wizard to Add a Master Replica Node 25

5 Gathering More Data by Adding a vRealize Operations Manager Remote

Collector Node 27About vRealize Operations Manager Remote Collector Nodes 27

Run the Setup Wizard to Create a Remote Collector Node 27

6 Continuing With a New vRealize Operations Manager Installation 29

About New vRealize Operations Manager Installations 29

Log In and Continue with a New Installation 29

7 Importing From a Previous Product Version 31About vRealize Operations Manager Migrations 31

Log In and Migratea Previous Installation 31

8 vRealize Operations Manager Post-Installation Considerations 35

Secure the vRealize Operations Manager Console 35

Change the vRealize Operations Manager Administrator Password 36

Add a Custom SSL Certificate to vRealize Operations Manager 36

Remove a vRealize Operations Manager Node 36

Remove High Availability 37

VMware, Inc. 3


4/88

Configuring Solutions and Adapters in vRealize Operations Manager 37

Migrating a vCenter Operations Manager Deployment into this Version 70

Index 85


4 VMware, Inc.


5/88

Updated Information

This vRealize Operations Manager vApp Deployment and Configuration Guideis updated with each release of the

product or when necessary.

This table provides the update history of the vRealize Operations Manager vApp Deployment and Configuration

Guide.

Revision Description

EN-001601-01 n Added statement to not make cluster node changes while the cluster is starting, in Run the SetupWizard to Create the Master Node,on page 19 and similar topics.

n Added link to video in About vRealize Operations Manager High Availability,on page 25.

n Added instructions for installing a custom certificate. See Add a Custom SSL Certificate to vRealizeOperations Manager,on page 36.

n Added additional supported URL formats for the adapter configuration in Add a vCenter AdapterInstance in vRealize Operations Manager,on page 41.

EN-001601-00 Initial release.

VMware, Inc. 5


6/88


6 VMware, Inc.


7/88

About vApp Deployment and Configuration

The vRealize Operations Manager vApp Deployment and Configuration Guide provides information about

deploying the VMware

vRealize Operations Manager virtual application, including how to create and

configure the vRealize Operations Manager cluster.

The vRealize Operations Manager installation process consists of deploying the

vRealize Operations Manager virtual application once for each cluster node, and accessing the product tofinish setting up the application.

Intended Audience

This information is intended for anyone who wants to install and configure vRealize Operations Manager

by using a virtual application deployment. The information is written for experienced virtual machine

administrators who are familiar with enterprise management applications and datacenter operations.

VMware Technical Publications Glossary

VMware Technical Publications provides a glossary of terms that might be unfamiliar to you. For definitions

of terms as they are used in VMware technical documentation, go tohttp://www.vmware.com/support/pubs.

VMware, Inc. 7
http://www.vmware.com/support/pubs


8/88


8 VMware, Inc.


9/88

Preparing for

vRealize Operations ManagerInstallation 1

You prepare for vRealize Operations Manager installation by evaluating your environment and deploying

enough vRealize Operations Manager cluster nodes to support how you want to use the product.

This chapter includes the following topics:

nAbout vRealize Operations Manager Virtual Application Installation,on page 10

n Complexity of Your Environment,on page 11

n About vRealize Operations Manager Nodes,on page 13

n Create a Node by Deploying an OVF,on page 15

VMware, Inc. 9


10/88

About vRealize Operations Manager Virtual Application Installation

The vRealize Operations Manager virtual application installation process consists of deploying the

vRealize Operations Manager OVF once for each cluster node, accessing the product to set up cluster nodes

according to their role, and logging in to configure the installation.

Figure 1

1. vRealize Operations Manager Installation

Start

Deploy OVF to create master node.(optional) Deploy OVFs for master replica, data,

or remote collector nodes

Run master node setup

(optional)Enable master replica

(optional)Run data nodes setup

(optional)Run remote collector

nodes setup

First-time login to the product

First-time login to the product

Licensing

Select source

Import from source

Monitor your environment

Select, license,and upload

Configure new installation

Licensing

Add solutions

Configure added solutions

Add monitoring policies


10 VMware, Inc.


11/88

Complexity of Your Environment

When you deploy vRealize Operations Manager, the number and nature of the resources that you want to

monitor might be complex enough to recommend a Professional Services engagement.

Complexity LevelsEvery enterprise is different in terms of the systems that are present and the level of experience of

deployment personnel. The following table presents a color-coded guide to help you determine where you

are on the complexity scale.

n Green

Your installation only includes conditions that most users can understand and work with, without

assistance. Continue your deployment.

n Yellow

Your installation includes conditions that might justify help with your deployment, depending on your

level of experience. Consult your account representative before proceeding, and discuss using

Professional Services.

n Red

Your installation includes conditions that strongly recommend a Professional Services engagement.

Consult your account representative before proceeding, anddiscuss using Professional Services.

Note that these color-coded levels are not firm rules. Your product experience, which increases as you work

with vRealize Operations Manager and in partnership with Professional Services, must be taken into

account when deploying vRealize Operations Manager.

Table 11. Effect of Deployment Conditions on Complexity

Complexity Level

Current or New Deployment

Condition Additional Notes

Green You run only one vCenter OperationsManager deployment.

Lone instances are usually easy to re-create invRealize Operations Manager.

Green Your deployment includes amanagement pack that is listed asGreen according to the compatibilityguide on the VMware SolutionsExchangeWeb site.

The compatibility guide indicateswhether the supported managementpack for vRealize Operations Manageris a compatible 5.x one or a new onedesigned for this release. In somecases, both might work but producedifferent results. Regardless, usersmight need help in adjusting theirconfiguration so that associated data,dashboards, alerts, and so on appear asexpected.

Note that the terms solution,management pack, and adapterare usedsomewhat interchangeably.

Yellow You run multiple instances ofvCenter Operations Manager.

Multiple instances are typically used toaddress scaling or operator usepatterns.

Yellow You configured vCenter OperationsManager to retain more data byincreasing the default six months ofhistory or by increasing the pollingfrequency.

A very large data set dramaticallyincreases the time needed formigration and makes it harder toproperly size and configure thedeployment.

Chapter 1 Preparing for vRealize Operations Manager Installation

VMware, Inc. 11
https://solutionexchange.vmware.com/https://solutionexchange.vmware.com/https://solutionexchange.vmware.com/https://solutionexchange.vmware.com/


12/88

Table 11. Effect of Deployment Conditions on Complexity (Continued)

Complexity Level



Yellow Your deployment includes amanagement pack that is listed asYellow according to the compatibilityguide on the VMware Solutions

ExchangeWeb site.

The compatibility guide indicateswhether the supported managementpack for vRealize Operations Manageris a compatible 5.x one or a new one

designed for this release. In somecases, both might work but producedifferent results. Regardless, usersmight need help in adjusting theirconfiguration so that associated data,dashboards, alerts, and so on appear asexpected.

Yellow You are deployingvRealize Operations Manager remotecollector nodes.

Remote collector nodes gather data butleave the storage and processing of thedata to the analytics cluster.

Yellow You are deploying a multiple-nodevRealize Operations Manager cluster.

Multiple nodes are typically used forscaling out the monitoring capabilityof vRealize Operations Manager.

Yellow Your current vCenter OperationsManager 5.x instance includes aLinux or Windows baseddeployment.

Linux and Windows deployments arenot as common as vApp deploymentsand often need special consideration.

Yellow Your newvRealize Operations Managerinstance will include a Linux orWindows based deployment.

Linux and Windows deployments arenot as common as vApp deploymentsand often need special consideration.

Yellow Your vRealize Operations Managerinstance will use high availability(HA).

High availability and its node failovercapability is a unique multiple-nodefeature that you might want additionalhelp in understanding.

Yellow You want help in understanding thenew or changed features invRealize Operations Manager andhow to use them in yourenvironment.

vRealize Operations Manager isdifferent than vCenter OperationsManager in areas such as policies,alerts, compliance, custom reporting,or badges. In addition,vRealize Operations Manager uses oneconsolidated interface.

Red You run multiple instances ofvCenter Operations Manager, whereat least one includes virtual desktopinfrastructure (VDI).

Multiple instances are typically used toaddress scaling, operator use patterns,or because separate VDI (V4Vmonitoring) and non-VDI instances areneeded.

Red Your deployment includes amanagement pack that is listed as

Red according to the compatibilityguide on the VMware SolutionsExchangeWeb site.

The compatibility guide indicateswhether the supported management

pack for vRealize Operations Manageris a compatible 5.x one or a new onedesigned for this release. In somecases, both might work but producedifferent results. Regardless, usersmight need help in adjusting theirconfiguration so that associated data,dashboards, alerts, and so on appear asexpected.

Red You are deploying multiplevRealize Operations Managerclusters.

Multiple clusters are typically used toisolate business operations orfunctions.


12 VMware, Inc.
https://solutionexchange.vmware.com/https://solutionexchange.vmware.com/https://solutionexchange.vmware.com/https://solutionexchange.vmware.com/


13/88

Table 11. Effect of Deployment Conditions on Complexity (Continued)

Complexity Level



Red Your current vCenter OperationsManager 5.x deployment required aProfessional Services engagement toinstall it.

If your environment was complexenough to justify a ProfessionalServices engagement in version 5.x, itis possible that the same conditions

still apply and might warrant a similarengagement for this version.

Red Professional Services customizedyour vCenter Operations Manager5.x deployment. Examples ofcustomization include specialintegrations, scripting, nonstandardconfigurations, multiple levelalerting, or custom reporting.

If your environment was complexenough to justify a ProfessionalServices engagement in version 5.x, itis possible that the same conditionsstill apply and might warrant a similarengagement for this version.

About vRealize Operations Manager Nodes

All vRealize Operations Manager clusters consist of a master node, an optional replica node for highavailability, optional data nodes, and optional remote collector nodes.

When you install vRealize Operations Manager, you use a vRealize Operations Manager OVF deployment

to create role-less nodes. After the nodes are created and have their names and IP addresses, you use an

administration interface to configure them according to their role.

You can create role-less nodes all at once or as needed. A common as-needed practice might be to add nodes

to scale out vRealize Operations Manager to monitor an environment as the environment grows larger.

Master Node The initial, required node in the cluster. All other nodes are managed by the

master node.

In a single-node installation, the master node must also perform data

collection and analysis because it is the sole node, and the only place wherevRealize Operations Manager adapters are installed.

Data Node In larger deployments, additional data nodes have adapters installed to

perform collection and analysis.

Larger deployments usually include adapters only on data nodes, not on the

master node or replica node.

Replica Node To enable high availability (HA), the cluster requires that you convert a data

node into a replica of the master node.

Remote Collector Node Distributed deployments might require a remote collector node that can

navigate firewalls, interface with a remote data source, reduce bandwidth

across data centers, or reduce the load on the vRealize Operations Manager

analytics cluster. Remote collectors only gather objects for the inventory,

without storing data or performing analysis. In addition, remote collector

nodes may be installed on a different operating system than the rest of the

cluster nodes.

NOTE The main part of the cluster that does not include remote collector

nodes is informally referred to as the analytics cluster.

Any node except a remote collector node can access the vRealize Operations Manager user interface when

you point a browser to the IP address or fully qualified domain name (FQDN) of the node.


VMware, Inc. 13


14/88

vRealize Operations Manager Node Requirements

When you create the nodes of the vRealize Operations Manager cluster, you address certain requirements at

deployment or installation time, before you log in to configure the role for any nodes, including the master

node.

General Requirements

n Deployment Type. Except for the remote collector, all cluster nodes must be the same kind of

deployment: vApp, Linux, or Windows. Do not mix vApp, Linux, and Windows nodes in the same

analytics cluster.

When you add a remote collector of a different deployment type, only the following combinations are

supported:

n vApp analytics cluster and Windows remote collector

n Linux analytics cluster and Windows remote collector

n Uniform Sizing. When you create nodes; CPU, memory, and disk sizing must be identical among nodes

in the analytics cluster. Data nodes, master node, and replica node must be the same size. Remote

collector nodes may be of different sizes.

Networking Requirements

n You must be able to successfully reverse-DNS all nodes to their fully qualified domain name (FQDN),

currently the node hostname. Nodes deployed by OVF have their hostnames set to this retrieved

FQDN.

n The master node and replica node must be addressed by static IP address or FQDN with a static IP

address. Other nodes can use dynamic host control protocol (DHCP).

n All nodes must be bidirectionally routable by IP address or FQDN.

n Nodes in the analytics cluster must not be separated by network address translation (NAT), load

balancer, firewall, or a proxy that inhibits bidirectional communication by IP address or FQDN.

n Multiple nodes in the analytics cluster may not have the same hostname.

Sizing the vRealize Operations Manager Cluster

The resources needed for vRealize Operations Manager depend on how large of an environment you expect

to monitor and analyze, how many metrics you plan to collect, and how long you need to store the data.

It is difficult to broadly predict the CPU, memory, and disk requirements that will meet the needs of a

particular environment. There are many variables, such as the number and type of resources collected,

which includes the number and type of adapters installed, the presence of HA, the duration of data

retention, and the quantity of specific data points of interest, such as symptoms, changes, and so on.

VMware expects vRealize Operations Manager sizing information to evolve, and maintains the followingKnowledge Base article so that sizing calculations can be adjusted to adapt to usage data.

Knowledge Base article 2093783

The Knowledge Base article includes overall maximums, plus spreadsheet calculators in which you enter the

number of objects and metrics that you expect to monitor. To obtain the numbers, some users take the

following high-level approach, which uses vRealize Operations Manager itself.

1 Review this guide to understand how to deploy and configure a vRealize Operations Manager node.

2 Deploy a temporary vRealize Operations Manager node.

3 Configure one or more adapters, and allow the temporary node to collect overnight.


14 VMware, Inc.
http://kb.vmware.com/kb/2093783


15/88

4 Access the Cluster Management page on the temporary node.

5 Using the Adapter Instances list in the lower portion of the display as a reference, enter object and

metric totals of the different adapter types into the sizing spreadsheet from Knowledge Base article

2093783.

6 Deploy the vRealize Operations Manager cluster based on the spreadsheet sizing recommendation. You

can build the cluster by adding resources and data nodes to the temporary node or by starting over.

If you have a large number of adapters, you might need to reset and repeat the process on the temporary

node until you have all the totals you need. The temporary node will not have enough capacity to

simultaneously run every connection from a large enterprise.

Another approach to sizing is through self monitoring. Deploy the cluster based on your best estimate, but

create an alert for when capacity falls below a threshold, one that allows enough time to add nodes or disk

to the cluster. You also have the option to create an email notification when thresholds are passed.

During internal testing, a single-node vApp deployment of vRealize Operations Manager that monitored

8,000 virtual machines ran out of disk storage within one week.

Add Disk Space to a vRealize Operations Manager vApp Node

You add disk to vRealize Operations Manager vApp nodes when space for storing the collected data runslow.

Prerequisites

n Use the vRealize Operations Manager administration interface to take the node offline.

n Verify that you are connected to a vCenter Server system with a vSphere client, and log in to the

vSphere client.

Procedure

1 Shut down the virtual machine for the node.

2 Edit the hardware settings of the virtual machine, and do one of the following:

n Increase the size of Hard disk 2.

You cannot increase the size when the virtual machine has snapshots.

n Add another disk.

3 Power on the virtual machine for the node.

During the power-on process, the virtual machine expands the vRealize Operations Manager data partition.

Create a Node by Deploying an OVF

vRealize Operations Manager consists of one or more nodes, in a cluster. To create nodes, you use the

vSphere client to download and deploy the vRealize Operations Manager virtual machine, once for eachcluster node.

Do not deploy vRealize Operations from an ESXi host. Deploy only from vCenter Server.

For effective backup, deploy a high availability replica node on different hardware from the master node.

Prerequisites

n Verify that you have permissions to deploy OVF templates to the inventory.

n If the ESXi host is part of a cluster, enable DRS in the cluster. If an ESXi host belongs to a non-DRS

cluster, all resource pool functions are disabled.


VMware, Inc. 15
http://kb.vmware.com/kb/2093783http://kb.vmware.com/kb/2093783


16/88

n From your network administrator, reserve a static IP address for the virtual machine, and know the

associated domain name server, default gateway, and network mask values.

n Download the vRealize Operations Manager .ovafile to a location that is accessible to the vSphere

client.

n If you download the virtual machine and the file extension is .tar, change the file extension to .ova.

n Verify that you are connected to a vCenter Server system with a vSphere client, and log in to thevSphere client.

Procedure

1 Select File > Deploy OVF Template.

2 Enter the path to the vRealize Operations Manager .ovafile.

3 Follow the prompts until you are asked for the node name.

4 Enter a node name. Examples might include Ops-Masteror Ops-Data.

Use a different name for each vRealize Operations Manager node.

5 Follow the prompts until you are asked to select a configuration size.

6 For the configuration size, select any size option.

Default disk space is allocated regardless of which size you select. If you need additional space to

accommodate the expected data, add more disk after deploying the vApp.

7 Follow the prompts until you are asked to select the disk format.

Option Description

Thick Provision Lazy Zeroed Creates a virtual disk in a default thick format.

Thick Provision Eager Zeroed Creates a type of thick virtual disk that supports clustering features suchas Fault Tolerance. Thick provisioned eager-zeroed format can improveperformance depending on the underlying storage subsystem.

Select the thick provisioned eager-zero option when possible.

Thin Provision Creates a disk in thin format. Use this format to save storage space.

Snapshots can negatively affect the performance of a virtual machine and typically result in a 2530

percent degradation for the vRealize Operations Manager workload. Do not use snapshots.

8 Click Next.

9 From the drop-down menu, select a Destination Network, for example, Network 1 = TEST, and click

Next.

10 In Properties, under Application, Timezone Setting, select your time zone or leave the default of UTC.

Use UTC if cluster nodes will be distributed across different time zones.

11 Under Networking Properties, leave the entries blank for DHCP, or fill in the default gateway, domainname server, static IP address, and network mask values.

The master node and replica node require a static IP. A data node or remote collector node may use

DHCP or static IP.

12 Click Next.

13 Review the settings and click Finish.

14 If you are creating a multiple-node vRealize Operations Manager cluster, repeat Step 1through Step 13

to deploy each node.


16 VMware, Inc.


17/88

What to do next

Use a Web browser client to configure a newly added node as the vRealize Operations Manager master

node, a data node, a high availability master replica node, or a remote collector node. The master node is

required first.

CAUTION For security, do not access vRealize Operations Manager from untrusted or unpatched clients, or

from clients using browser extensions.


VMware, Inc. 17


18/88


18 VMware, Inc.


19/88

Creating the

vRealize Operations Manager MasterNode 2

All vRealize Operations Manager installations require a master node.


n About the vRealize Operations Manager Master Node,on page 19

n Run the Setup Wizard to Create the Master Node,on page 19

About the vRealize Operations Manager Master Node

The master node is the required, initial node in your vRealize Operations Manager cluster.

In single-node clusters, administration and data are on the same master node. A multiple-node cluster

includes one master node and one or more data nodes. In addition, there might be remote collector nodes,

and there might be one replica node used for high availability.

The master node performs administration for the cluster and must be online before you configure any new

nodes. In addition, the master node must be online before other nodes are brought online. For example, if

the entire cluster were offline for any reason, you would bring the master node online first.

Run the Setup Wizard to Create the Master Node

All vRealize Operations Manager installations require a master node. With a single node cluster,

administration and data functions are on the same master node. A multiple-node

vRealize Operations Manager cluster contains one master node and one or more nodes for handling

additional data.

Prerequisites

n Create a node by deploying the vRealize Operations Manager vApp.

n After it is deployed, note the fully qualified domain name (FQDN) or IP address of the node.

Procedure

1 Navigate to the name or IP address of the node that will be the master node of

vRealize Operations Manager.

The setup wizard appears, and you do not need to log in to vRealize Operations Manager.

2 Click New Cluster.

3 Click Next.

VMware, Inc. 19


20/88

4 Enter and confirm a password for the admin user account, and click Next.

Passwords require a minimum of 8 characters, one uppercase letter, one lowercase letter, one digit, and

one special character.

The user account name is admin by default and cannot be changed.

5 Select whether to use the certificate included with vRealize Operations Manager or to install one of

your own.

a To use your own certificate, click Browse, locate the certificate file, and click Opento load the file

in the Certificate text box.

The file extension of the certificate file that you want to import does not matter. However the

certificate file must contain both a valid private key and a valid certificate chain, and cannot be self-

signed.

b Enter the certificate password and alias name.

c Click Upload.

d Review the information detected about your certificate to verify that it conforms to the

requirements for certificates.

6 Click Next.

7 Enter a name for the master node.

For example: Ops-Master

8 Enter the URL or IP address for the Network Time Protocol (NTP) server with which the cluster will

synchronize.

For example: time.nist.gov

9 Click Add.

Leave the NTP blank to have vRealize Operations Manager manage its own synchronization by having

all nodes synchronize with the master node and replica node.

10 Click Next, and click Finish.

The administration interface appears, and it takes a moment for vRealize Operations Manager to finish

adding the master node.

What to do next

n (Optional) Create data nodes.

n (Optional) Create remote collector nodes.

n Click Start vRealize Operations Managerto start the cluster, and log in to finish configuring the

product.

The cluster might take from 10 to 30 minutes to start, depending on the size of your cluster and nodes.

Do not make changes or perform any actions on cluster nodes while the cluster is starting.


20 VMware, Inc.


21/88

Requirements for Custom vRealize Operations Manager SSL Certificates

By default, vRealize Operations Manager installs its own SSL certificate. The included certificate generates

security warnings when you connect to the vRealize Operations Manager monitoring page. If you do not

want to use the included certificate, you can use your own SSL certificate.

Custom Certificate Requirements

A custom SSL certificate must conform to the following requirements. Using a custom certificate is optional

and does not affect vRealize Operations Manager features.

n The certificate file contains both a valid private key and a valid certificate chain.

n The private key is generated by the RSA or the DSA algorithm.

n The private key is not encrypted by a pass phrase.

n If the certificate is signed by a chain of other certificates, all other certificates must be included in the

certificate file that you plan to import

n All the certificates and the private key that are included in the certificate file must be PEM-encoded.

vRealize Operations Manager does not support DER-encoded certificates and private keys.

n All the certificates and the private key that are included in the certificate file must be in the PEM format.

vRealize Operations Manager does not support certificates in the PFX, PKCS12, PKCS7, or other

formats.

Chapter 2 Creating the vRealize Operations Manager Master Node

VMware, Inc. 21


22/88


22 VMware, Inc.


23/88

Scaling vRealize Operations ManagerOut by Adding a Data Node 3

You can deploy and configure additional nodes so that vRealize Operations Manager can support larger

environments.


nAbout vRealize Operations Manager Data Nodes,on page 23

n Run the Setup Wizard to Add a Data Node,on page 23

About vRealize Operations Manager Data Nodes

Data nodes are the additional cluster nodes that allow you to scale out vRealize Operations Manager to

monitor larger environments.

A data node always shares the load of performing vRealize Operations Manager analysis and might also

have a solution adapter installed to perform collection and data storage from the environment. You must

have a master node before you add data nodes.

You can dynamically scale out vRealize Operations Manager by adding data nodes without stopping the

vRealize Operations Manager cluster. When you scale out the cluster by 25% or more, you should restart thecluster to allow vRealize Operations Manager to update its storage size, and you might notice a decrease in

performance until you restart. A maintenance interval provides a good opportunity to restart the

vRealize Operations Manager cluster.

In addition, the product administration options include an option to rebalance the cluster, which can be

done without restarting. Rebalancing adjusts the vRealize Operations Manager workload across the cluster

nodes.

Run the Setup Wizard to Add a Data Node

Larger environments with multiple-node vRealize Operations Manager clusters contain one master node

and one or more data nodes for additional data collection, storage, processing, and analysis.

Prerequisites

n Create nodes by deploying the vRealize Operations Manager vApp.

n Create and configure the master node.

n Note the fully qualified domain name (FQDN) or IP address of the master node.

Procedure

1 In a Web browser, navigate to the name or IP address of the node that will become the data node.


VMware, Inc. 23


24/88

2 Click Expand Existing Cluster.

3 Click Next.

4 Enter a name for the node (for example, Data-1).

5 From the Node Type drop-down, select Data.

6 Enter the FQDN or IP address of the master node and click Validate.

7 Click Accept this certificateand click Next.

If necessary, locate the certificate on the master node and verify the thumbprint.

8 Verify the vRealize Operations Manager administrator username of admin.

9 Enter the vRealize Operations Manager administrator password.

Alternatively, instead of a password, type a pass-phrase that you were given by your

vRealize Operations Manager administrator.


The administration interface appears, and it takes a moment for vRealize Operations Manager to finish

adding the data node.

What to do next

n (Optional) Create more data nodes.

n (Optional) Create a high availability master replica node.



product.




24 VMware, Inc.


25/88

Adding High Availability tovRealize Operations Manager 4

You can dedicate one vRealize Operations Manager cluster node to serve as a replica node for the

vRealize Operations Manager master node.


nAbout vRealize Operations Manager High Availability,on page 25

n Run the Setup Wizard to Add a Master Replica Node,on page 25

About vRealize Operations Manager High Availability

vRealize Operations Manager supports high availability (HA) by enabling a replica node for the

vRealize Operations Manager master node.

When present, an HA replica node can take over the functions that a master node provides. When a problem

occurs with the master node, failover to the replica node is automatic and requires only two to three minutes

of vRealize Operations Manager downtime. Data stored on the master node is always 100% backed up on

the replica node. In addition, with HA enabled, the cluster can survive the loss of a data node without losing

any data.

To enable HA, you must have another node deployed in addition to the master node. When you deploy

nodes as virtual machines, deploy the replica node on different hardware than the master node so that

backup is physically redundant.

Install vRealize Operations Manager with High Availability

(http://link.brightcove.com/services/player/bcpid2296383276001?

bctid=ref:video_install_vrom_with_ha)

Run the Setup Wizard to Add a Master Replica Node

You can convert a vRealize Operations Manager data node to a replica of the master node, which adds high

availability (HA) for vRealize Operations Manager.

NOTE If the cluster is running, enabling HA restarts the cluster.

If you convert a data node that is already in use for data collection and analysis, adapters and data

connections that were provided through that data node fail over to other data nodes.

You may add HA to the vRealize Operations Manager cluster at installation time or after

vRealize Operations Manager is up and running. Adding HA at installation is less intrusive because the

cluster has not yet started.

Prerequisites


VMware, Inc. 25
http://link.brightcove.com/services/player/bcpid2296383276001?bctid=ref:video_install_vrom_with_hahttp://link.brightcove.com/services/player/bcpid2296383276001?bctid=ref:video_install_vrom_with_hahttp://link.brightcove.com/services/player/bcpid2296383276001?bctid=ref:video_install_vrom_with_ha


26/88

n Create and configure the master node.

n Create and configure a data node with a static IP address.


Procedure

1 In a Web browser, navigate to the master node administration interface.https://master-node-name-or-ip-address/admin

2 Enter the vRealize Operations Manager administrator username of admin.

3 Enter the vRealize Operations Manager administrator password and click Log In.

4 Under High Availability, click Enable.

5 Select a data node to serve as the replica for the master node.

6 Select the Enable High Availability for this clusteroption, and click OK.

If the cluster was online, the administration interface displays progress as vRealize Operations Manager

configures, synchronizes, and rebalances the cluster for HA.

What to do next




product.




26 VMware, Inc.


27/88

Gathering More Data by Adding a

vRealize Operations Manager RemoteCollector Node 5

You deploy and configure remote collector nodes so that vRealize Operations Manager can add to its

inventory of objects to monitor without increasing the processing load on vRealize Operations Manager

analytics.


n About vRealize Operations Manager Remote Collector Nodes,on page 27

n Run the Setup Wizard to Create a Remote Collector Node,on page 27

About vRealize Operations Manager Remote Collector Nodes

A remote collector node is an additional cluster node that allows vRealize Operations Manager to gather

more objects into its inventory for monitoring. Unlike data nodes, remote collector nodes only include the

collector role of vRealize Operations Manager, without storing data or processing any analytics functions.

A remote collector node is usually deployed to navigate firewalls, reduce bandwidth across data centers,

connect to remote data sources, or reduce the load on the vRealize Operations Manager analytics cluster.

You must have at least a master node before adding remote collector nodes.

Run the Setup Wizard to Create a Remote Collector Node

In distributed vRealize Operations Manager environments, remote collector nodes increase the inventory of

objects that you can monitor without increasing the load on vRealize Operations Manager in terms of data

storage, processing, or analysis.

Prerequisites


During vApp deployment, select a remote collector size option.

nCreate and configure the master node.


Procedure

1 In a Web browser, navigate to the name or IP address of the deployed OVF that will become the remote

collector node.


2 Click Expand Existing Cluster.

3 Click Next.

VMware, Inc. 27


28/88

4 Enter a name for the node, for example, Remote-1.

5 From the Node Typedrop-down menu, select Remote Collector.

6 Enter the FQDN or IP address of the master node and click Validate.

7 Click Accept this certificateand click Next.

If necessary, locate the certificate on the master node and verify the thumbprint.

8 Verify the vRealize Operations Manager administrator username of admin.

9 Enter the vRealize Operations Manager administrator password.

Alternatively, instead of a password, type a passphrase that you were given by the

vRealize Operations Manager administrator.


The administration interface appears, and it takes several minutes for vRealize Operations Manager to

finish adding the remote collector node.

What to do next

n(Optional) Create more remote collector nodes.


n (Optional) Create a high availability master replica node.


product.




28 VMware, Inc.


29/88

Continuing With a New

vRealize Operations ManagerInstallation 6

After you deploy the vRealize Operations Manager nodes and complete the initial setup, you continue with

installation by logging in for the first time and configuring a few settings.


nAbout New vRealize Operations Manager Installations,on page 29

n Log In and Continue with a New Installation,on page 29

About New vRealize Operations Manager Installations

A new vRealize Operations Manager installation requires that you deploy and configure nodes. Then, you

add solutions for the kinds of resources to monitor and manage.

After you add solutions, you configure them in the product and add monitoring policies that gather the

kind of data that you want. At any future point, a new installation can also have part or all of an

environment that is monitored by a previous vCenter Operations Manager instance migrated to it.

Log In and Continue with a New InstallationTo finish a new vRealize Operations Manager installation, you log in and complete a one-time process to

license the product and add solutions for the kinds of resources to monitor and manage.

Prerequisites

n Create and configure the new cluster of vRealize Operations Manager nodes.

n Click the Start vRealize Operations Managerbutton to start the cluster.

Procedure

1 In a Web browser, navigate to the name or IP address of the master node.

If you configured nodes and started the cluster, the product takes you to the login page.

2 Enter the username adminand the password that you defined when you configured the master node,

and click Login.

Because this is the first time logging in to the product, a one-time wizard appears.

3 Click New Environmentand click Next.

4 Read and accept the End User License Agreement, and click Next.

VMware, Inc. 29


30/88


31/88

Importing From a Previous ProductVersion 7

After you deploy the vRealize Operations Manager nodes and complete the initial setup, you can import

from an earlier vCenter Operations Manager deployment by logging in for the first time and configuring a

few settings.

You can also migrate the data later, after the new installation of vRealize Operations Manager is established

or in production. Migrating and importing are synonymous.


n About vRealize Operations Manager Migrations,on page 31

n Log In and Migrate a Previous Installation,on page 31

About vRealize Operations Manager Migrations

By importing data, this version of vRealize Operations Manager can assume the monitoring of an earlier

vCenter Operations Manager deployment.

Migration occurs side by side, and while the migration is in progress, the source continues to monitor

resources. After migration, both target and source are monitoring the resources. When you turn off theearlier deployment, monitoring of the inventory and data is done solely by the new version of

vRealize Operations Manager. Performing the entire process is known as a migration-based upgrade.

A vRealize Operations Manager migration requires that you deploy and configure a target cluster of new

nodes in the same way as you would for a new vRealize Operations Managerinstallation. Then, you

perform a one-time connection to your previous vCenter Operations Manager source deployment to import

the configuration from that environment.

Log In and Migrate a Previous Installation

To migrate a previous vCenter Operations Manager installation, you log in to the target and complete a one-

time wizard to license the product and import the source to your new deployment.

Prerequisites

Source Prerequisites

n Review About vRealize Operations Manager Migrations,on page 70 through Best Practices when

Migrating to vRealize Operations Manager,on page 79.

n Update the source vCenter Operations Manager installation to version 5.8.1 or later.

n Disable dynamic thresholding (DT).

n Verify that the source is not collecting from a vCenter Server that is already being monitored by the

target.

VMware, Inc. 31


32/88

n Verify that the disk that contains the vCenter Operations Manager log directory has free space.

Migration requires approximately 2 GB free log space for every 20,000 resources, 1 TB of FSDB data,

and run time history of 1 year.

n Disable alerts so that migrated notifications do not fire immediately.

n When two vCenter Operations Manager sources will be migrated, and both collect from the same

vCenter Server, verify that one source connects to the vCenter Server using the vCenter Server IP

address, and the other source connects using FQDN.

n Know the names and IP addresses of the source machines.

n Know the administrator username and password of the source machines.

n For sources that use Oracle or SQL Server for the database, verify that a minimum of 10 idle

connections are available.

n For vApp sources, verify that the vSphere UI is up and running.

n For Linux and Windows sources, verify that the Custom UI is up and running.

n For Linux and Windows sources, verify that the source has a minimum of 1 GB of free memory.

n For Linux and Windows sources, verify that the outbound port on the source is open so that data can be

transferred to the target. The default port is 6061.

n For Windows sources, verify that HTTPS is enabled.

n For Windows sources, verify that vCenter Operations Manager is installed under a folder path that

does not contain spaces.

Target Prerequisites

n Verify that network connection speed between the target and source is 100 mbps minimum.

n If the target has high availability (HA) enabled, temporarily disable HA.

n Take a target snapshot in case the migration does not produce the result that you want, and you need to

revert the target.

n Increase the data retention time to match the setting from the source.

n To avoid a large number of immediate notifications, temporarily disable notifications.

n Synchronize the system time setting on the target and all sources. The time zone does not need to be

synchronized.

n If, after starting the Import Data wizard, the wizard reports a shortage, add CPU, memory, and disk

before proceeding.

n If, after starting the Import Data wizard, the wizard reports any missing adapters, install the adapters

before proceeding.

Procedure

1 In a Web browser, navigate to the FQDN or IP address of the master node of the

vRealize Operations Manager target.

If you configured nodes and started the cluster, the product takes you to the login page.

2 Enter the username adminand the password that you defined when configuring the master node, and

click Login.

Because this is the first time logging in to the product, a one-time wizard appears.

3 Click Import Environmentand click Next.

4 Read and accept the End User License Agreement, and click Next.


32 VMware, Inc.


33/88

5 Enter your product key, or select the option to run vRealize Operations Manager in evaluation mode.

vRealize Operations Manager does not license managed objects like vSphere does, so there is no object

count when licensing the product.

6 If you entered a product key, click Validate License Key.

7 Click Next.

8 Enter the fully qualified domain name (FQDN) or IP address of the source from which you want to

import.

For a vApp deployment, the source must be a vCenter Operations Manager UI server, not an analytics

server.

9 Enter the admin password for the source.

10 Click Add Source.

vRealize Operations Manager finds and loads the security certificate for the source.

11 Select Accept this certificateand click OK.

vRealize Operations Manager adds the source to the list of sources from which it will import, and

calculates the amount of resources that the target must have for the import to succeed. If the target doesnot have enough resources, you must install more disk or data nodes before proceeding.

12 For each source in the list, use the drop menu to select the Migration Mode.

Migration mode allows you to exclude historical data when migrating, because migrating the data

significantly increases migration time as well as the free space needed on the target.

13 Add more sources or click Next.

A list of solutions appears, which reveals any that are present on sources but missing from the target

deployment.

14 If the source has an adapter installed that is missing from the target, click Add Solutionto add the

adapter to the target.

The steps to add a solution adapter are the same during migration as when you add a new solution.

15 After adding solutions, click Next.

16 To start the migration import, click Finish.

The wizard closes, and you can monitor the progress of the migration.

What to do next

While an import is in progress, do not make changes to the source inventory or resources.

The import process might take many hours to complete, especially if you chose to migrate historical data.

The number of resources, number of metrics, length of history, and size of the FSDB all contribute to the

time needed for migration. During internal testing, an inventory of 13,000 resources with 2.5 years of history

took about 44 hours to migrate. A guideline of 1 hour per 10 GB of FSDB data is a good starting point but

might be influenced by network performance or other factors.

Multiple sources are migrated in sequence. If one source migration fails, the migration continues with the

next source. In addition, you can stop a migration at any time.

After the import finishes, use vRealize Operations Manager to monitor the newly imported resources.

Eventually, you might also want to turn off your earlier source vCenter Operations Manager deployment.

Chapter 7 Importing From a Previous Product Version

VMware, Inc. 33


34/88


34 VMware, Inc.


35/88

vRealize Operations Manager Post-Installation Considerations 8

After you install or migrate vRealize Operations Manager, consider post-installation tasks that might need

your attention.


nSecure the vRealize Operations Manager Console,on page 35

n Change the vRealize Operations Manager Administrator Password,on page 36

n Add a Custom SSL Certificate to vRealize Operations Manager,on page 36

n Remove a vRealize Operations Manager Node,on page 36

n Remove High Availability,on page 37

n Configuring Solutions and Adapters in vRealize Operations Manager,on page 37

n Migrating a vCenter Operations Manager Deployment into this Version,on page 70

Secure the vRealize Operations Manager Console

After you install vRealize Operations Manager, you secure the console of each node in the cluster by loggingin for the first time.

Procedure

1 Locate the node console in vCenter or by direct access. In vCenter, use Alt+F1 to access the login

prompt.

For security, vRealize Operations Manager remote terminal sessions are disabled by default.

2 Log in as root.

vRealize Operations Manager prevents you from accessing the command prompt until you create a root

password.

3 When prompted for a password, press Enter.

4 When prompted for the old password, press Enter.

5 When prompted for the new password, enter the root password that you want, and note it for future

reference.

6 Re-enter the root password.

7 Log out of the console.

VMware, Inc. 35


36/88

Change the vRealize Operations Manager Administrator Password

You might need to change the vRealize Operations Manager administrator password as part of securing or

maintaining your deployment.

Procedure

1 In a Web browser, navigate to the vRealize Operations Manager administration interface at

https://master-node-name-or-ip-address/admin.

2 Log in with the admin username and password for the master node.

3 In the upper right, click the admindrop-down menu, and click Change Administrator Password.

4 Enter the current password, and enter the new password twice to ensure its accuracy.

NOTE You cannot change the administrator username of admin.

5 Click OK.

Add a Custom SSL Certificate to vRealize Operations ManagerIf you did not add your own SSL certificate when configuring the vRealize Operations Manager master

node, you can still add an SSL certificate after vRealize Operations Manager is installed.

Prerequisites

Create and configure the master node.

Procedure




3 At the upper right, click the yellow SSL Certificate icon.

4 In the SSL Certificate window, click Install New Certificate.

5 Click Browse for certificate.

6 Locate the certificate file, and click Opento load the file in the Certificate Information text box.

The file extension of the certificate file that you want to import does not matter. However, the certificate

file must contain both a valid private key and a valid certificate chain, and cannot be self-signed.

7 Click Install.

Remove a vRealize Operations Manager Node

You might need to remove a data node or remote collector node from a vRealize Operations Manager

cluster as part of resizing or maintaining your deployment.

NOTE You cannot remove the vRealize Operations Manager master node. In addition, you cannot remove a

replica node using this procedure. To remove a replica node, see Remove High Availability,on page 37.

Prerequisites

Note any adapters that are installed on the node, in case you want to reinstall those adapters on another

node. Removing a node also removes the adapter connections supported by that node.


36 VMware, Inc.


37/88

Procedure




3 Under Nodes in the vC Ops Cluster, select the node to remove.

4 If it is online, take the node offline.

5 Click the red Xto remove the node.

vRealize Operations Manager rebalances the cluster.

What to do next

Removing a node does not decommission the node because sensitive files, such as certificate files, remain on

the node.

For security, if you do not expect to re-add the node to the cluster, take one of the following precautions.

n Safeguard access to the node.

nSecurely delete it if it is a virtual machine.

n Securely erase the disk if it is a physical machine.

Remove High Availability

You might need to remove high availability (HA) from a vRealize Operations Manager cluster as part of

resizing or maintaining your deployment.

NOTE This process removes the replica node and restarts the vRealize Operations Manager cluster.

Prerequisites

Verify that the vRealize Operations Manager cluster is online.

Procedure




3 Click Disable HAand click OK.

vRealize Operations Manager converts the replica node back to a data node, and restarts the cluster.

Configuring Solutions and Adapters in vRealize Operations Manager

Solutions target a particular kind of monitoring or analysis of your environment by adding dashboards,alerts, reports, and other vRealize Operations Manager components.

Some solutions are delivered with vRealize Operations Manager, others can be added as management packs

that extend vRealize Operations Manager capabilities by integrating with external management tools.

Solutions that are delivered as management packs include dashboards, reports, alerts and other content, and

adapters. Adapters are how vRealize Operations Manager manages communication and integration with

other products, applications, and functions. When a solution management pack is installed and the solution

adapters are configured, you can use the vRealize Operations Manager analytics and alerting tools to

manage the objects in your environment.

Chapter 8 vRealize Operations Manager Post-Installation Considerations

VMware, Inc. 37


38/88

The most common solution is the VMware vSphere solution. This solution manages the connection between

vRealize Operations Manager and your vCenter Server instances, and provides the ability to run actions on

those instances. This solution is installed with vRealize Operations Manager and does not require you to

install a management pack.

Installing a Solution to Monitor and Manage Objects in Your Environment

If a solution is not delivered with vRealize Operations Manager, you install the solution by installing itsmanagement pack. A solution is a licensable entity and can contain multiple management packs.

You download management packs from the VMware Solutions Exchange Web site.

Install a Solution (http://link.brightcove.com/services/player/bcpid2296383276001?

bctid=ref:video_install_solution_vrom)

Add a Management Pack

A management pack is the part of the solution that you install. It contains the dashboards, alerts defintions,

policies, reports, and other content. A management pack may include multiple adapters.

You use the user interface to install the management pack.

If you upgrade from an earlier version of vRealize Operations Manager, the previous management pack files

are copied to the /usr/lib/vmware-vcops/user/plugins/.backupfile in a folder with a with a date and time

as the folder name. Before migrating your data to your new vRealize Operations Manager instance, install

the new adapters. After migration, none of your adapter customizations are included in the migration, and

you must reconfigure them.

Prerequisites

The solution that you downloaded includes a PAK file. Save that PAK file to a temporary folder on your

local system.

Procedure

1 Log in to the vRealize Operations Manager user interface with administrator privileges.

2 In the left pane of vRealize Operations Manager, click the Administrationicon and click Solutions.

3 On the Solutionstab, click the plus sign.

a Browse to locate the temporary folder and select the PAK file.

For example, vmware-vcops-6.0-MPforVCM-6.0-3900464.pak.

b Because existing dashboards are not overwritten by default, if you are performing a management

pack upgrade and you want to replace existing dashboards, select Reset out-of-the box content,

overwriting to a newer version provided by this update.

c Click Upload. After the file uploads, click Next.

d Read and accept the EULA and click Next.

Installation details appear in the window during the process. The installation might take several

minutes.

e When the installation is finished, click Finish.

The management pack is listed as a solution.

What to do next

Configure an adapter instance for the solution.


38 VMware, Inc.
http://link.brightcove.com/services/player/bcpid2296383276001?bctid=ref:video_install_solution_vromhttp://link.brightcove.com/services/player/bcpid2296383276001?bctid=ref:video_install_solution_vromhttp://link.brightcove.com/services/player/bcpid2296383276001?bctid=ref:video_install_solution_vromhttp://link.brightcove.com/services/player/bcpid2296383276001?bctid=ref:video_install_solution_vromhttp://link.brightcove.com/services/player/bcpid2296383276001?bctid=ref:video_install_solution_vrom


39/88

VMware vSphere Solution in vRealize Operations Manager

The VMware vSphere solution connects vRealize Operations Manager to one or more vCenter Server

instances so that you can collect data from those instances, monitor them, and run actions in them.

This solution, which is installed with vRealize Operations Manager, includes dashboards, alerts, actions,

analysis badges, capacity planning, reports, views, and other tools that monitor the target systems based onthe collected data.

The data collected from vCenter Server for managed objects includes metrics and some properties.

vRealize Operations Manager evaluates the data, identifying trends in object behavior, calculating possible

problems and future capacity for objects in your system based on those trends, and alerting you when an

object exhibits defined symptoms. The solution also provides actions that you can run on vCenter Server

from vRealize Operations Manager to manage those objects as you respond to problems and alerts.

The actions provided with the action adapter are focused on managing your virtual machines. The actions

include managing virtual machine power states, the number of CPUs, and the amount of memory. You can

also clean up datastores by deleting unused snapshots.

How the vCenter Adapter Credentials Work

The vCenter Server credentials that you use to connect vRealize Operations Manager to a vCenter Server

instance determine what objects vRealize Operations Manager monitors. As a vRealize Operations Manager

administrator, you must understand how the vCenter Adapter credentials and the user privileges interact to

ensure that you configure adapters and users correctly.

Because vRealize Operations Manager supports local user accounts and vCenter Server authentication, you

must take care with user permissions in vCenter Server and vRealize Operations Manager.

vCenter Adapter Credentials

When you configure a vCenterAdapter, you must provide vCenter Server credentials that have sufficient

privileges to connect to the vCenter Server and have access to the objects you are monitoring with

vRealize Operations Manager.

The privileges of the provided credentials determines what objects all users can see in

vRealize Operations Manager. For example, you can configure the adapter to connect to a vCenter Server

instance with credentials that have permission to access only one of your three hosts. Every user who logs in

to vRealize Operations Manager sees only the one host, even when an individual user has privileges on all

three of the hosts in vCenter Server.

User Privileges

You can control user access for the local users based on how you configure user privileges in Access Control

in vRealize Operations Manager. If users log in using their vCenter Server accounts, then how their

vCenter Server account is configured determines their privileges.

To avoid this type of unexpected result, configure local vRealize Operations Manager users and

vCenter Server users with the privileges you want them to have in your environment.

How vCenter Python Actions Adapter Credentials Work

When you configure a vCenter Python Actions Adapter in vRealize Operations Manager, you configure

credentials that are used to run the actions in vCenter Server. As a vRealize Operations Manager

administrator, you must understand how the adapter credentials and user privileges interact to ensure that

you configure adapters and users correctly.

Because vRealize Operations Manager supports local user accounts and vCenter Server authentication, you

must take care with user permissions in vCenter Server and vRealize Operations Manager.


VMware, Inc. 39


40/88

vCenter Python Action Adapter Credentials

When you configure a vCenter Python Actions Adapter, you must provide vCenter Server credentials that

have sufficient privileges to connect and make changes to objects on the vCenter Server. If the provided

credentials have limited access to objects in vCenter Server, even vRealize Operations Manager

administrative users can run actions only on the objects for which the vCenter Server credentials have

permission. If the provided credentials have access to all the objects in vCenter Server, any

vRealize Operations Manager user who runs actions is using this account.

User Privileges and Actions

You can control user access to actions for the local users based on how you configure user privileges in

Access Control in vRealize Operations Manager. If users log in using their vCenter Server accounts, then

how you have the account configured in vCenter Server determines their privileges.

For example, you might have a vCenter Server user with a read-only role in vCenter Server. If you give this

user the vRealize Operations Power User role in vCenter Server rather than a more restrictive role, the user

can run actions on objects because the adapter is configured with credentials that have privileges to change

objects.

To avoid this type of unexpected result, configure local vRealize Operations Manager users and

vCenter Server userswith the privileges you want them to have in your environment.

Configure a VMware vSphere Solution in vRealize Operations Manager

To monitor your VMware virtual infrastructure, you configure the vCenter Server and vCenter Python

action adapters for each of your vCenter Server instances.

The VMware vSphere solution is provided with vRealize Operations Manager. You do not need to

download or install a management pack.

The solution includes a vCenter Adapter and a vCenter Python Actions Adapter.

Procedure

1 Add a vCenter Adapter Instance in vRealize Operations Manageron page 41

To manage your vCenter Server instances in vRealize Operations Manager, you must configure an

adapter instance for each vCenter Server instance. The adapter requires the credentials that are used

for communication with the target vCenter Server.

2 Add a vCenter Python Actions Adapter Instance in vRealize Operations Manageron page 43

The vCenter Python Actions Adapter allows you to modify objects on your managed vCenter Server

instances from vRealize Operations Manager. The adapter is included with

vRealize Operations Manager solution and works in combination with the vCenter Server Adapter.

3 Define Monitoring Goals for Your VMware vSphere Solutions in vRealize Operations Manageron

page 44

To begin creating a monitoring policy specific to your environment, you provide answers to questions

that configure your default policy for this solution. Monitoring policies determine howvRealize Operations Manager evaluates the collected data and calculates trends.

4 Configure User Access for vCenter Server Actions in vRealize Operations Manageron page 45

To ensure that users can run actions in vRealize Operations Manager, you must configure user access

to the actions. You create action roles to control which actions a user can run and create user groups to

control which action adapter objects are available to the groups to which each user belongs.

5 Modify a vCenter Python Action Adapter Collection Intervalon page 47

The vCenter Python Action Adapter is installed with a five-minute collection interval. To minimize

traffic between vCenter Server and vRealize Operations Manager, you can change the collection

interval to a longer cycle.


40 VMware, Inc.


41/88

Add a vCenter Adapter Instance in vRealize Operations Manager

To manage your vCenter Server instances in vRealize Operations Manager, you must configure an adapter

instance for each vCenter Server instance. The adapter requires the credentials that are used for

communication with the target vCenter Server.

The vCenter Adapter that you use to connect to one or more instances of vCenter Server is provided in the

vRealize Operations Manager VMware vSphere solution. You do not need to install a management pack

before configuring this solution adapter.

When you configure the adapter, you must use one of the following URL formats:

n IP address

n FQDN

n https://IP address/sdk

n https://FQDN/sdk

CAUTION Any adapter credentials you add are shared with other adapter administrators and

vRealize Operations Manager collector hosts. Other administrators might use these credentials to configure

a new adapter instance or to move an adapter instance to a new host.

Prerequisites

Verify that you know the vCenter Server credentials that have sufficient privileges to connect and collect

data. If the provided credentials have limited access to objects in vCenter Server, all users, regardless of their

vCenter Server privileges, will see only the objects that the provided credentials can access. At a minimum,

the user account must have Read privileges and the Read privileges must be assigned at the data center or

vCenter Server level. See How the vCenter Adapter Credentials Work,on page 39

Procedure


2 On the Solutionstab, select VMware vSphereand click the Configurebutton on the toolbar.

3 Select vCenter Adapterin the Adapter Type list to add a new vCenter Server adapter instance.

If you are adding an additional adapter instance, click the plus sign on the lower pane toolbar.

4 Enter a Display nameand Descriptionfor the adapter configuration.

For example, vCenter Server 192.0.2.0.

5 In the vCenter Server text box, enter the FQDN or IP address of the vCenter Server instance to which

you are connecting.

The vCenter Server FQDN or IP address must be reachable from all nodes in the


6 To add credentials, click the plus sign.

a In the Credential nametext box, enter the name by which you are identifying the configured

credentials.

b Type the User nameand Passwordfor the vCenter Server instance.

c Click OK.

7 Click Test Connectionto validate the connection with your vCenter Server instance.


VMware, Inc. 41


42/88

8 In the Review and Accept Certificate dialog box, review the certificate information.

u If the certificate presented in the dialog box matches the certificate for your target vCenter Server,

click OK.

u If you do not recognize the certificate as valid, click Cancel. The test fails and the connection to

vCenter Server is not completed. You must provide a valid vCenter Server URL or verify the

certificate on the vCenter Server is valid before completing the adapter configuration.

9 To modify the advanced options regarding object discovery, change events, or registration user, expand

the Advanced Settings.

Option Description

Collector Determines which vRealize Operations Manager collector is used tomanage the adapter processes. If you have only one adapter instance,select Automatically select collector. If you have multiple collectors inyour environment, and you want to distribute the workload to optimizeperformance, select the collector to manage the adapter processes for thisinstance.

Auto Discovery Determines whether new objects added to the monitored system arediscovered and added to vRealize Operations Manager after the initialconfiguration of the adapter.

n If the value is true, vRealize Operations Manager collects informationabout any new objects that are added to the monitored system after theinitial configuration. For example, if you add more hosts and virtualmachines, these objects are added during the next collections cycle.This is the default value.

n If the value is false, vRealize Operations Manager monitors only theobjects that are present on the target system when you configure theadapter instance.

Process Change Events Determines whether the adapter uses an event collector to collect andprocess the events generated in the vCenter Server instance.

n If the value is true, the event collector collects and publishes eventsfrom vCenter Server. This is the default value.

n If the value is false, the event collector does not collect and publish

events.

Registration User and Password Provides the option to use a different set of credentials than you providedas the standard credentials.

The standard credentials must be provided. The standard credentialsshould have at least read permissions so that vRealize Operations Managercan collect data.

These advanced credentials allow you to register a vCenter Server with adifferent set of credentials. The registration user commonly has moreaccess rights. For example, this user account can register a vCenter Serverextension or asset. You use the advanced credentials in conjunction withthe standard credentials when you need to manage security by minimizingaccess.

10 Click Save Settings.

The adapter instance is added to the list.

vRealize Operations Manager begins collecting data from the vCenter Server instance. Depending on the

number of managed objects, the initial collection can take more than one collection cycle. A standard

collection cycle begins every five minutes.

What to do next

n Add a vCenter Python Actions Adapter for the same vCenter Server that you configured. See Add a

vCenter Python Actions Adapter Instance in vRealize Operations Manager,on page 43.


42 VMware, Inc.


43/88

Add a vCenter Python Actions Adapter Instance in vRealize Operations Manager

The vCenter Python Actions Adapter allows you to modify objects on your managed vCenter Server

instances from vRealize Operations Manager. The adapter is included with vRealize Operations Manager

solution and works in combination with the vCenter Server Adapter.

CAUTION Any adapter credentials you add are shared with other adapter administrators and

vRealize Operations Manager collector hosts. Other administrators might use these credentials to configurea new adapter instance or to move an adapter instance to a new host.

Prerequisites

n Verify that the vCenter Adapter is configured for the vCenter Server instances on which you are

running the actions. See Add a vCenter Adapter Instance in vRealize Operations Manager,on

page 41.

n Ensure that you know the vCenter Server credentials that have sufficient privileges to connect and

make changes to objects on this instance. If the credentials limited access to objects in vCenter Server,

you have the ability to run actions only on the objects for which the credentials have permission. See

How vCenter Python Actions Adapter Credentials Work,on page 39.

Procedure


2 On the Solutionstab, select VMware vSphereand click the Configurebutton on the toolbar.

3 Select vCenter Python Actions Adapterin the Adapter Type list to add a new adapter instance.

If you are adding an additional adapter instance, click the plus sign on the lower pane toolbar.

4 Type a Display Nameand Descriptionfor the adapter configuration.

For example, vCenter Server Actions 192.0.2.0.

5 In the vCenter Server text box, enter the FQDN or IP address of the vCenter Server instance to which

you are connecting.

The vCenter Server FQDN or IP address must be reachable from all nodes in the


6 To add credentials, click the plus sign.

a In the Credential nametext box, enter the name by which you are identifying the configured

credentials.

b Type the User nameand Passwordfor the vCenter Server instance.

c Click OK.

7 Click Test Connectionto validate the connection with your vCenter Server instance.

8 In the Review and Accept Certificate dialog box, review the certificate information.

u If the certificate presented in the dialog box matches the certificate for your target vCenter Server,

click OK.

u If you do not recognize the certificate as valid, click Cancel. The test fails and the connection to

vCenter Server is not completed. You must provide a valid vCenter Server URL or verify the

certificate on the vCenter Server is valid before completing the adapter configuration.


VMware, Inc. 43


44/88

9 To modify the advanced option regarding collectors, which determines which

vRealize Operations Managercollector manages the adapter processes, expand the Advanced Settings

and select one of the options.

If you have only one adapter instance, select Automatically select collector. If you have multiple

collectors in your environment and you want to distribute the workload to optimize performance, select

a collector.

10 Click Save Settings.

The adapter instance is added to the list.

What to do next

n Configure the default monitoring policy. See Define Monitoring Goals for Your VMware vSphere

Solutions in vRealize Operations Manager,on page 44

n If the monitoring policies page is not available because you are configuring an additional adapter

instance, configure the user roles for the actions. See Configure User Access for vCenter Server Actions

in vRealize Operations Manager,on page 45.

n If this is not the first time you configured an adapter instance, you can test that the vCenter Server

Python action adapter is working, select a virtual machine and then check that the actions are availablein the Actions menu. See the vRealize Operations Manager User Guide.

Define Monitoring Goals for Your VMware vSphere Solutions in vRealize Operations Manager

To begin creating a monitoring policy specific to your environment, you provide answers to questions that

configure your default policy for this solution. Monitoring policies determine how

vRealize Operations Manager evaluates the collected data and calculates trends.

This page of the Manage Solution - VMware vSphere wizard is available the first time you configure a

vSphere solution. It is not available when you configure additional solutions.

Prerequisites

n Configure the adapter for your vCenter Server instance. See Add a vCenter Adapter Instance in

vRealize Operations Manager,on page 41.

n To run actions on the vCenter Server instance for which you configured the adapter, configure the

vCenter Python Actions Adapter. See Add a vCenter Python Actions Adapter Instance in vRealize

Operations Manager,on page 43.

Procedure

1 On the Define Monitoring Goals page of the Manage Solution - VMware vSphere wizard, create a base

monitoring policy or use the current policy.

Option Description

Skip policy customization and use

the default base policy settings.

To use the current default policy, select the check box.

If you do not select this option, you must complete all the questions in thispage.

Which objects to you want to be

alerted on in your environment?

Determines which objects you manage with vRealize Operations Manager.

Which type of alerts do you want to

enable?

Determines which alert badge notifications you want to see in yourenvironment.

Alert definitions are configured to affect Health, Risk, or Efficiency whenan alert is generated. Select one or more of the alert types for which youwant to receive alerts.


44 VMware, Inc.


45/88

Option Description

How much do you want to

overcommit CPU and Memory in

your environment?

Determines how objects are monitored based on how you prefer tooversubscribe resources and whether you want to allow overcommitmentfor CPU and Memory.

CPU overcommitment is running more vCPUs on a host than the totalnumber of physical processor cores in the host.

Memory overcommitment is allowi

Documents

Vrealize Operations Manager 60 Vapp Deploy Guide