EMAIL SUPPORT

dclessons@dclessons.com

LOCATION

US

SD-WAN VeloCloud Network Migration

SD-WAN VeloCloud Network Migration

In this topic we will see how a traditional WAN is transformed to SD-WAN , what are all step by step procedure that is to be used for SD-WAN network Migration. Let see how the topology looks like before SD-WAN migration.

In this above topology, Branch 1 is connected to MPLS and one legacy site is also connected to MPLS. Two DC which are also connected to MPLS and Internet and also to each other via DCI link.

  • Two identical active/standby DCs with DCI
  • Branch 1 will eventually replace CE with SD-WAN but no change to MPLS circuit

Step 1: Add HUB VCE and activate in DC1 & DC2

  • Activate the hub VCE and enable BGP with the L3 switch, by doing this this HUB will be managed by Orchestrator and will peer with Global gateway for Control plane. It will build the tunnel with gateway and start running BGP with L3 switch in DC.
  • Best practice: When you start, filter the BGP routes from SD-WAN toward your network, so that you start learning any prefixes but do not inject in DC network until all SD-WAN is ready.

Step 2: Add Branch VCE and Activate

Activate the branch VCE and enable BGP with L3 switch, by doing so Branch VCE will form the SD-WAN overlay tunnel to DC1 and DC2 HUB VCE via internet link



Step 3: Building the overlay tunnel and enable routing at branch

GENERAL FAQ

The main objective of SD-WAN migration is to transition from a traditional MPLS-based WAN to an SD-WAN architecture without disrupting existing connectivity. During migration, MPLS, Internet, and SD-WAN overlays can operate together so that traffic is gradually shifted to the new SD-WAN fabric in a controlled manner.

The first step is deploying and activating the Hub VCE devices in both data centers. These Hub Edges connect to the Orchestrator, establish secure tunnels to Gateways, and form BGP peering with the Layer 3 core to exchange routing information.

BGP route filtering prevents SD-WAN routes from being prematurely injected into the data center network. Initially, the SD-WAN overlay can learn routes for validation purposes, but advertisements toward the production network are restricted until the migration is fully tested and stable.

When the Branch VCE is activated, it automatically establishes secure overlay tunnels to both Hub VCEs over the Internet links. After this, BGP can exchange branch prefixes across the SD-WAN fabric, enabling proper route advertisement and inter-site connectivity.

Routing integration takes place after secure overlay tunnels between the branch and data centers are successfully established. At this stage, traffic can dynamically select between MPLS and SD-WAN paths based on routing policies and link quality conditions.

This page explains the fundamental migration workflow from traditional WAN to SD-WAN. For detailed production-grade design, dual data center migration models, routing control strategies, and real-world troubleshooting scenarios, you can explore the complete course available on the DCLessons platform.

Comment

  • GA

    This is a very detailed course on sd wan velocloud network migration. It will help you provide develop knowledge, skills, and abilities to deploy VMware SD-WAN with the help of VeloCloud. They have covered a step-by-step procedure that is to be used for SD-WAN network Migration. This has helped me gain a lot of knowledge.


  • OL

    This is a very important course for those in the network operations team with SD-WAN solutions. They have covered everything needed to build an SD-WAN environment. I have gained a lot from this course. My boss has considered promoting my designation. Thanks to the DC lesson and this amazing course.


LEAVE A COMMENT

Please login here to comment.