Meraki

DexterLaBora · ‎Apr 17 2019

Should be working, just tested. Maybe share your script snippet without key? curl -X GET \ https://api.meraki.com/api/v0/networks/L_1234567890/syslogServers \ -H 'X-Cisco-Meraki-API-Key: <APIKEY>' [ { "host": "1.2.3.4", "port": "443", "roles": [ "URLs", "Wireless event log" ] } ]

DexterLaBora · ‎Apr 16 2019

We plan to fix the incorrect type returned in the `/organizations` response. This was the only place where this ID appeared as a `number`. It was stated in our documentation that the org ID and all other IDs should be treated as a strings, but this ID was a little ambiguous with the JSON response. This should not break any normal code, as long as you ultimately used the org ID as a string. Stay tuned, for an update shortly. Once it's implemented, we will make an announcement in this community.

DexterLaBora · ‎Apr 5 2019

This was noted and we are investigating the best way to address the issue. Essentially, the organization ID should be a String but is being sent as a Number. If we switch the type, it's technically a breaking change. That being said, it doesn't do you much good if the number is getting mangled by JavaScript. Stay tuned for updates on this. FWIW, I have used json-bigint in the past to parse the JSON as a workaround.

DexterLaBora · ‎Mar 7 2019

FWIW, I tried sending the data directly to the test results, but it looks kind of silly.

DexterLaBora · ‎Mar 7 2019

The "test results section" will simply return a status success/failed with a message string. If you are wanting to use the resulting data response, you could set the data to an environment variable. More Info: https://learning.getpostman.com/docs/postman/scripts/test_examples/ var jsonData = JSON.parse(responseBody); var filteredData = jsonData.filter(function(item) { if (!item.tags) { return } return item.tags.includes(" Teleworkers"); }); console.log("data", filteredData); pm.test("Status code is 200", function () { pm.response.to.have.status(200); pm.environment.set("filteredNets", JSON.stringify(filteredData)); }); After running my test, the new Env variable showed up and had my data (from the sandbox org)

DexterLaBora · ‎Mar 7 2019

This is the JS solution to filtering the JSON array based on network tags within Postman. I'm not clear how you want to use the data, so I am just printing it to the console. (Menu -> Developer --> Show DevTools (CurrentView) ) var jsonData = JSON.parse(responseBody); var filteredData = jsonData.filter(function(item) { if (!item.tags) { return } return item.tags.includes("KIT"); }); console.log("filteredData", filteredData); My Local Test As a more generic HTML/JS solution var data = [{ "id": "redacted1", "organizationId": "xxx", "name": "Location1", "timeZone": "Europe/Paris", "tags": " KIT0003 OSI ", "type": "combined", "disableMyMerakiCom": false, "disableRemoteStatusPage": false }, { "id": "redacted2", "organizationId": "xxx", "name": "Location2", "timeZone": "Europe/Paris", "tags": " KIT0006 OSI ", "type": "combined", "disableMyMerakiCom": false, "disableRemoteStatusPage": false }, { "id": "redacted3", "organizationId": "xxx", "name": "Location3", "timeZone": "Europe/Paris", "tags": " OSI ", "type": "combined", "disableMyMerakiCom": false, "disableRemoteStatusPage": false } ] newData = data.filter(function(item) { if (!item.tags) { return } return item.tags.includes("KIT"); }); console.log(newData); //Print to HTML page document.getElementById("demo").innerHTML = "<pre>"+JSON.stringify(newData,undefined, 2) +"</pre>" Results [ { "id": "redacted1", "organizationId": "xxx", "name": "Location1", "timeZone": "Europe/Paris", "tags": " KIT0003 OSI ", "type": "combined", "disableMyMerakiCom": false, "disableRemoteStatusPage": false }, { "id": "redacted2", "organizationId": "xxx", "name": "Location2", "timeZone": "Europe/Paris", "tags": " KIT0006 OSI ", "type": "combined", "disableMyMerakiCom": false, "disableRemoteStatusPage": false } ] Here is a working JS fiddle to demo it. https://jsfiddle.net/oa86k3ug/ Hope this helps, Cory

DexterLaBora · ‎Mar 7 2019

Nice work! This will be a great benefit to all. .. I had to make a small change to the app.js file line 29 the original line was causing errors running. res.render('error'); by using this method, it doesn't require a default view to be setup and works great. res.json({ error: err }); Error I was receiving > node ./bin/www POST / 400 24.616 ms - 1314 Error: No default engine was specified and no extension was provided. at new View (/Users/u/dev/merakialerts/node_modules/express/lib/view.js:61:11)

DexterLaBora · ‎Feb 26 2019

Yes! The port forwarding rules were just released. See the new updates here: https://create.meraki.io/whats-new/

DexterLaBora · ‎Feb 26 2019

Hi, Thanks for sharing your findings. FWIW, the more recent version of the Scanning API documentation is on the Meraki.io site. https://create.meraki.io/build/scanning-api-docs/ The newer doc provides a few other examples (node, python, etc). The Node version I wrote has the package.json file etc included, so it handled the changes with the NPM libraries. https://github.com/dexterlabora/cmxreceiver

