Integrate VeloCloud SD-WAN with Microsoft Route Server

You can integrate VeloCloud SD-WAN with Microsoft Route Server for the Establish Branch-to-Cloud Connectivity and Establish Branch-to-AVS Connectivity use cases.

Prerequisites

Complete the following prerequisites before proceeding with integrating VeloCloud SD-WAN with Route Server:
  • Obtain Enterprise account access to VeloCloud Orchestrator.
  • On the VeloCloud Edges, run software version 4.2.0 or newer.
  • Obtain access to the Microsoft Azure portal with the appropriate IAM roles.

Establish Connectivity

Complete the following high-level tasks to establish connectivity:
  1. Deploy a 2-member cluster in a region.
  2. Deploy the Route Server.
  3. Connect on-premises either to Microsoft Azure resources and/or to Azure VeloCloud Solutions (AVS)
For detailed instructions on how to integrate VeloCloud SD-WAN with Microsoft Route Server, see the following use cases:

Establish Branch-to-Cloud Connectivity

This section describes the steps to integrate VeloCloud SD-WAN with Microsoft Route Server for the Establish Branch-to-Cloud Connectivity use case.

The following figure illustrates the branch-to-cloud connectivity.

Figure 1. Branch-to-Cloud Connectivity
Note: As shown in the diagram, connect “host1” sitting on-premises to “VM1” and “VM2” in Azure.

To create Edge instances and Route Server and to establish branch-to-cloud connectivity, perform the following tasks:

  1. Create two SD-WAN virtual Edge instances. For instructions, refer to the Azure Virtual Edge Deployment Guide.
  2. Log in to the Orchestrator as an Enterprise user, and then add the two SD-WAN virtual Edge instances to a cluster. For instructions, refer to the “Configure Edge Clustering” section in the VeloCloud SD-WAN Administration Guide, and for more information, see the section titled, "How Edge Clustering Works."
  3. From the Azure Portal, create your Route Server. For instructions, refer to Create and Configure Route Server using the Azure portal.
  4. Retrieve the Azure Route Server IPs and ASN.
    Figure 2. Azure Route Server IPs and ASN Details
  5. From the Orchestrator, for the first Edge called sdwan-edge1:
    1. Statically assign an IP address to GE3 interface, which can be retrieved by selecting Test & Troubleshoot > Remote Diagnostics > Edge > Interface status .
      Figure 3. Configure GE3 Routed Interface
      Figure 4. GE3 Interface Settings
    2. Configure the static routes for your Edge to be able to reach the Route Server IPs.
      Figure 5. Configure Static Routes
    3. Configure BGP by assigning your local ASN, neighbour IP/ASN (from step 4.) and configure eBGP multi-hop.
      Figure 6. Configure BGP Settings
  6. Repeat Steps 5.a-5.c for your second Edge sdwan-edge11.
  7. From the Azure portal, complete the Route Server configuration by completing the following steps:
    1. Configure its peers, as shown in the following image.
      Figure 7. Configure Peers for RouteServer
    2. Configure Route Exchange, as explained here: Quickstart: Create and configure Route Server using the Azure portal, and as shown in the following image.
      Figure 8. Configure Route Exchange for RouteServer
  8. Verify that the four BGP sessions are UP.
    Figure 9. Verify BGP Sessions
  9. Configure VNET peering.
    Figure 10. Configure VNET Peering
  10. Verify route exchange as follows:
    1. The Spoke VNET routes that are learned from the Route Server.
      Figure 11. Verify Spoke VNET Route Exchange
    2. The ROBO Site routes that are advertised to the Route Server.
      Figure 12. Verify ROBO Site Route Exchange

Run a ping test to verify the connection between the ROBO Edge instance and VM1 or VM2.

Establish Branch-to-AVS Connectivity

This section describes the steps to integrate VeloCloud SD-WAN with Microsoft Route Server for the Establish Branch-to-AVS Connectivity use case.

Azure VeloCloud Solution (AVS) enables enterprises to set up private clouds in Azure. The private cloud contains Arista’s software defined datacenter clusters, built from dedicated bare-metal infrastructure from Azure. All private clouds are provisioned with vCenter Server, vSphere, vSAN, and NSX-T. Organizations can migrate workloads from on-premises environments, create or deploy new virtual machines, and consume Azure services from private clouds using the familiar Arista tools.

Figure 13. Establish Branch-to-AVS Connectivity

Complete the following tasks to establish branch-to-AVS connectivity:

  1. Create SD-WAN virtual Edge instances and Route Server. Refer to steps 1-10 in Establish Branch-to-Cloud Connectivity.
  2. From the Azure Portal, configure a Virtual Network Gateway for Express Route as well as a Gateway Subnet, as shown in the image below. For instructions, refer to Configure a Virtual Network Gateway for ExpressRoute.
    Figure 14. Configure Virtual Network Gateway
  3. Connect your Virtual Network to your Express Route Server:
    1. From the Azure Portal, look up your AVS Private Cloud and request an Authorization Key.
      Figure 15. Manage Connectivity of Virtual Network to Express Route Server
    2. Connect your Virtual network to your Express Route Server, as shown in the following image.
      Figure 16. Connect Virtual Network to Express Route Server

      For information, see Azure VMware Solution Networking and interconnectivity concepts.

  4. Verify the AVS subnets are advertised by the Route Server to your virtual Edge instances.

    The following image below shows the subnet Private Cloud Management Network.

    Figure 17. Verify Connectivity of Virtual Network to Express Route
  5. Log into Orchestrator and verify it is being learned by the virtual Edge.
    Figure 18. Show BGP Neighbor Learned Routes
  6. Log in to Orchestrator and then verify connectivity to the route table on the virtual Edge instances.

Run a ping test to verify the connection between the on-prem Edge instance, host1 and your workloads that reside in AVS.