VRealize Operations Manager 8.3 Deployment on Oracle Cloud Vmware Solution

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

Oracle Cloud VMware Solution

but lets talk on my Favor VMware Solution OCVS , we are going to deploy the solution on OCVS , that mean deploying vmware like on-prem or even under you desk , VMware with Full control.

Oracle Cloud VMware Solution is a fully certified and supported solution that uses Oracle Cloud Infrastructure (OCI) to host a highly available and scalable VMware software-defined data center (SDDC). A standard VMware implementation, it works with existing operational practices.

https://blogs.oracle.com/cloud-infrastructure/announcing-the-global-availability-of-oracle-cloud-vmware-solution

Key Benefits of Oracle Cloud VMware Solution

i have choose the OCVS as a Platform to deploy and configure the VROPS 8.3, it is the simple and the easy way you can deploy the Vsphere Platform, oracle share much more common ground with vmware then other Cloud vendor, making it perfect fit for your migration of Vsphere Workload to OCI OCVS Cloud Solution.

during the process of the deployment i decide to deploy the vRealize Operation as an OVA Deployment , of course you can deploy it with the ISO file and of VRLCM but for VROPS it is clear the OVA Deployment is the most easy and common method to use.

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 objects
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.

https://kb.vmware.com/s/article/2093783

VROPS Installation Requirements

  • All Nodes must use static IP address, or fully qualified domain name (FQDN) with a static IP address. Nodes deployed by OVF have their hostnames set to the retrieved FQDN by default.
  • 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.
  • vRealize Operations Manager version. All nodes must run the same vRealize Operations Manager version.
  • Do not distribute analytics cluster nodes over a wide area network (WAN).
  • Download the Latest VROPS 8 .3 OVA from your Vmware Web Platform.
  • Valid VROPS or Cloud License for Version 8.X .

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.
  • 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.

Download of vRealize Operations Manager

pretty simple , you just need a valid account within myvmware to access and download the vRealize Operation 8.3

https://my.vmware.com/en/web/vmware/downloads/info/slug/infrastructure_operations_management/vmware_vrealize_operations/8_3

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 workload Resource Pool and press Next.

Review and Next.

Accept the EULA and Next.

you will need to choose the Size of the VROPS, i have chosen the Medium configuration, Therefore you can serve until 15000 Objects.

Select Disk provision as Thin or Thick Base on your VSAN Storage Policy and press Next.

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

i have chosen to run the vRealize Operation on the workload network to still give high priority to the management stack

Provide below information and click Next :

Gateway: 172.0.0.1
Domain Name: workload-dns.zone
Domain Search Path: workload-dns.zone
DNS: 172.0.0.99 (DNS servers with comma)
Network 1 IP: 172.0.0.160
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://vrops831.workload-dns.zone/admin or https://172.0.0.160/admin as shown below. vrops831.workload-dns.zone is my first and master node.

please Choose the New Installation, if this a second node you can choose to expend, but the easier way to setup VROPS will be single Node and protect the Application with FFT 2 of VSAN Protection, this is the cheapest way to achieve high level of vrealize Operation Service.

Click Next.

In the vRealize Operations Manager Initial Setup dialog box, set the new password for the vRealize Operations Manager instance.

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.

In the vRealize Operations Manager Initial Setup dialog box, select whether to use a self-signed SSL certificate or install a customer certificate.

Provide the appliance or Master node Name as in DNS record

Enter the NTP address pool.ntp.org – 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.

wait for the Cluster to first be configure until you will have the option to start.

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.

after the solution is build you will need to open a browser and login to the VROPS8 UI with https://172.0.0.160

Login with Admin and password you have configure for Admin.

on the Welcome screen please press NEXT.

Accept the EULA and Next.

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

Accept the EULA and Next.

Click Finish.

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.

Remember to enable the VSAN Management pack, that will enable you to view your storage needs in much more details.

and here you go, the OCVS solution is being Monitor by VROPS 8.3, you can see that the OCVS solution is build on NSX-T , Vcenter and HCX, but you can see that i have added lots of more VM’s to run on the solution.

on the next Blogs i will show how to Monitor your NSX-T and HCX with VROPS 8.3 on OCVS.

Leave a Reply

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