Meraki MX HUB Priority change use to API(Python code)

[mskang1]

Hello, I work network engineer in South Korea.
Please understand that I post through a Papago translator because I am not good at English.
Currently, we are planning to change MX HUB priority using Meraki API.
The official document is limited to processing 10 requests per second and It seems normal only when the priority is changed by 10 per second.
I wrote the Python code in visual studio and config a test network of about five spoke.
However, unlike the official document, when the code was executed, it took 10 seconds to change the priority.
Is there a solution to this?

Thank you.

[aleabrahao]

I sent you a private message.

[BrandonD1]

Hi @mskang1,

Thanks for the post! I can confirm the APIv1 does support 10 API calls per second per organization, however this limitation is strictly related to the API Call processing and not necessarily the time it would take for an MX to update its configuration.

Are you able to confirm when processing the API command to (1) single hub, that there is no delay experienced? Also if you could confirm the API endpoint you're referencing it would be greatly appreciated!

[Alisdair Mckeand]

Hi @mskang1

Is it the Hub / Concentrator priority you are looking to amend, i.e. the below area on the Dashboard UI? Only as we as a dev team were looking at this early last month for a few retail customers and there is very limited API coverage for MX Firewalls in VPN Concentrator / Passthrough mode, this one didn't have a support operation we found so made a feature request, it is also acknolegde by MX PM that there is limited API coverage for MX Firewalls in this mode. Be interesting to know which API endpoint you utilising like @BrandonD1 has mentioned 🙂

[Philip D'Ath · Accepted solution]

It is normal for the change to take some time to take effect. 10s is quite reasonable.