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.
Prerequisites
- 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.
Procedure
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.