DexterLaBora · ‎Nov 21 2018

After some quick research, it looks like the POST format of the Slack webhook API requires a specific JSON format as discussed. This means you cannot just point Meraki to Slack, since you will need some middleware to format the data first. Zapier does this with their integration. Alternatively, you could write a micro-service to do this. https://api.slack.com/incoming-webhooks#enable_webhooks Expected Slack format POST https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX Content-type: application/json { "text": "Hello, world." } Meraki Format { "alertData" : { "kbTotal" : 10750, "nodeTag" : "", "period" : 1200, "usageThreshold" : 10240 }, "alertId" : "643451796765320956", "alertType" : "Network usage alert", "networkId" : "L_123456789123456789", "networkName" : "Network - 1", "networkUrl" : "https://n1.meraki.com/...", "occurredAt" : "2018-10-25T17:17:38.623000Z", "organizationId" : "123456", "organizationName" : "Organization", "organizationUrl" : "https://n1.meraki.com/o/.../organization/overview", "sentAt" : "2018-10-25T17:17:46.608245Z", "sharedSecret" : "asdf1234", "version" : "0.1" } Middleware would convert JSON to look like this, where "text" could be the "alertType" and then you could parse out any other important details to format the message. POST https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX Content-type: application/json { "text":"Network usage alert /n more info.." }

DexterLaBora · ‎Oct 29 2018

Enable VLANs is now a supported endpoint! Postman Collection - Enable VLANs Enable/Disable VLANs for the given network PUT /networks/{{networkId}}/vlansEnabledState

DexterLaBora · ‎Oct 29 2018

Several updates to the Dashboard API & Postman Collection! https://documenter.getpostman.com/view/897512/2To9xm#whats-new What's New? October 2018 ALERT SETTINGS Return the alert configuration for this network GET /networks/[networkId]/alertSettings Update the alert configuration for this network PUT /networks/[networkId]/alertSettings HTTP SERVERS Manage servers for Meraki Alerts with webhooks List the HTTP servers for a network GET /networks/[networkId]/httpServers Return an HTTP server GET /networks/[networkId]/httpServers/[id] Update an HTTP server PUT /networks/[networkId]/httpServers/[id] Add an HTTP server POST /networks/[networkId]/httpServers Delete an HTTP server DEL /networks/[networkId]/httpServers/[id] Send a test webhook POST /networks/[networkId]/httpServers/webhookTests Return the status of a webhook test GET /networks/[networkId]/httpServers/webhookTests/[id] WIRELESS HEALTH Aggregated connectivity info for this network GET /networks/[networkId]/connectionStats Aggregated connectivity info for this network, grouped by node GET /networks/[networkId]/devices/connectionStats Aggregated connectivity info for a given AP on this network GET /networks/[networkId]/devices/[serial]/connectionStats Aggregated connectivity info for this network, grouped by clients GET /networks/[networkId]/clients/connectionStats Aggregated connectivity info for a given client on this network GET /networks/[networkId]/clients/[clientId]/connectionStats Aggregated latency info for this network GET /networks/[networkId]/latencyStats Aggregated latency info for this network, grouped by node GET /networks/[networkId]/devices/latencyStats Aggregated latency info for a given AP on this network GET /networks/[networkId]/devices/[serial]/latencyStats Aggregated latency info for this network, grouped by clients GET /networks/[networkId]/clients/latencyStats Aggregated latency info for a given client on this network GET /networks/[networkId]/clients/[clientId]/latencyStats List of all failed client connection events on this network in a given time GET /networks/[networkId]/failedConnections VLANS Enable/Disable VLANs for the given network PUT /networks/[networkId]/vlansEnabledState September 2018 SYSLOG SERVERS List the syslog servers for a network GET /networks/[networkId]/syslogServers Update the syslog servers for a network PUT /networks/[networkId]/syslogServers Returns video link for the specified camera. If a timestamp supplied, it links to that time. GET /devices/[serial]/cameras/video_link List LLDP and CDP information for a device GET /networks/[networkId]/devices/[serial]/lldp_cdp

DexterLaBora · ‎Oct 29 2018

Hi, I have updated a few things with this script. It now has an Org-wide and Net-wide menu. This will allow for some large reports to be more focused, such as Clients. Script: https://gist.github.com/dexterlabora/9884aa4399715df8f453ea9de63255a0 (replace your existing script with this one)

DexterLaBora · ‎Oct 29 2018

If you are using Google Apps for business, it is likely the administrator has disabled this option. You will need to either have this adjusted or test this solution using a personal Google account. (from a stackoverflow thread) This setting is controlled by the domain administrator via the "Allow users in [domain] to publish files on the web or make them visible to the world as public or unlisted files" options that's under "Settings for Drive and Docs". Note that after checking that option, you'll have to create a new Script in order to be able to publish it with "Anonymous" access. Existing scripts don't seem to get that option even after the setting has been changed. Also note the Google issue tracker for this: https://issuetracker.google.com/issues/36764781

