I would install a small linux server / raspberry pi on the remote site. there is a tool etherwake which will send the WOL packet on the subnet. Depending on the user you can either let him use the server via ssh to wake his machine or just do a simple web server which will invoke the etherwake command. ... View more

Not directly, but you can implement SSO with SAML. This should do the trick. ... View more

Delete the api key and generate a new one. After that wait a few minutes before you are testing it out. I had this issue once too and I've opened a case for this. The support technician told me, that there was a problem with the replication of the api key. With deleting/generate the replication will be triggered again. The new key was working fine then. ... View more

Exactly. maybe we should also change it to a time range. E.g. 1 second up to  random(concurrent_requests_counter/2)   The Problem with a fixed value is that you are just postponing the next rate limit.   E.g 100 requests are getting sent at once. 10 are going through -> 90 requests would currently be send 60s later -> 10 are going through.....   So you are hitting the rate limit again and again and again.   With a range we would spread the requests over the time period and not hit the rate limit all the time (even with an increased concurrent_request limit)   ... View more

Actually it is the same speed as node.js your python code takes also about 6 seconds. I've made an additional code to get the network. This created the additional seconds (200x10 requests) ... View more

I've found the issue.   Believe it or not it's an nginx/configuration issue. You are not hitting the api rate limit here. Instead you are hitting the rate limiter of the nginx proxy. With the default configuration the python api will wait 60 seconds for the next retry.   I've created 200 test orgs with 10 networks. When I set the nginx_429_retry_wait_time & retry_4xx_error_wait_time to 1 the whole run took 22 seconds with maximum_concurrent_requests=3 and ~6 seconds with maximum_concurrent_requests=200 with your test methods.   @chengineerI know this parameter is set to 60 seconds as a protection to the nginx, but do you think it would be possible to decrease it per default? From a script performance perspective it is a lot faster to hit the nginx & shards with as much concurrent requests as possible and just handle the rate limits (nginx 1 seconds, shard whatever will be returned in the header), than limiting the concurrent requests to 3. This is a sample code I've used for my tests     async def processNetworks(aiomeraki: meraki_v1.aio.AsyncDashboardAPI, org): try: networks = await aiomeraki.organizations.getOrganizationNetworks(org["id"]) netTasks = [aiomeraki.networks.getNetwork(net["id"]) for net in networks] for task in asyncio.as_completed(netTasks): n = await task print(n["name"]) except meraki_v1.AsyncAPIError as e: print(f"processNetworks: Meraki API error: {e}") except Exception as e: print(f"processNetworks: error: {e}") return async def max10(): async with meraki_v1.aio.AsyncDashboardAPI( api_key=api_key, base_url="https://api.meraki.com/api/v1", suppress_logging=True, maximum_concurrent_requests=10, nginx_429_retry_wait_time=WAIT, retry_4xx_error_wait_time=WAIT, maximum_retries=200 ) as aiomeraki: # Get list of organizations to which API key has access orgs = await aiomeraki.organizations.getOrganizations() for org in orgs: print(org["id"] + " " + org["name"]) orgTasks = [processNetworks(aiomeraki, org) for org in orgs] for task in asyncio.as_completed(orgTasks): await task     Very interesting are the speed results here:   max3 took 159.34725640000002 seconds max10 took 65.28876129999999 seconds max50 took 39.83993439999999 seconds max200 took 29.977361000000016 seconds The wait time parameters were set to 1 second on each test run. The numbers after "max" are the maximum_concurrent_requests   ... View more

@PhilipDAth wrote: The node.js SDK has no rate limiter.  node.js is a greedy async engine, it starts executing stuff as soon as you request it.  the meraki module in nodejs uses "bottleneck" in the background -> https://www.npmjs.com/package/node-meraki   @PhilipDAth wrote: Python is a lazy async engine, it doesn't start processing async requests until you call the event loop. that purely depends on how you are using it. When you are using a simple "await" then it is like that yes, but you could also use asyncio.ensure_future instead. ... View more

I think your conclusion is wrong here. I havn't used meraki with node.js yet, but I thinkt that there are some differences here on how ther meraki modules are handling the ratelimit in python and node.js   How did you configure the rateLimiter in node.js? Are you using scopes in node.js?   the current async implementation in python uses a simple concurrt request counter, and if there are too many requests open, then it will wait for 0.3 seconds and check again (maybe we should lower that value).   the nodejs meraki module has the option of a scope, so the concurrent counter gets counted for each scope. I had a similiar idea, when I've implemented the counter. My problem here was, that I wanted to do it automatically, but you don't have the "orgId" in each request, so i've abonden the idea. I never thought of letting the programmer add it via "scope". At the moment you could achieve something similiar with creating the AsyncDashboardAPI object for each organization.   You could also speedup your dependencies: just run pip install aiohttp[speedups] and see if the script runs faster now. ... View more

Congrats @PacerX ! ... View more

After one week we are already having people in Tier 3. @MeredithW I think we need more Swag... I mean Tiers here =D ... View more

I've added a new IDEA in the early developer community. API related wishes are getting more attention there. If someone else needs that information, then there is some tricky workaround. You can extract the subnet settings from the dashboard changelog and use the latest one.     ... View more

I'm not talking about the generated one. I want the address settings from which they are generated ... View more

Empty IP Addresses 😞 ... View more

Do you know how to get the address/vlan configuration over the api from the template? ... View more

Thank you very much 😃 ... View more

I haven't tried it, but from the docs it should work like that: data_wan1 = {'wanEnabled': 'not configured', 'usingStaticIp': False, 'vlan': None} data_wan2 = {'wanEnabled': 'not configured','usingStaticIp': True,'staticIp': '1.1.1.1','staticSubnetMask': '255.255.255.252','staticGatewayIp': '1.1.1.2.','staticDns': [ '8.8.8.8', '8.8.8.8.']} 'vlan': None} m.management_interface_settings.updateNetworkDeviceManagementInterfaceSettings(networkID,mx_serial_number, wan1=data_wan1, wan2=data_wan2) ... View more

every method which starts with "get" will read the data from the dashboard. You won't be able to update the settings with this. In your case you will need updateNetworkDeviceManagementInterfaceSettings def updateNetworkDeviceManagementInterfaceSettings(self, networkId: str, serial: str, **kwargs): """ **Update the management interface settings for a device** https://api.meraki.com/api_docs#update-the-management-interface-settings-for-a-device - networkId (string) - serial (string) - wan1 (object): WAN 1 settings - wan2 (object): WAN 2 settings (only for MX devices) """   ... View more

At the moment it's more for statistical reasons and personal interest. I don't need to track it instantaneous. It would be enough to have the value which is in the dashboard (which gets updated every 1-2 minutes I think). I would pull the data every 1-5 minutes. From the API side we currently have GET/devices/{serial}/switchPortStatuses which is currently providing most of the statistical data (e.g. TX/RX, CDP, ... ). PoE is just missing here. ... View more

Exactly. I want to monitor the PoE usage of the ports. ... View more