Meraki

MartinS · ‎Jan 16 2023

Thanks @sungod - we have customers where we have both the underlay connectivity routers and the Meraki appliance in Highlight. I'll look to see if I can compare in/out for these

BlakeRichardson · ‎Feb 3 2022

Dormant is a device that you have added to your inventory but not connected or has been offline for over a week. and alerting is a device thats online but has an issue i.e. network configuration or something that could be causing issues with it communicating with the dashboard properly.

Pettho · ‎Feb 3 2022

It's already done! But they can't say anything......

LearningIsFun · ‎Jan 14 2022

As far as I know that is not documented. Agree it would be nice if it was. Ones I am aware of: get-organization-appliance-uplink-statuses "active", "ready", "failed", "not connected" get-organization-appliance-vpn-statuses : "reachable" "unreachable" and "unknown"

Martin_Rowan · ‎Feb 8 2021

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

Martin_Rowan · ‎Feb 8 2021

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

Martin_Rowan · ‎Feb 8 2021

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.

Martin_Rowan · ‎Nov 29 2019

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.

Martin_Rowan · ‎Oct 17 2018

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

colo · ‎May 25 2018

It's the Organization that is limited to 5 calls per second.

Brian_P · ‎May 14 2018

I should warn you that this is also likely to result in a large increase in API requests. I can see most monitoring platforms polling every 60s, and if you get a number of customers doing this, you could get a large increase in API requests. I disagree that this method would increasing API calls. I think having this would DECREASE API calls dramatically. Right now I have to scan through every single device to pull the link information. It is a very costly API call and do this among multi organizations. Having a single call that pulls all the information would be extremely useful and much more efficient. This would decrease thousands of API calls into a single call. I really hope they expand this to include the link status's, otherwise I am stuck with making thousands of calls ( which sucks with the rate limits ) to understand if any links are down or not.

Meraki

Community

About Martin_Rowan

Martin_Rowan

API Early Access Group

Community Record

Badges

Re: New MX endpoint: Appliance uplinks usage history 🔃📊🧾

Re: Organisation device statuses "dormant" and "alerting" - What do they ac...

Re: Meraki API Performance degraded?

Re: List of all statuses returned by API?

Are Deep Links deprecated in favour of URL in API responses?

Deep Links - Don't work for MSP accounts

Deep Links - Login page mostly broken

Re: Incorrect organisation licenseState / licensedDeviceCounts retuned

Re: API Endpoint for listing details of all clients within an organisation.

Re: API Rate limit on API key or Org_id?

Re: New API Endpoint! Org-wide Device Summary

Re: Meraki API Performance degraded?

Meraki API Performance degraded?

API Endpoint for listing details of all clients within an organisation.

Re: New MX endpoint: Appliance uplinks usage history 🔃📊🧾

Re: Meraki API Performance degraded?