The Azure Virtual Edge Deployment Guide provides information on how to deploy a virtual edge in Azure leveraging the convenience of an Azure Resource Manager (ARM) Template.
More customers are moving workloads to a public cloud infrastructure to extend SD-WAN from remote sites to a public cloud to guaranteed Service Level Agreements (SLAs). There are multiple options offered by VMware SD-WAN, leveraging distributed VMware SD-WAN Gateways to establish IPsec towards public cloud private network or deploy the Virtual Edge directly in Azure.
For small branch deployment that demand throughput less than 1G, single virtual edge can be deployed in the private network (Azure vNets). For larger data center deployments that demand multi-gig throughput, Hub clustering can be deployed.
Note: In the
VMware SD-WAN Hub clustering design, a Layer 3 Instance is leveraged on the LAN side to run BGP between Hubs in the cluster and the Layer 3 Instance for route distribution in LAN. Since the Azure UDR does not support dynamic routing protocol, a third-party virtual router is required in the Azure infrastructure.
Prerequisites
The following prerequisites are required before you begin:
- An Azure account and login information.
- Familiarity with Azure Virtual Network concepts. (For more information, go to: https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-overview)
- RSA Public Key (For more information, go to: https://docs.microsoft.com/en-us/azure/virtual-machines/linux/mac-create-ssh-keys
- VMware ARM Template
- SD-WAN Orchestrator target and admin account to login.
