This issue was resolved by associating the subnet at the server level and not the subnet Meraki is in. Instructions on Meraki sites are incorrect, for further details you can see this post.
Meraki VMx virtual appliance gateway issue
I am trying to replace our express route with a Meraki VMx virtual appliance. So far I have been able to get it working so from on-prem traffic is routed through the appliance, but on the Azure side traffic is still coming over the express route. So it is a asymmetrical routing issue.
I have created a Route Table to route traffic from Virtual Machine vnets but every time I associate the subnet with Meraki VMx I lose network connectivity and have to disassociate.
Any help would be greatly appreciated.
Azure VPN Gateway
Azure Virtual Network
2 additional answers
Sort by: Most helpful
-
arjun bhamra 1 Reputation point
2021-05-18T14:43:10.103+00:00 Hi FarkhondehEddie-1149 ,
Thank you for the info. I do actually have vMX and the site to site vpn--we are adding the Azure ER flavour to the network. Need your expertise to know, if the GatewaySubnet for Azure should be in the same RG as the Meraki vMX vnet subnet ?Any guidance for on prem Route tables with Azure ER as related to vMX would help.
Thank you
-
Farkhondeh, Eddie 96 Reputation points
2021-05-18T15:38:06.433+00:00 Arjun,
That is more of a personal preference or maybe dictated by the organization cost structure. If you want to track cost for ER I would recommend putting that in a separate RG.
I also find it cleaner when I try to look for all resources for ER if they happen to be in their own RG group.Hope this helps.