Meraki

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_on_API · ‎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_on_API · ‎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_on_API · ‎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_on_API · ‎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_on_API · ‎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.

John_on_API · ‎Apr 6 2023

Hi @tcanty glad you got the answer, but in the future, you can see in the docs that there are no required parameters. Hope this helps! https://developer.cisco.com/meraki/api-v1/#!update-organization-login-security

John_on_API · ‎Apr 6 2023

Wow, thanks for raising this @Expo233 ! Yes, the older OpenSSL implementation does not seem to be operating as expected. This raises an interesting question, "How old an OpenSSL library should you use in production?" I honestly don't know the answer to that question but it might be a better practice to use one that was updated post-COVID. Thanks again for reporting this, and please update your OpenSSL version as described above to resolve the issue.

John_on_API · ‎Mar 29 2023

This is a great idea, @Thomas_Sterber! It would be nice to be able to get all of them across the organization.

Daniel___ · ‎Mar 28 2023

Note, I just tried the same test with 'appliance' and 'wireless' and it works as expected. Both the organizations/[org-id]/networks and /networks/[net-id], return the correct productTypes list. Maybe it is something to do with systemsManager? Although the original post didn't have systemsManager set.

John_on_API · ‎Mar 3 2023

Library version 1.30.0 includes the latest capabilities released in dashboard API release 1.30.0. Install or upgrade with: pip install --upgrade meraki Read more on GitHub.

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

John_on_API · ‎Nov 2 2022

Hi @david_n_m_bond, thanks for your interest. I don't believe the Insights team is currently publishing the scores of API specifications from different product teams across Cisco. However, as you mentioned, our spec is open source, as is the tool itself, and anyone interested could run the analysis on our open spec by standing up a copy of the application. How might the score (or the detailed analysis) be useful outside of the teams building those APIs? I'm not sure how outside developers would act on the feedback from the tool. Curious to hear your thoughts, here.

John_on_API · ‎Sep 26 2022

https://developer.cisco.com/meraki/api-v1/#!get-organization-devices-uplinks-addresses-by-device

John_on_API · ‎Sep 23 2022

Please be advised that we've identified an issue with a third-party application from Centreon that can improperly consume your API budget. This is an issue that Centreon needs to fix on their end. Unfortunately, Centreon is not an official ecosystem partner, so if you are using Centreon, please reach out to Centreon support for assistance. If you are not familiar with nor using products from Centreon, then you are not affected and can ignore this message.

Dieter · ‎Aug 30 2022

thanks! I enabled early API access and tried to do the following curl: curl -L -H 'X-Cisco-Meraki-API-Key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' -X GET -H 'Content-Type: application/json' "https://api.meraki.com/api/v1/organizations/2xxxxx/wireless/devices/ethernet/statuses" but always getting back 404 </div> <div class="content__container"> <h1 class="content__title">Page not found</h1> <p class="content__primaryText">The page you are looking for may have been moved or does not exist.</p> <p class="content__secondaryText">To log in to the Cisco Meraki Dashboard, go to <a href="https://dashboard.meraki.com">https://dashboard.meraki.com</a>.</p> </div> <div class="footer__container"> <span id="footer" class="footer__text">© Cisco Systems, Inc.</span> </div> <script type="text/javascript" charset="utf-8"> //<![CDATA[ (function () { var year = new Date().getFullYear(); document.getElementById("footer").innerHTML = '© ' + year + ' Cisco Systems, Inc.'; })() //]]> </script> </body> </html> Also I was wondering if this needs the networkID somewhere or the list always returns for the full organization? thanks Dieter

John_on_API · ‎Aug 9 2022

We've made it easier than ever to participate in the early API access program! Previously, it was necessary to allow Support to access your dashboard, and then to make a special request to have the opt-in applied to your organization, and leaving the program for an org required contacting support. No more! Please see the How do I join or leave the program? section of the OP for more info.

John_on_API · ‎Aug 4 2022

Seems like the error message could be more clear, then. You can ask Support to improve that!

John_on_API · ‎Jul 7 2022

In the latest release of dashboard API, there is a new feature in the OpenAPI spec that enables you to know if a given organization has access to early access APIs. The tag is called "x-release-stage" and appears for endpoints in the spec that are beta. To see this tag, GET the spec for the given org using the getOrganizationOpenapiSpec endpoint: GET /organizations/:organizationId/openapiSpec As an example, you''ll see this for a given beta GET endpoint, if that org has access to beta endpoints: "endpoint/path/here": { "get": { "description": "endpoint description here", // other attributes here "x-release-stage": "beta" } } If you get the spec for an org, and you don't see any endpoints marked "x-release-stage": "beta", then you know the organization is not opted into the early API access program.

Inderdeep · ‎Jul 2 2022

@John-K : Awesome !

About John_on_API

John_on_API

Community Record

Badges