Hi All, I have some vMX deployed in Azure right now and I am following this reference architecture, but I am having trouble with the following document. https://documentation.meraki.com/MX/Other_Topics/Deploying_Highly_Available_vMX_in_Azure This documentation is in my opinion quite vague. There are two diagrams shown that appear to be two different solutions, but that isn't exactly said in the document. #1 #2 I am trying to create scenario #1, but I can't actually seem to get the routing to work over the "secondary" vMX. The reason is because even with the VNET peering, the VNETs behind both vMX VNETs, still need a manual change to the route table during a failover scenario to change the next hop for traffic going to my spoke. When I configure these vMX I have to add the subnets for the VNETs behind the vMX VNETs, in my case 10.50.1.0/24, they both are configured with this, and thus they both advertise that route to the spoke.. So my question is in solution #1, is this actually more "active / active"? Or is the primary/secondary controlled via setting the hub priority in the dashboard? For example So how do we get true active passive in solution #1 without the Azure function, my guess is we cannot. Should I just build this with both vMX in the same VNET, two different public IPs with both connecting to the same private subnet and use Azure function to change the next hop in the route table?
... View more