Has there been any update to this. I am working on a similar project. Just kind if getting my feet wet in api and python ... View more

No problem @Maccaa31 I am sure this would work for you, as worked for me Answering your question, the MPLS should go to the internet port(1 or 2) on both MX devices (look at the diagram).The MX devices will treat it as an internet link, as long as you are allowing the Meraki cloud IPs from the MPLS. Technically you would be cheating the MX devices to think this is an internet link. Do not forget to allow ICMPs to Google 8.8.8.8 ... View more

That's what I thought to. So I prepared the code via the sample on the Meraki developer page https://developer.cisco.com/meraki/api/#/python/api-endpoints/switch-ports/update-device-switch-port added my api-key and run it, same error occurred.   I will now analyze it a bit deeper, as I've answered Philip.   Thank you. ... View more

Are you in Windows? Try accessing it via IE and see if UAC is interfering. Once I'd told IE to allow it, I was then able to pull copies into Postman via Chrome. ... View more

Regarding updating multiple VLANs in one call;    You might want to checkout Action Batches, which have recently been added to the API. They are designed to combine multiple operations into a single request. This is good for adding VLANs, updating switch ports, managing policies, etc. https://developer.cisco.com/meraki/api/#/rest/guides/action-batches     ... View more

Nope you're good, I was miss reading your diagram.    So with your original setup, your AP's are going to pull an address from your ADSL router because you have ports 3-5 set as native vlan 1.  You are also trying to pass VLAN 1 to your clients for DHCP.  We know this doesn't work because you can't pass tagged traffic of the same vlan as your native, the port will drop the tags.  If you change the native vlan on ports 3-5 to say vlan 5, you would be able to pass vlan 1 traffic over that interface and route the way you would like.  You would need to make sure that you have a DHCP scope tagged to vlan 5 though as the meraki APs still need to pull an internal IP from somewhere.  This is where I was going with the "management" VLAN.   TL;DR The AP's need an IP that is not pulled from the VLAN you are tagging your clients as. ... View more

Switchport set as access instead of trunk?? ... View more

You're welcome.   For the regular API's the documentation is the postman collection: postman.meraki.com   For the Python library, I didn't see decent documentation that would have mentioned this. But I came to the correct code by looking at both what the API expects and what was in the source code of the python library. Then just testing. Unfortunately the errors aren't always very explanatory. ... View more