Meraki

JasonM

I don't believe this to be due to TLS version compatibility as the TLS handshake wouldn't complete and thus wouldn't have an expectation any payload, partial or otherwise, would be delivered from the server. This can be easily verified in a Wireshark packet capture. Image attached illustrates this where the client sends an API request with TLSv1.1 and the server responds with a descriptive error followed by the termination of the TCP session.

JasonM

To add to what @RaphaelL mentioned regarding sensitive information, I'd include the Organization ID to that as well.

JasonM

Very humbling to be included in such a knowledgeable group of community members. Congrats to you all and thank you for all your contributions! @from_afar @Cid7 @PhilipDAth @cmr @alemabrahao @DarrenOC

JasonM

Hi @mlaskowski-r7, My lab shows the following for the MS and MR, respectively. Hopefully this helps. Cheers! SNMPv2-MIB::sysDescr.0 = STRING: Meraki MS120-8LP Cloud Managed PoE Switch SNMPv2-MIB::sysDescr.0 = STRING: Meraki MR46E Cloud Managed AP

JasonM · ‎Mar 21 2024

It looks like you are referencing netnumberhere (networkId?) in the URI but the call takes the organizationId for this endpoint. That is likely the issue if I'm reading that right.

JasonM · ‎Jan 26 2024

Hi @jsteurs and happy Friday! One way that should work for you is to iterate through all of your Networks using the getNetworkFirmwareUpgrades endpoint. This will allow you to make comparisons to what firmware is currently installed vs which firmware are currently available, specifically which is stable, for your need. Additionally, it will show you if any firmware upgrade is already scheduled to be done. If there is a discrepancy between what is stabled vs what is currently installed (with no pending upgrade) then you can use this logic to use the updateNetworkFirmwareUpgrades endpoint to schedule that upgrade to the current stable version.

JasonM · ‎Oct 3 2023

When you import the Meraki Postman collection it has a configured test for JSON Magic that is used to help visualize the results in tabular form. What you can do to get around this is save the particular endpoints to a new folder to be used just for your flow so that it doesn't complicate the Postman Flow. Be sure to remember to add your API key (or environmental variable) into the settings for the new folder. Alternatively, if you are fine without the options for visualizations you can just remove that from the tests from the Meraki collection folder.

JasonM · ‎Sep 28 2023

One somewhat rarely mentioned gem that I like to use is to open Postman and generate a snippet for whatever language I need the line of code for. Very nifty in certain situations. https://learning.postman.com/docs/sending-requests/generate-code-snippets/

JasonM · ‎Aug 14 2023

The field with key of "id" has a value that is the key of "shortName". "id" will have a value that is something like "4321" which will be a unique ID for that firmware. There is an example body from the reference doc for this endpoint. https://developer.cisco.com/meraki/api-v1/update-network-firmware-upgrades/

JasonM · ‎Jun 16 2023

Hello cumoon, You could also use in addtion to the other mentioned endpoint the getNetworkApplianceWarmSpare endpoint by iterating through appliance networks if you need to know which specific device is primary and which is the spare.

JasonM · ‎Jun 12 2023

Hello aurelijanob, Be sure to see if the network is bound to a template as such networks will have their alerts configured at the template level rather than the network level.

JasonM · ‎Jun 12 2023

Hello Aponte, If you only need loss % and latency then the uplink loss and latency endpoint will provide that.

JasonM · ‎Jun 8 2023

From the supported resources list for action batches it looks like you will want to use /organizations/{organizationId}/switch/devices for the resource path with the operation of clone.

JasonM · ‎Jun 5 2023

Another idea may be to utilize webhooks for the configuration settings are changed alert so to leverage a push method with details of the network and the details of the change made.

JasonM · ‎Apr 24 2023

Hello david_n_m_bond, Perhaps deep linking could be useful for you which allows direct linking to orgs, networks, devices, and summary reports.

JasonM · ‎Mar 13 2023

Just a suggestion but would webhooks be useful in this use case? That way it is a push method rather than pull. As long as you have alerts setup for all wireless networks to notify when an AP goes offline you should be able to track that on your required interval and calc the time difference between the down and up notifications for each serial and/or mac address. It will save on your API budget as well.

JasonM · ‎Mar 8 2023

The only endpoints that will give you any such an indication (which will be status, as you indicated, and details of the connection) are the following: https://developer.cisco.com/meraki/api-v1/#!get-organization-appliance-uplink-statuses https://developer.cisco.com/meraki/api-v1/#!get-organization-uplinks-statuses

JasonM · ‎Mar 3 2023

The data field ownerEmail is an option to provide in the fields parameter that is of type array. It only allows to display additional fields in the returned response body and is not a query parameter to filter on a specific value. You will have to return all the results first, including the ownerEmail field, and then filter the response accordingly.

JasonM · ‎Feb 28 2023

@sungod wrote: webhooks, syslog, snmp, netflow Love the callout for all the integration points. +1 on this answer.

JasonM · ‎Feb 16 2023

The Meraki collection for Postman comes with a utility called JSON Magic that will allow you to export the results to a csv file. From there you could manipulate the data as needed. https://developer.cisco.com/meraki/build/meraki-postman-collection-getting-started/#!overview/visualize-with-json-magic

JasonM · ‎Dec 30 2022

There is an event log event type for Primary Uplink Status Change that you could use. I assume that your primary interface is WAN1. An event will be generated upon failure and again for when it is restored. The event type to filter by is failover_event. https://developer.cisco.com/meraki/api-v1/#!get-network-events

JasonM · ‎Dec 22 2022

You can run the API call below to get results of GET calls made in the org. https://developer.cisco.com/meraki/api-v1/#!get-organization-api-requests

JasonM · ‎Dec 5 2022

The endpoint below can be used if the IP address is configured statically: https://developer.cisco.com/meraki/api-v1/#!get-device-management-interface

JasonM · ‎Dec 2 2022

In addition to the other great comments here, it looks like it is doing a redirect because your base URL is https://dashboard.meraki.com rather than https://api.meraki.com. Try changing the base URL and see what that results in.

JasonM · ‎Nov 17 2022

No worries! Glad you got it working.

About JasonM

JasonM

Community Record

Badges