vRealize Operations Manager 8.0 Deployment Guide

In this article we will try to describes the steps to you need to take to deploy the new Vmware vRealize Operations 8

Preparing for VROPS Installation Requirements

  • All Nodes must use static IP address, or fully qualified domain name (FQDN) with a static IP address.
  • You can successfully reverse-DNS all nodes, including remote collectors, to their FQDN, currently the node hostname.
  • All nodes, including remote collectors, must be bidirectionally routable by IP address or FQDN.
  • Do not separate analytics cluster nodes with network address translation (NAT), load balancer, firewall, or a proxy that inhibits bidirectional communication by IP address or FQDN.
  • One-way latency between the analytics cluster nodes must be 5 ms or lower.
  • Do not distribute analytics cluster nodes over a wide area network (WAN).
  • Download the Latest VROPS 8 .0OVA from your Vmware Web Platform.
  • Valid VROPS or Cloud License for Version 8 – remember , old License from 6.6 and below will not work.

Cluster Node Networking Requirements

When you create the cluster nodes that make up vRealize Operations Manager, the associated setup within your network environment is critical to the inter-node communication and proper operation.

  • The master and replica nodes must use a static IP address, or fully qualified domain name (FQDN) with a static IP address.Data and remote collector nodes can use dynamic host control protocol (DHCP).
  • You can successfully reverse-DNS all nodes, including remote collectors, to their FQDN, currently the node hostname.Nodes deployed by OVF have their hostnames set to the retrieved FQDN by default.
  • All nodes, including remote collectors, must be bidirectionally routable by IP address or FQDN.
  • Do not separate analytics cluster nodes with network address translation (NAT), load balancer, firewall, or a proxy that inhibits bidirectional communication by IP address or FQDN.
  • Analytics cluster nodes must not have the same hostname.
  • Place analytics cluster nodes within the same data center and connect them to the same local area network (LAN).
  • Place analytics cluster nodes on same Layer 2 network and IP subnet.A stretched Layer 2 or routed Layer 3 network is not supported.
  • Do not span the Layer 2 network across sites, which might create network partitions or network performance issues.
  • With Continuous Availability enabled, separate analytics cluster nodes into fault domains, stretched across vSphere clusters
  • One-way latency between the analytics cluster nodes must be 5 ms or lower.
  • Network bandwidth between the analytics cluster nodes must be one gbps or higher.
  • Do not distribute analytics cluster nodes over a wide area network (WAN).To collect data from a WAN, a remote or separate data center, or a different geographic location, use remote collectors.
  • Remote collectors are supported through a routed network but not through NAT.
  • Do not include an underscore in the hostname of any cluster node.

Cluster Node Best Practices

When you create the cluster nodes that make up vRealize Operations Manager, additional best practices improve performance and reliability in vRealize Operations Manager.

  • Deploy vRealize Operations Manager analytics cluster nodes in the same vSphere cluster in a single datacenter and add only one node at a time to a cluster allowing it to complete before adding another node.
  • If you deploy analytics cluster nodes in a highly consolidated vSphere cluster, you might need resource reservations for optimal performance.Determine whether the virtual to physical CPU ratio is affecting performance by reviewing CPU ready time and co-stop.
  • Deploy analytics cluster nodes on the same type of storage tier.
  • To continue to meet analytics cluster node size and performance requirements, apply storage DRS anti-affinity rules so that nodes are on separate datastores.
  • To prevent unintentional migration of nodes, set storage DRS to manual.
  • To ensure balanced performance from analytics cluster nodes, use ESXi hosts with the same processor frequencies. Mixed frequencies and physical core counts might affect analytics cluster performance.
  • To avoid a performance decrease, vRealize Operations Manager analytics cluster nodes need guaranteed resources when running at scale. The vRealize Operations Manager Knowledge Base includes sizing spreadsheets that calculate resources based on the number of objects and metrics that you expect to monitor, use of HA, and so on. When sizing, it is better to over-allocate than under-allocate resources.

Deployment of vRealize Operations Manager

