vRealize Operations Manager – vROPS 6.0 – New Deployment

vRealize Operations

In this post we will go through the steps of deploying vROPS 6.0 and configuring basics to allow vROPS to start collecting data from vCenter instance.

Some notes about vROPs deployments in general:

  1. The resources that is needed for VROPS is dependent on multiple factors, such as number of management packs, objects (hosts, VMs, etc)
  2. During installation, each node can be Extra Small/Small/Medium/Large in size.
  3. Every node must be same size.
  4. Each node must be registered and resolved by DNS (forward/reverse)!!!
  5. No requirement for IP Pools

Quick overview of installation steps:

Installation of Master Node > Configuration of Master Node > Optional – Installation of Data Nodes and Remote collectors  > Optional – Enabling HA –> Login into UI >> Configuration for new installation or upgrade scenarios

Deployment Options:

  1. Single location with one or more vCenters: Scale out, multi node vROPs, scaling out as necessary in the same site
  2. Multiple location/sites and one or more vCenters at each site
    1. At each location, vROPS instanca can be deployed. In this case, each user log into their respective vROPS instance at their site.
    2. VROPS cluster at main Datacenter and Remote Collectors at remote sites.
      1. Each user logs into VROPS UI at the main site
      2. If the network between sites is not at the speed of LAN and you want to have single vROPS instance, remote collectors must be used to collect data from other sites.
  3. Two main locations with one or more vCenters: Seperate VROPS clusters at each site can be deoployed. Each cluster/instance owns its data and do not share data between deployments.

For sizing, please refer to the article which is being maintained by VMware: vRealize Operations Manager 6.0 Sizing Guidelines (2093783)

As of Feb 27th, the following is the recommended sizing for vROPS. Please check out the KB for up to data…

vROPS Sizing

Installation

Deploy OVF Template

Installation is very easy. We will be deploying ovf as usual via vCenter.  After pointing the ovf file, in the second step, accept “extra configuration” to allow numa.vcpu.preferHT to be enabled.

VROPS Advanced Config preferHT

Select deployment size (in this case small < 2000 VMs). This will deploy appliance with 4vCPU and 16GM memory.

Deployment Size VROPS

For the storage part, it depends on your environment but the best practice is to have thick eager zeroed since the workload will be write intensive.

For Network, please use static IP if you are not deploying the appliance just to play :=)

Configuring the vRealize Operations Manager Cluster

After you deploy the appliance, through web browser, open DNS name of the deployed system.

Get Started VROPS

Initial Setup:

  • Express: Quick and easiest. Best for 1 node vROPS clusters.

Express InstallationcVROPS

  • New Installation: Advanced Configuration options that is not available with express options

New Installation VROPS

We will be going with new installation. The first node will be Master.

vROPS Admin Password vROPS Certificate

As a best practice, provide external NTP source for master node. All other nodes will sync time from Master node:

Master Node Name and NTP

Now you can start Cluster, this will take some time though. In addition, as shown in the initial workflow, you can now optionally add additional nodes to this instance as either Data node or Remote Collector.

vROPS Staring Cluster 

Add other nodes:

Open the URL for the additional node and select Expand an Existing Installation:

Expand an Existing Installation VROPS

VROPS Node Settings

VROPS - Cluster Info 

To join Cluster 

For shared password, you can create one if someone else is deploying additional node and you don’t want to give the admin password. For this, in the Master Node UI, click generate password icon…

Passphrase to add Node

First Configuration:

Self-explanatory:

Configure Solution image

Licence

We will be configuring vCenter Solution to collect data. There is two adapters for vCenter.

vCenter Solution in vROPS

One is vCenter Adapter to collect data and the second one is python Actions Adapter to apply/Remediate resolution actions via vROPS. Add Adapter for each and click save button before proceeding further.

vCenter Solution Adapters in vROPS

For monitoring goals in the next section, I will be going with the following policy: All Objects, All Alerts, Dont Overcommit, Include Network and Storage IO..

Monitoring Goals 

Now, once you click finish you should be able to see adapters in “Data Receiving” State.

Solution State 

An Voila! Of course, it needs some time to collect data and analyze.

vRealize Operations Manager

Bulent Tolu

Bulent Tolu

Sr. Systems Engineer at VMware
Bulent is an IT professional with Master's in MIS and 10-years of experience in broad range of Information Technologies. He is exposed to engineering/architecting, implementation/integration, and administration of various high-available IT systems and infrastructure. He has a passion to continually research, test and evaluate new technologies and follow industry best practices to secure and optimize IT systems. Currently, he lives in Istanbul and works as a Sr. Systems Engineer at VMware.
Bulent Tolu

3 Thoughts on “vRealize Operations Manager – vROPS 6.0 – New Deployment

  1. Bulent,

    Thank you for your post on the vROPS, I have a question for you, How do you add additional vCenters to a vROPS instance and what could be the best practices for a large environment ?, would you use a HA solution, such as installing two master nodes and a data node?

    Your response would be greatly appreciated.

    Thanks in advanced.

Leave a Reply

Your email address will not be published. Required fields are marked *

Post Navigation

Share
Translate »