Describes how to configure a Non-VeloCloud Site (NVS) of type Microsoft Azure Virtual Hub in VCO.
To configure a NVS of type Microsoft Azure Virtual Hub in VCO:
- Ensure you have configured an IaaS subscription. For steps, see configure an Infrastructure as a Service Provider (IaaS) subscription.
- Ensure you have created Virtual WAN and Hubs in Azure. For steps, see Configure Azure Virtual WAN for Branch-to-Azure VPN Connectivity.
- From the navigation panel in the VCO, go to Configure > Network Services.
The Services screen appears.
- In the Non-VeloCloud Sites area, click the New button.
The New Non-VeloCloud Site dialog box appears.
- In the Name text box, enter the name for the Non-VeloCloud site.
- From the Type drop-down menu, select Microsoft Azure Virtual Hub.
- From the Subscription drop-down menu, select a subscription.
The application fetches all the available Virtual WANs dynamically from Azure.
- From the Virtual WAN drop-down menu, select a virtual WAN.
The application auto-populates the resource group to which the virtual WAN is associated.
- From the Virtual Hub drop-down menu, select a Virtual Hub.
The application auto-populates the Azure region corresponding to the Hub
- Select the Enable Tunnel(s) checkbox to enable VeloCloud VPN Gateways initiate VPN connections to the target Virtual Hub, as soon as the site is successfully provisioned.
Note: VeloCloud VPN Gateways will not initiate IKE negotiation until this Non-VeloCloud Site (NVS) is configured on at least one profile.
- Click Next.
The VCO automatically initiates deployment, provisions Azure VPN Sites, and downloads the VPN Site Configuration for the newly configured sites and stores the configuration in the VCO’s Non-VeloCloud site configuration database.
Once the Azure VPN sites are provisioned at the VCO side, you can view the VPN sites (Primary and Redundant) in the Azure portal by navigating to your Virtual WAN page > Virtual WAN architecture > VPN sites.
What to do next
- Associate the Micorsoft Azure Non-VeloCloud Site to a Profile in order to establish a tunnel between a branch and Azure Vitual Hub. For more information, see Associate a Non-VeloCloud Site to a Profile.
- You must add SD-WAN routes in to Azure network manually. For more information, see Edit a VPN Site.