Lambda Meraki Route Extraction Problem

[NickB118]

Our existing SD-WAN topology is Hub and Spoke, with the Hub currently set to a pair of physical MX appliances in an on-prem DC and both vMX's set as spokes.

When the below Lambda function ran with our topology, no routes were extracted at all, so no routing updates were made.

I wondered whether this might be to do with what the get_all_vpn_routes function is expecting the topology to be like?

quickstart-cisco-meraki-sd-wan-vmx/functions/source/lambda_function.py

Line 57 in 510a621

def get_all_vpn_routes(dashboard, org_id, vmx1_id, vmx2_id):

[myhomenwlab]

I have no way of knowing the design philosophy, but reading the code, the following conditions must be met.

• vMX must be Hub.

• Spoke MX on the Branch side specifies vMX as Hub.

In short, only Hub & Spoke with vMX as Hub is supported.
In other words, Hub & Spoke with MX as Hub is not supported.

[goopilot]

Yes, we have same issue. And I see that it's not only us #24