Register or Sign in
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
Here to help
Member since May 8, 2018
09-14-2021
Community Record
14
Posts
4
Kudos
0
Solutions
Badges
09-14-2021
06: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
09-13-2021
02: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
02-08-2021
07: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:
02-08-2021
06:11 AM
Following the guidance at https://developer.cisco.com/meraki/build/deep-links/ I want to create a deep link to a device form within our product. However if I login using an MSP account which has multiple organisations I'm not taken to the device. Instead I'm presented with the list of orgs and the reference to the device has been lost. If once logged I navigate to the correct org and then try the deep link again then it works. However If I go to another org and then try and access the deep link again I get an error: "Sorry, we couldn't find that client. Please go back and try again." Example: https://api.meraki.com/manage/dashboard/show?mac=e0:55:3d:f4:39:17 User: devnetmeraki@cisco.com Password: ilovemeraki
... View more
Labels:
02-08-2021
06:03 AM
Following: https://developer.cisco.com/meraki/build/deep-links/ we're creating deep links directly to a device e.g https://api.meraki.com/manage/dashboard/show?mac=e0:55:3d:f4:39:17 (as DevNet Sandbox device) If the user is not already logged in, then they are shown a login page, but this appears to be visually broken and would (rightly) discourage a user from entering their credentials.
... View more
Labels:
11-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
11-25-2019
06: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
11-25-2019
03: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:
10-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
10-12-2018
01: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
09-26-2018
08: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:
05-11-2018
02: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
05-08-2018
04:01 AM
Is there a list of the potential return values for status, beyond online? "status":"online", The docs are generally lacking in detailing all the potential return values. The same is true for the interface status reported as "Active" when querying: /api/v0/networks/{{networkId}}/devices/{{serial}}/uplink
... View more
05-08-2018
02: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:
My Top Kudoed Posts
