Using cloud proxies in vRealize Operations, you can collect and monitor data from your remote data centers. Typically, you need only one cloud proxy per physical data center. You can deploy one or more cloud proxies in vRealize Operations to create a one-way communication between your remote environment and vRealize Operations. The cloud proxies work as one-way remote collectors and upload data from the remote environment to vRealize Operations. Cloud proxies can support multiple vCenter Server accounts. For more information on cloud proxies, see the topic called Cloud Proxy FAQ in the VMware vRealize Operations vApp Deployment Guide.
- Verify that you have an IP address, a DNS entry, and permissions to deploy OVF templates in vSphere.
- Log in to vSphere and verify that you are connected to a vCenter Server system.
- Allow outgoing HTTPS traffic for cloud proxy over port 443.
- Allow outgoing traffic from the endpoints to cloud proxy over 443, 4505, and 4506.
- Add a vCenter cloud account and provide an account with the following read and write privileges:
- vCenter IP address or FQDN
- Permissions required to install a cloud proxy on the vCenter Server.
For more information on privileges, see the topic called "Privileges Required for Configuring a vCenter Adapter Instance" in the vRealize Operations Configuration Guide.
- Cloud proxies must have a proper DNS resolution to the vRealize Operations nodes when using short/long FQDN names. This is applicable to on-prem cloud proxy.
- Log in to vRealize Operations.
- From the left menu, click New. , and then click
- Save the OVA path. Optionally, click Download Cloud Proxy OVA to download and save the OVA file locally.
- To copy the link for the VMware vRealize® Operations Cloud Appliance™, click the Copy Path icon for the Cloud Proxy OVA.
- To download and save the OVA file locally, click Download Cloud Proxy OVA.
- Navigate to your vSphere, select the name of your vCenter Server cluster, and select Deploy OVF Template from the Actions menu.
- Insert the ova link and then click Next.
- Paste the cloud proxy ova link in the URL field.
- Click the Local File option, browse, and select the downloaded OVA file.
- Follow the prompts to install the OVA on your vCenter Server.
For the most current information about sizing and scaling, see Knowledge Base article 78491.
- When prompted to enter the Unique Registration Key in the Customize template screen, return to the Install Cloud Proxy page in vRealize Operations.
- (Optional) Activate Data Persistence to store data in the cloud proxy in case of connectivity issues.
Note: The Unique Registration Key is refreshed and a new key is generated if you activate data persistence.
- Click the Copy Key icon.
The Unique Registration Key expires 24 hours after generation. To avoid using an expired key, click Regenerate Key before proceeding. The unique registration key is used by the cloud proxy to authenticate to vRealize Operations.
- Return to vSphere and paste the key in the Unique Registration Key text box to install the vRealize Operations Cloud Appliance.
- Select Use IPv6 to use IPv6 for internal communications. For more information, see Using IPv6 with vRealize Operations.
- (Optional) Set up a proxy server in the Customize template screen.
- Enter details in the Network Proxy IP Address and Network Proxy Password properties.
- To activate SSL, select the Use SSL connection to proxy check box.
- If you are using SSL, you can verify the certificate of the proxy server. Public certificate authorities are used to verify the proxy server certificate. To activate this, select the Verify proxy's SSL cert check box in the Verify SSL cert property.
- You can specify the IP /FQDN URL that is used to access the system when a load balancer is used.
- If you have a custom certificate authority, paste the root certificate authority in the Custom CA property to verify the certificate of the proxy server. The root certificate authority is passed on to the cloud proxy. Do not include the following lines from the certificate authority:
For more information on adding CA certificates while deploying a cloud proxy in vRealize Operations, see the VMware KB article 83698.
You can use the Load Balancer Custom CA for the vRealize Operations environment.
- Click Finish.
The deployment takes a few minutes to finish.
- Locate the cloud proxy you just installed, select the vRealize Operations Cloud Appliance, and click Power on.
Note: You must power on the vRealize Operations Cloud Appliance within 24 hours of registering it. After 24 hours, the Unique Registration Key expires, and you must delete the vRealize Operations Cloud Appliance and deploy another cloud proxy.
- Return to the Cloud Proxy page in vRealize Operations to view the status of the cloud proxy you just installed. For more information, see Monitoring the Health of Cloud Proxies.
- To view the accounts that are using this connection, click the Cloud Proxy.
The communication from the cloud proxy to cloud is one way. The cloud proxy initiates this connection and if necessary, it also pulls data from cloud (like the adapters configuration or upgrade pak). The cloud proxy requires a regular Internet access over the https protocol but it does not need any special firewall configuration. The cloud proxy verifies the certificate of the cloud service it connects to and if there are transparent proxy servers which do stop SSL, it might cause connectivity problems for the cloud proxy.
The cloud proxy also supports connection through the corporate proxy server. The proxy settings are given during OVF deployment.
- (Optional) To remove a cloud proxy, click Remove. For more information, see Removing Cloud Proxies.
What to do next
Upgrade your cloud proxy. For more information, see the topic called Upgrading Cloud Proxy in the VMware vRealize Operations vApp Deployment Guide.
The VMware vSphere solution connects vRealize Operations to one or more vCenter Server instances. For more information see the topic called Configure a vCenter Server Cloud Account in vRealize Operations in the Connecting to Data Sources section in the VMware vRealize Operations Configuration Guide.