Hello,
When I initially introduced the Meraki MX, we had 1 MX100 hub, which has a number of static routes and local networks terminated to it.
The device is connected to our Coe switch and has access to our primary DC and things like that. All traffic flows out via an internal Sophos firewall and then onto a managed firewall for external traffic.
All of our branch sites need to get back here to learn the routes to get to our Azure-based LAN services.
In the meantime, we have introduced two new Meraki vMX hubs in our Azure environment, and these have been setup on a brand new Azure Landing Zone and will replace the MX100. The three hubs can communicate with each other using BGP and can see each other in their respective route tables.
The issue I have is that when I remove the static routes from the MX100 hub, it causes the branch sites to lose connectivity to Azure services and also to our primary domain controller, which is located on the same site as the MX100.
Is there a way of decoupling the MX100 from the schema without causing connectivity issues with existing services?
I will provide some screenshots of the existing setup.
Existing Original Hub with static Routes to allow outside connectivity via internal Firewall
MX 100 local networks
These are the vMX hubs and their BGP settings.
The goal is to remove the MX100 so there is no visibility of it. At the moment its using iBGP to communicate with the vMX hubs. There is this option to change the mode on the MX100 from routed to passthrough or vpn concentrator
All sites are using the Hubs ,but when you check the VPN status of the branch the MX100 is still showing up - probably because of iBGP.
