We have deployed 2x 2 vMX pairs in Azure and AWS for a customer, all in concentrator mode. At the Azure side we are using an Azure Route Server (ARS) for the routing part, in AWS the 'Cloud WAN tunnel-less connect' setup is used.
All is working fine for the Auto-VPN spoke sites, they can access the Azure and AWS subnets perfectly. Since more and more services are moved to Azure, we now ran into the issue that we can't reach AWS subnets from Azure and Azure subnets from AWS.
The AWS vMX's do have routes for the Azure subnets in their route table and the Azure vMX's do have the routes for the AWS subnets in their route table. Unfortunately these routes are not distributed to the Azure Routes Server or the AWS 'Cloud WAN Tunnel-less connect' solution. In short: eBGP learned routes are not distributed to other eBGP peers.
Meraki support confirmed this, and advised to change the vMX's to NAT/Routed mode instead of concentrator mode. With the limited NAT mode which is currently available in version 18.211.5, this is not an option due to the full tunnel requirement described in Meraki documentation.
Were are now considering to upgrade to the stable release candidate version 19.1.7 but it is hard find correct information if this version offers a solution for our case (searched in documentation and release notes). We were promised that this version would offer the same functionality like the physical MX counterpart.
- Can we upgrade from the current version to 19.1.7 and will the LAN NIC pop-up in the VM? Or should we deploy a new vMX?
- Anyone who ran into the same issue, and maybe found a solution?
- Anyone already running 19.1.7? (Already read the 19.1 POC post of user ShaunB93)
