Moving ExR Circuits from VNG to Azure Virtual WAN, and minimise any potential down-time?

Ajaz Nawaz 21 Reputation points
2023-02-09T20:01:32.9566667+00:00

We have single region Azure setup with standard Hub-n-Spoke VNETs. Single VNG with ExR. Now wish to add Azure vWAN. How to go about 'shifting' the ExR circuits from VNG to vWAN [without disruption] ?

What are the high-level steps to 'move' routing functionality away from UDRs etc. to vWAN (custom and default route tables)

Thanks in advance !

Azure Virtual WAN
Azure Virtual WAN
An Azure virtual networking service that provides optimized and automated branch-to-branch connectivity.
197 questions
Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,476 questions
Azure Migrate
Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
745 questions
Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,267 questions
Azure ExpressRoute
Azure ExpressRoute
An Azure service that provides private connections between Azure datacenters and infrastructure, either on premises or in a colocation environment.
342 questions
0 comments
Accepted answer
  1. KapilAnanth-MSFT 39,461 Reputation points Microsoft Employee
    2023-02-10T05:15:05.7466667+00:00

    @Ajaz Nawaz

    Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

    I understand that you are planning to migrate from classic Hub and Spoke Model to vWAN.

    This should be done in a maintenance window.

    • Create a vWAN, vHub and a ExpressRoute Gateway on the vHub.
    • Now, create a connection between ExR Gateway and the existing ExR Gateway
    • Refer: Create an ExpressRoute association to Virtual WAN
    • This is, of course, assuming that the ExpressRoute Circuit SKU and the existing number of connections allows you to establish a new connection.
    • Now, you will have two Hubs, one being VNet with Gateway(vNetHub) and the other being the vWAN's Hub connected to your OnPremises.
    • Now, this is where a maintenance window is required.
    • You have to remove the Peering between the Spokes and vNetHub and connect the Spoke to the vHub one by one.
    • During this time, while there is no peering/connection with Spoke, you will experience connectivity problems to the Spoke VMs
    • Post this, delete the ExR Connection on the vNetHub, then delete the ExR Gateway and then either delete or add the vNetHub to the vHub depending upon your requirement.

    I hope I was able to provide a high-level summary of how to do this migration.

    Also refer : Migrate to Azure Virtual WAN

    Please let me know should you require further assistance on this.

    Thanks,

    Kapil :)

    Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest