This section describes post-installation and installation verification steps.
If everything worked as expected in the installation, you can now login to the VM.
- 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.
- 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.
- Verify that the VeloCloud Gateway is registered with VCO.
- Verify Outside Connectivity.
- Verify that the MGMT VRF is responding to ARPs.
- 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
- Associate the new gateway pool, (created in the section titled, “ Creating a Gateway and getting the Activation Key”) with the customer.
- Associate the Gateway with an Edge.
- 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
From the VMware SD-WAN Orchestrator, go to Run to view the list of active paths., and click
- Configure the Handoff interface.
- Verify that the BGP session is up.