Meraki

John-K · ‎Oct 4 2023

Hello @PSChapman, this is now available in Early Access. You can read more about our Early Access program here.

RaphaelL · ‎Sep 14 2023

Hey @PhilipDAth , I think it is now fixed in 1.37.2 https://github.com/meraki/dashboard-api-python/releases/tag/1.37.2

John-K · ‎Sep 7 2023

I, for one, am a huge fan of these changes. So much easier to find the endpoint I want!

amabt · ‎Sep 6 2023

Just adding my voice for getting that uptime in dashboard or via API

sungod · ‎Aug 30 2023

Different API call, but yes it looks like a similar change. It's great that return structures are being made more consistent, but as in the other post about device info, it'd be useful if there was some place these changes were notified or at least documented. I've now hit three different calls where a return structure change has broken automated reporting scripts and each time I've had to drop other things to investigate, fix, test and deploy. If there are more coming, it'd be much better to have some warning.

sungod · ‎Aug 30 2023

Would it be possible to give advance warning, or at least have a list of calls with modified return structures? At the moment the way I find out is when something breaks. The calls used depend on exact context, so if it's just a single network or device, that call gets used rather than org-wide. Depends how ancient the script is as well 🙂

John-K · ‎Aug 30 2023

Hi @CiscoLumen the most common data retention period for items in dashboard is 1 month, so if it 404s after 4 weeks then that seems normal! I'd recommend removing your serial number from the post above at your first convenience--it's generally best to not publish them.

John-K · ‎Aug 30 2023

Hi @xaviervalette , as @Greenberet mentioned, this statement is inaccurate: @xaviervalette wrote: But if you are using the given Webex payload (Network-wide > Alerts > Webhooks > Add or edit webhook templates)... ...you will need to host a script listening for Meraki webhooks, and then posting a message to Webex API (via your Webex Bot). Webex supports incoming webhooks out of the box. Link: https://apphub.webex.com/applications/incoming-webhooks-cisco-systems-38054-23307-75252

John-K · ‎Aug 25 2023

Hi @Rusalka thanks for reporting this. I talked to the developer of the plugin and he thinks he has a fix in the works. In the future, if you have issues with the Gsheets plugin please feel free to start a new thread, since it's unrelated to the Python library.

KonJain · ‎Aug 9 2023

Hey @david_n_m_bond , we're rolling a fix out for this. Notifying here since its a breaking change and I can post what to expect. Both latest and historical will send the response in the following format: { "ts": "2023-05-03T19:59:14Z", "metric": "remoteLockoutSwitch", "remoteLockoutSwitch": { "locked": false } }, { "ts": "2023-05-03T19:59:14Z", "metric": "downstreamPower", "downstreamPower": { "enabled": true } } Note that for historical data, there will be extra info about the SN and Network ID in each objects. This will be rolled out in a few days. Let me know if you have any questions. Thanks, Konark

Jamieinbox · ‎Aug 9 2023

Ah... I thought because I was in API v 1 I was safe, further drilling in per pic below, I see it- and now know the significance. Thanks for assistance, was super confused as it was coming up in the browser.

John-K · ‎Aug 4 2023

Heck yeah https://developer.cisco.com/meraki/api-v1/search/uplinks%20addresses/

John-K · ‎Aug 4 2023

Hm, what do you mean by 'pull client Wi-Fi connections'?

rwiesmann · ‎Jul 26 2023

Congrats to all! Well done

RaphaelL · ‎Jul 21 2023

Thanks for the clarification !

sungod · ‎Jul 20 2023

Catching up on testing after covid, this post has been edited as I went along... The old/new details arrays can differ in size, either can be zero, I've not seen either >2 The only time I see size >1 is where the first element just says it's an alert, and the second says what the alert is/was. As the call is GA now, probably too late, but if it were me I'd have simplified and put the alert description in the value rather than have detail arrays. Or are there other instances where array will be >1 ? total elements timestamp modell old name old value new name new value 4 2023-07-19T21:17:25.795000Z MS350-48LP status alerting status alerting 4 2023-07-19T21:17:25.795000Z MS350-48LP alert DHCP failure on management VLAN alert Disabled gateway (bad DNS) 4 2023-07-19T21:17:25.779999Z MS350-48LP status alerting status alerting 4 2023-07-19T21:17:25.779999Z MS350-48LP alert DHCP failure on management VLAN alert Disabled gateway (bad DNS) 3 2023-07-19T23:59:07.091000Z MS350-48LP status online status alerting 3 2023-07-19T23:59:07.091000Z MS350-48LP alert DHCP failure on management VLAN 3 2023-07-19T23:59:07.036999Z MS350-48LP status online status alerting 3 2023-07-19T23:59:07.036999Z MS350-48LP alert DHCP failure on management VLAN 3 2023-07-19T21:19:29.835000Z MS350-48LP status alerting status online 3 2023-07-19T21:19:29.835000Z MS350-48LP alert Disabled gateway (bad DNS) 3 2023-07-19T21:19:29.818000Z MS350-48LP status alerting status online 3 2023-07-19T21:19:29.818000Z MS350-48LP alert Disabled gateway (bad DNS) 3 2023-07-19T21:18:30.970999Z MX67 status alerting status online 3 2023-07-19T21:18:30.970999Z MX67 alert Disabled gateway (bad DNS) 3 2023-07-19T21:18:15.997999Z MX67 status offline status alerting 3 2023-07-19T21:18:15.997999Z MX67 alert Disabled gateway (bad DNS) 3 2023-07-19T21:17:25.653000Z MS350-48LP status alerting status online 3 2023-07-19T21:17:25.653000Z MS350-48LP alert DHCP failure on management VLAN

Techniche · ‎Jun 12 2023

It's not occuring any more as requested to confirm 😉

John-K · ‎Jun 9 2023

Hi @NJNetworkGuy100 you could do this a few ways, but it sounds like https://developer.cisco.com/meraki/api-v1/#!split-network is the simplest/easiest way. After doing this, you can delete whichever switch networks are empty. You could even re-combine the remaining networks (if desired) via https://developer.cisco.com/meraki/api-v1/#!combine-organization-networks Hope this helps!

John-K · ‎Jun 9 2023

I love the idea of subscribing to events! That said, @JasonM has the right idea -- once you've got your initial polling done, it'd be easier to find subsequent changes via polling the configuration changes endpoint -- that way you don't need to poll all the individual endpoints. This wouldn't include topology info, but otherwise, looks like the rest would be evidenced in the config changes output.

John-K · ‎Jun 9 2023

Hi @Gini_Dev_Team do you only see this issue on networks without switches? https://developer.cisco.com/meraki/api-v1/#!get-network-topology-link-layer

PhilipDAth · ‎Jun 2 2023

Negative. I just assumed the API was designed to only work with System Manager clients, and the policies that can be applied to them.

John-K · ‎Jun 2 2023

Exciting to hear this! Glad to hear you're up and running. Feel free to dive into the webinars as well when you're ready!

sungod · ‎May 10 2023

as the other endpoints are working and you're following the published documentation, i think it'd be best to open a case with support

DanielWahlsten · ‎May 4 2023

Great stuff 😀

John-K · ‎Apr 7 2023

Thanks @josua for reporting this! Please update to 1.32.1 to fix, and if you have any other issues please open an issue on GitHub.

About John-K

John-K

Community Record

Badges