MX100 Hub migration to vMX's in Azure

[J_Donegan]

Hello,

We have a current MX100 Hub at our HQ site with a list of static routes listed.

One of those static routes is for our Azure LAN traffic.When one our branch site users needs to access an Azure hosted server it needs to come back to our HQ site(via Express Routes) first to learn the routes.

We have introduced 2 new Azure hosted vMXs using BGP. These new vMXs have been added to each branch site hub setup.

What is the best approach to remove the MX100 from the setup and get all traffic to contact the new primary vMX to learn the routes etc.

MX100 Hub static routes

Branch Network Hub setup

[rhbirkelund]

The fact that you've already added the two new vMX's to the Branches mean that each branch has already learned the vMX sites and their Local Networks.

You should be able to verify it by checking the branch route tables.

[J_Donegan]

When we tried removing the MX100 routes which is the same as excluding it. 
The branch traffic wasn’t able to find the routes of the Azure servers. 
we feel we need to advertise the routes on the VMx hubs but these are only vpn concentrators. 
Not sure what our next move should be. 

[PhilipDAth]

Change these to disable.

Make sure the branches still show a route to the azure subnets but via the VMXs.  Make sure Azure has a return route for the branch via one of the VMXs.

Site to site VPN firewall rules are stateful for a single VMX and not across VMX - so be careful if you use these.