Before you deploy the remote collector nodes of vRealize Operations Manager in Region B, verify that your environment fulfills the requirements for this deployment.

IP Addresses and Host Names

Verify that static IP addresses and FQDNs for the vRealize Operations Manager application virtual network are available for Region B of the SDDC deployment. 

For the remote collector group, allocate two static IP addresses and FQDNs and map host names to the IP addresses.

Table 1. Application Virtual Network Names for vRealize Operations Manager
vRealize Operations Manager Component Application Virtual Network
Analytics Cluster Mgmt-xRegion01-VXLAN
Remote Collector Group Mgmt-RegionB01-VXLAN
Table 2. IP Addresses and Host Names for the Remote Collector Nodes in Region B
Role IP Address FQDN
Remote collector node 1 192.168.32.31 lax01vropsc01a.lax01.rainpole.local
Remote collector node 2 192.168.32.32 lax01vropsc01b.lax01.rainpole.local
Default gateway 192.168.32.1 -
DNS server
  • 172.17.11.5
  • 172.17.11.4
-
Subnet mask 255.255.255.0 -

Deployment Prerequisites

Verify that your environment satisfies the following prerequisites for deployment of vRealize Operations Manager remote collector nodes.

Prerequisite Value
Storage
  • Virtual disk provisioning.
    • Thin
  • Required storage per analytics cluster node to support replication and failover: 1.3 TB
  • Required storage per remote collector group nodes.
    • Initial storage per node: 274 GB
Software Features
  • Verify that vCenter Server is operational.
  • Verify that the vSphere cluster has DRS and HA enabled.
  • Verify that the NSX Manager is operational.
  • Verify that the application virtual networks are available.
  • Verify that the Load Balancer service is disabled on the NSX Edge services gateway.
  • Verify that the vRealize Suite Lifecycle Manager is operational and data collection from the management vCenter Server instance has run successfully.
  • Verify that Postman App is installed in your browser.