DexterLaBora · ‎Oct 26 2018

The Shared secret is optional unless required by the receiving application. Google Sheets and Zapier do not support a secret, so you can put anything in there. If you are building your own webhook receiver, then it is advised to leverage this to ensure you trust the incoming data. Webhook Doc has been updated: https://create.meraki.io/guides/webhooks/#security Google Sheets guide has more info on this as well. https://create.meraki.io/build/meraki-dashboard-alerts-with-google-sheets/#meraki-alerts

DexterLaBora · ‎Oct 25 2018

Hi @kknopp, Thanks for testing out the Google Sheets app. - If you've updated the script, you must re-publish the app, setting a Project version to one higher. - The sharedSecret and version were not implemented in the Google Sheets app. This was a list minute addition to the webhook schema. In the future I may add a security handler to the Google script. Use the Postman collection to test out your sheet. Just update your {{webhook-url}} environment variable with the Google web app URL. Let me know if you have more questions or feedback.

DexterLaBora · ‎Oct 24 2018

We’re pleased to announce the availability of Meraki Webhook Alerts for all alerts within the dashboard! Meraki Webhook Alerts sends HTTP POSTs to a unique URL that can easily be fed into a receiving service. A receiving service can be as simple as a Webex Teams space, a Google Sheet logging all network alerts, or something more advanced, such as PagerDuty and ServiceNow, that can take the POSTs and create support tickets, send SMS messages to concerned parties, or even automate corrective action. Read More: - Blog - Reference

DexterLaBora · ‎Sep 18 2018

Postman Updated!

DexterLaBora · ‎Aug 30 2018

Hello! This has been added to the report! Overwrite your Code.GS file with this one https://gist.github.com/dexterlabora/9884aa4399715df8f453ea9de63255a0 Delete or Rename your settings sheet Refresh the Sheet window to load new script Update the new settings sheet

DexterLaBora · ‎Aug 30 2018

This script takes a while because it iterates through every device in every network to pull clients over a period of 86400 seconds. I was motivated by this question, so I have updated the script with a few additions. I've added a timespan and network setting so you can focus on a particular network and limit the search range. I also extended the reports with a Details version, that makes an API call for every client to get its SSID and other info. This will likely break on a large network, but I built it for another use case. Replace your existing code file with this one Code.gs Delete the settings tab or rename it so you have a copy Refresh the sheet to load the new version. It will generate a new settings sheet, which you must update. Its a work in progress, so still working on the UI, etc. Happy to hear any feedback.

DexterLaBora · ‎Jul 20 2018

Hi Ben, You can use the Device Status report to get the uplink status for every device in the org. This is a very fast call, as it returns an array of every device in the organization by default. I could write a recursive script to iterate through every device in every network in every org... but that takes a lot longer. If there is critical information in that call that you still need, I could consider writing an additional report. I added some extra reports and refined how the data is parsed be more dynamic with available attributes. Make sure you the newest script (simply replace yours with this new one). https://gist.github.com/dexterlabora/9884aa4399715df8f453ea9de63255a0 (formatting colors were applied after report)

DexterLaBora · ‎Jul 10 2018

Now with more reports! + admins + device details + clients

DexterLaBora · ‎Jul 6 2018

I created a simple tool to import Meraki Dashboard API data directly into a Google Sheet. Check out the full write-up https://create.meraki.io/build/meraki-dashboard-reports-with-google-sheets/ If you have cool ideas or feedback, let me know!

DexterLaBora · ‎Jun 20 2018

Connect a Meraki splash page to a hotel property management system with ease. By using the captive portal API and the MEWS API, I was able to build a seamless login experience using the customer's booking information. Authorize the user and dynamically attach a Group Policy. Then, send the logs to a Node-RED server for extra workflows like a WebEx Teams room or database. Check out the article. https://create.meraki.io/build/captive-portal-with-mews-hospitality-pms/

DexterLaBora · ‎Jun 8 2018

There are now two ways to get application traffic analysis. Hope this helps! Network Specific Postman Doc GET /networks/[id]/traffic [ { "application": "Miscellaneous web", "destination": "scripts.dailymail.co.uk", "protocol": "TCP", "port": 80, "recv": 375, "sent": 12, "flows": 2, "activeTime": 60, "numClients": 1 }, { "application": "Miscellaneous web", "destination": "www.metdaan.com", "protocol": "TCP", "port": 80, "recv": 4218, "sent": 144, "flows": 9, "activeTime": 240, "numClients": 1 }, Client Specific - NEW! Postman Doc GET /networks/[networkId]/clients/[id_or_mac_or_ip]/trafficHistory Successful HTTP Status: 200 [ { "ts": 1518365681, "application": "Google", "destination": "www.google.com", "protocol": "UDP", "port": 443, "recv": 383, "sent": 56, "numFlows": 5, "activeSeconds": 240 } ]

About DexterLaBora

DexterLaBora

Community Record

Badges