This section describes post-installation and installation verification steps.

If everything worked as expected in the installation, you can now login to the VM.

  1. If everything works as expected, you should see the login prompt on the console. You should see the prompt name as specified in cloud-init.

    vcg-post-install-verification-code-prompt-name

  2. You can also take a look at /var/log/cloud-init.log. If you see the message below, it is likely that the cloud init runs successfully.

    vcg-code-cloud-init-completed

  3. Verify that the VeloCloud Gateway is registered with VCO.

    vcg-is-registered-with-vco

  4. Verify Outside Connectivity.

    vcg-code-verify-outside-connectivity

  5. Verify that the MGMT VRF is responding to ARPs.

    vcg-code-verify-mgmt-vrf

  6. Remove cloud-init so it doesn’t run again.
    Note: If you have deployed OVA on VeloCloudvSphere with vAPP properties, you must disable cloud-init prior to upgrading to versions 4.0.1 or 4.1.0. This is to ensure that the customization settings such as network configuration or password are not lost during the upgrade.
    apt-get purge cloud-init 
  7. Associate the new gateway pool, (created in the section titled, “ Creating a Gateway and getting the Activation Key”) with the customer.

    vcg-associate-new-gateway-pool

  8. Associate the Gateway with an Edge.

    vcg-associate-gateway-with-edge

  9. Verify that the Edge is able to establish a tunnel with the Gateway on the Internet side. From the VMware SD-WAN Orchestrator, go to Monitor > Edges > Overview.

    From the VMware SD-WAN Orchestrator, go to Test & Troubleshoot > Remote Diagnostics > [Edge] > List Paths, and click Run to view the list of active paths.

  10. Configure the Handoff interface.

    vcg-configure-handoff-interface

  11. Verify that the BGP session is up.

    vcg-verify-bgp-session-is-up