Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About Martin_Rowan
Martin_Rowan
Getting noticed
Member since May 8, 2018
Nov 26 2022
Community Record
27
Posts
22
Kudos
0
Solutions
Badges
Feb 3 2022
9:33 AM
The endpoint: /organizations/{organizationId}/devices/statuses/overview has return values: "online": 5, "alerting": 2, "offline": 0, "dormant": 2 To me, online and offline are self-explanatory, but what situations would set the state to dormant or alerting? Specifically in the context of an Appliance (Meraki MX) I'm trying to make a determination of if either of these states should be treated more like online or offline or something else. Thanks
... View more
Jan 24 2022
3:28 AM
1 Kudo
Can you confirm which API Endpoints you're using? We have an issue where some times API requests don't respond before an internal timeout (60 seconds), I sometimes see the same issue using just PostMan, as a result, we changed our implementation to have an additional retry policy, such that if we don't start to get a reply within a second, we drop that request and make it again (after a short delay). This has improved the overall reliability significantly. Not sure if you're hitting the same issue.
... View more
Jan 21 2022
8:30 AM
1 Kudo
@AutomationDude Checked again and response times are fine using api.meraki.com not getting timeouts or seeing very slow replies.
... View more
Jan 21 2022
6:47 AM
Indeed performance seems to have improved dramatically. Hopefully, we won't see the gradual decline I detected since 11th Jan.
... View more
Jan 21 2022
12:48 AM
4 Kudos
Not sure if this will help some people in the short term. But I make the request directly to the shard endpoint for example: https://n376.meraki.com/api/v1/ then responses are back in milliseconds, whereas going via the API gateway https://api.meraki.com/api/v1 is where it's slow.
... View more
Jan 20 2022
12:00 PM
2 Kudos
Is a bulk endpoint for this data going to be added, so that I can get the uplink data for all the networks in an organisation without needing to make per network calls?
... View more
Jan 20 2022
9:54 AM
1 Kudo
Well the more people that raise tickets the better I guess. Slow responses are annoying, incomplete/truncated responses (invalid json) are something else. An example below took nearly 3 mins and sent ~48k of the 160k expected. The SSL handshake was very long and unusual in that request, most of the time it appears to be the download. It's definitely a lot slower during 8am-9pm timeframe, early this morning a call was still slow 5 seconds, but as the day progresses it has become more erratic and flaky.
... View more
Jan 20 2022
5:42 AM
1 Kudo
Thanks, I've opened a support case.
... View more
Jan 19 2022
11:43 AM
4 Kudos
Hi, Is there an ongoing issue with the performance of the Meraki Dashboard API? We've developed software for a number of Meraki SD-WAN customers and in recent days have been experiencing issues with a significant increase in the API reliability and response times. Whilst requesting data from various endpoints we're seeing issues, which can also be reproduced in Postman Some requests are made and never responded to Some requests respond with a 200 header, but then don't appear to respond with any payload data. Requests that do succeed are taking a lot longer than expected, sadly I don't have precise figures to be able to quantify this, as an example query for the 1st page (300) VPN statuses {{baseUrl}}/organizations/:organizationId/appliance/vpn/statuses takes between 4 and 25 seconds (at 7-7:30pm UK time today). Earlier today I experienced times of > 1min. This problem was seen with multiple unrelated customer organisations. For example one his hosted on n376.meraki.com and another on n271.meraki.com Looking at some historical data this issue appears to have started around 11th Jan and has been getting progressively worse. It also appears to be worse from 8am until 8-9pm. I'm not aware of anywhere to see service status or performance if there is such a thing. But it looks very much like a load issue
... View more
Jan 14 2022
12:13 AM
Thanks John, my last point was a more general one of knowing what the valid set of values are for various statuses. For example: get-organization-appliance-uplink-statuses an uplink can be "active", "ready" but what else? get-organization-appliance-vpn-statuses a tunnel reachability can be "reachable" and "unreachable", anything else?
... View more
Sep 14 2021
6:36 AM
Thanks for the link, missed that section of the docs, though I'm cautious if the docs would reflect all possible states. I'm curious if device status is more and online/offline for example does the status change when it's rebooting, upgrading. or even in some unknown state.
... View more
Sep 13 2021
2:31 AM
Hi, The API documentation is pretty good but lacks details of all return values for what I suspect are enums for the state. Specifically: For device status: {{baseUrl}}/organizations/:organizationId/devices/statuses ... "status": "online" ... What are the valid return values? online, offline, ...? For uplink status on an SD-WAN appliance: {{baseUrl}}/organizations/:organizationId/uplinks/statuses ... "status": "active" ... What are the valid return values for this? active, ready, ... ??? Thanks, Martin
... View more
Feb 8 2021
7:03 AM
Is the method of deep linking described in: https://developer.cisco.com/meraki/build/deep-links/ still the correct way of doing it? Or should/can we use the URL property that is included in the API responses: e.g. https://dashboard.meraki.com/api/v1/networks/{{networkId}}/devices returns: { "lat": 37.4180951010362, "lng": -122.098531723022, "address": "", "serial": "Q2MD-Y5QK-LAK2", "mac": "e0:cb:bc:51:28:f2", "lanIp": null, "url": "https://n149.meraki.com/DNENT2-axxxxxxym/n/hvBc4avc/manage/nodes/new_list/247165642418418", "networkId": "L_646829496481107582", "tags": [], "model": "MR53", "firmware": "wireless-27-5-12", "floorPlanId": null } Where the URL property appears to link directly to the device, without being redirected through api.meraki.com
... View more
Labels:
- Labels:
-
Dashboard API
Nov 29 2019
12:35 AM
1 Kudo
I've opened a support case with Meraki, will see if they can get to the bottom of what's going on. The API call was looking really promising for being a simple/lightweight method to get an inventory and count of device types without needing to request details of all devices within the org.
... View more
Nov 25 2019
6:04 AM
Looking at the inventory change log for when we applied the license (on 21 Nov) , it shows "Assigned 1 MX68W device licenses", so yes I believe we're using per-device licensing. But I'd still expect the org license status to reflect the number and type of licensed devices. We only have a couple of devices as needed them for some testing outside of the devnet/sandbox environment.
... View more
Nov 25 2019
3:30 AM
Hi, We're developing some API integration with Meraki for SD-WAN devices. We have a MX68W and a MX60 in our organisation, with only the MX68W currently licensed. I'd expect the call: https://api.meraki.com/api/v0/organizations/:organizationId/licenseState to list the MX68W in the "licensedDeviceCounts" however what I'm seeing returned is: { "status": "License Required", "expirationDate": "N/A", "licensedDeviceCounts": {} } Calling https://api.meraki.com/api/v0/organizations/:organizationId/licenses shows the licensed device. What is needed to get the correct licensedDeviceCounts returned?
... View more
Labels:
- Labels:
-
Dashboard API
Oct 17 2018
12:09 AM
Hi thanks for the link to GitHub. The approach taken in the Python script is iterative. By this I mean it queries for a list of networks (for a given org ID), then for each network it gets all the devices, then for each devices it then gets all the clients, then for each client it collects data. This is what we already do today (roughly). What I was requesting from Meraki with my initial post, was to have an API endpoint which provided the information in bulk for a given organization or network, without needing to make API calls for each client. If there is a better way of making a API enhancement request, I'd be happy to explore that route. Thanks Martin
... View more
Oct 12 2018
1:18 PM
What specifically in the docs were you thinking indicated a call which met the requirements above? We have a working implementation, but would welcome the addition of an API endpoint which reduced the number of round trips.
... View more
Sep 26 2018
8:13 AM
3 Kudos
Our integration with the Meraki Dashboard API requires us to get the network usage for each client, for each WiFi Access Point in an organization. This requires us to make a separate call for each device to fetch the client, which is slow, prone to throttling by the API, and puts unnecessary load on the Meraki servers. We would like to request an additional endpoint to enable us to do this without making multiple calls, or some guidance on if there is an existing API/functionality that would help us achieve this goal more efficiently. For example: Lists all the clients for an organization, including the serial number of the device the client is connected to. GET /organizations/[id]/clients Parameters timespan - The timespan for which clients will be fetched. Must be in seconds and less than or equal to a month (2592000 seconds). Sample Response Successful HTTP Status: 200 [
{
"usage": {
"sent": 138.0,
"recv": 61.0
},
"id": "k74272e",
"description": "Miles's phone",
"mdnsName": "Miles's phone",
"dhcpHostname": "MilesPhone",
"mac": "00:11:22:33:44:55",
"ip": "1.2.3.4",
"vlan": "",
"switchport": null,
"serial":"Q234-ABCD-5678"
}
] Critical fields for our integration are: usage (sent/recv) description mac ip serial (i.e. the AP the client is connected to) Thanks Martin
... View more
Labels:
- Labels:
-
Dashboard API
May 11 2018
2:53 AM
Would be good to get a reply from Meraki, as it impacts the design of the integration we're working on for MSPs. Thanks
... View more
May 8 2018
2:46 AM
The documentation here states: Note: Call volume is limited to 5 calls per second (per organization) I wanted to confirm that using an MSP User/API Key that the rate limiting occurs based on the org_id in the query and not on the API key being used. Thanks
... View more
Labels:
- Labels:
-
Dashboard API
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 4 | 10332 | |
| 4 | 10562 | |
| 3 | 5943 | |
| 2 | 6073 | |
| 1 | 10033 |
© 2024 Cisco Systems, Inc.
