You must have an active VMware Cloud Proxy before you can use vRealize Log Insight Cloud. If none are present, you are informed of this when you open the landing page and prompted to begin download and deployment.

If you already have one or more Cloud Proxies, you can deploy an additional Cloud Proxy for your installation.
Note: Cloud Proxy does not support an HTTP proxy that requires NTLM authentication.

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.
  • Verify that outgoing HTTPS traffic is allowed for the Cloud Proxy.
  • When you use a web browser to connect to VMware Cloud Services, ensure that the computer that runs the web browser has HTTPS port 443 open to outgoing traffic with access through the firewall to:
    • *.vmwareidentity.com gaz.csp-vidm-prod.com
    • *.vmware.com
  • When you connect to VMware Cloud Services from a data collector, ensure that the computer that the data collector is on has HTTPS port 443 open to outgoing traffic with access through the firewall to:
    • *.vmware.com
    • symphony-docker-external.jfrog.io
    • ci-data-collector.s3.amazonaws.com
  • Log in to vRealize Log Insight Cloud by specifying the URL https://www.mgmt.cloud.vmware.com/li/ and entering your login credentials.

Procedure

  1. Click the two arrows icon in the upper-left corner of the screen to expand the main menu.
  2. Navigate to Configuration > Cloud Proxies.
  3. Click New.
    The Install Cloud Proxy dialog box appears. Leave this dialog box open, as you will need it later.
  4. To deploy the Cloud Proxy, click Download OVA.
  5. Navigate to your VMware vSphere Web Client data center and click the name of your vCenter cluster. In the drop-down menu, select Deploy OVF Template.
  6. In the Deploy OVF Template form, perform the following actions.
    1. Click Select template, then Local File. Paste in the path to the OVA Cloud Proxy file you downloaded. Click Next.
    2. Click Select name and location, then enter the name of your OVA file. Select the cluster where you want to install the Cloud Proxy, and click Next.
    3. Click Select a resource and the cluster where you want to run the Cloud Proxy, and then click Next.
    4. Review the details of your Cloud Proxy deployment. Notice the Size on disk text box. The location where you deploy the Cloud Proxy in the following steps must have enough space available. Click Next.
    5. Accept the License Agreement. Click Next.
    6. Click Select storage and select a datastore from the list with enough free space for the OVA file. Click Next.
    7. Click Select networks and select a destination network, and then click Next.
    8. Click Customize template and enter the required information. Do not click Next.
      • For Root User Password, choose a unique password. It does not need to match the vCenter password.
    9. Return to vRealize Log Insight Cloud and collect the token key provided on the Install Cloud Proxy dialog box. Click Copy to copy the key. Use the Copy control to ensure you are copying the entire key.
      Note: Token keys should be used within 24 hours and should be used for only one Cloud Proxy.
    10. Return to the template form and click Networking Properties. If you use DHCP in your vCenter network, do not enter any information. If you do not use DHCP, then you must provide information for each setting. Click Next.
    11. Click Ready to complete and review your configuration data. Click Finish.
      The Cloud Proxy is installed.
  7. Click the green arrow at the top of your page to run the Cloud Proxy.
  8. To verify that your Cloud Proxy is running, look under the VMs tab at the list of your virtual machines to ensure its state is Powered On.
  9. Return to the vRealize Log Insight Cloud Install Cloud Proxy dialog box. Wait for a success message saying a connection has been made. (This may take several minutes.)

What to do next

Consult Port Requirements of Remote Cloud Proxy and then enable log and event forwarding to the Cloud Proxy.