Login to vCenter – Right click Cluster or Host – Deploy OVA template – provide Name for appliance and select the OVA file downloaded.

Provide the Location of the OVA Deployment File.

Provide the Name for VM to display and select VM folder.

Select the host and Next.

Review and Next.

Accept the EULA and Next.

you will need to choose the Size of the VROPS, i have chosen the small configuration, Therefore you can serve until 3500 VMs.

Select Disk provision as Thin or Thick and Next.

Select the Network port group for vROPS appliance Network and Next.

Provide below information and click Next :

Gateway: 192.168.1.1
Domain Name: mt.local
Domain Search Path: mt.local
DNS: 192168.1.100,192.168.1.101 (DNS servers with comma)
Network 1 IP: 192.168.1.130
Network Netmask: 255.255.255.0

Review and finish to deploy the appliance.

Power on your new VROPS Virtual machine.

The console of vROPS appliance will look like this, as you notices it has automatically detected the DNS record from DNS server as shown below.

Cluster configuration

Open vROPS using https://vrops02.mt.local/admin or https://192.168.1.130/admin as shown below. vrops02.mt.local is my first and master node.

Installation Types

  • Express Installation
  • New installation
  • Expand Installation

Click New installation.

Click Next.

Provide the appliance admin account password for ui access.

Use default certificates or if you like to have certificate from external CA go ahead and install. will advise to use VRLCM to generate and install the VROPS Certification.

Provide the appliance or Master node Name as in DNS record

Enter the NTP address 216.239.35.0 – click ADD

Then click Next.

if you wish to enable VROPS HA , i dont recommend enable HA During the First Deployment of VROPS.

As a result This module has been change a lot with VROPS 8 that recognize that only provide HA for Compute is cover at most and Therefore to be able to extend availability that the enable us to Configure Continues Availability to provide Datacenter Crush that does happen from time to time.

please add any Data Node to your Cluster, i will choose continue without any other Data Node.

Click Finish.

The VROPS Admin UI is open and the VROPS Cluster is starting to buildup.

you will need to press the bottom to “START vREALIZE OPERATIONS MANAGER”

Please Confirm first Application Startup and press YES

The Startup Process takes between 10-15 min to get the Cluster online.

and as you can see you have now two option for configure Availability

Verify that you Cluster online before processing to the UI

Solution Configuration

Please login to the VROPS8 UI with https://vrops02.mt.local

Login with Admin and password

on the Welcome screen please press NEXT.

Accept the EULA and Next.

Provide VROPS License, i have chosen to use the Product Evaluation.

you can choose if to join the VMware Customer Experience Improvement Program.

Click Finish to process to the UI

Vcenter Adapter configuration

Please choose to Create Cloud Account to be able configure VROPS Adapter.

Press on the ADD ACCOUNT.

With Account Type lets choose Vcenter type.

with the Cloud Account you will need to provide this Data:

  • Name of Account
  • vCenter Server IP Address or FQDN
  • Credential for Vsphere Adapter
  • Collector/Group
  • if the Operational Action is Enable you will need to provide
  • Action Vsphere Credentials

Vcenter Admin User

Privileges Required for Configuring a vCenter Adapter Instance

The vCenter Adapter instance monitors and collects data from vCenter Server and the vCenter Action Adapter performs some actions in vCenter Server. So, for monitoring or collecting vCenter Server inventory and their metrics and properties, the vCenter Adapter instance needs credentials with the following privileges enabled in vCenter Server.

Vcenter Admin Action

Privileges Required for Configuring a vCenter Action Adapter Instance

Press the TEST Connection to Verify Configuration.

Accept the Certification.

Verify that Test has finish Successful.

Define the Monitoring Goal, this will define the Default policy Goals

Verify you are able to save your Goals.

Accept the vrealize Operations Manager Registration

and now you can see the Cloud Account configured and status.

the next Step will be to configure the VROPS Currency

in this examples i will choose US Dollar and press Set Currency.

Press OK to acknowledge

Leave a Reply

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