Meraki

colo · ‎Jul 25 2018

A retail customer of mine wants a simple provisioning tool to allow a store technician to add a device to the network. All configuration will be done in advance using the API to automate, so we just need to add the serial number to the network. The google form is on Meraki.io is a good example, but they want something with a better front-end. What front-end do you recommend for a form using Dashboard API? Meraki.io has several guides with sample code that uses Vue, React, Angular, and Node. I want to know what you think would be the best solution for this customer. Requirements: 1.Select Organization Name  2.Search/Select Network Name   3.Search/Select Template Name   4.Enter Serial Number  5."Deploy" button VueJS app: https://create.meraki.io/build/dashboard-admin-app-demo/  AngularJS app: https://create.meraki.io/build/meraki-network-creator-with-servicenow-and-angular/   ReactJS Toolkit: https://create.meraki.io/build/dashboard-api-react-toolbox-demo/  NodeJS with Node-RED: https://create.meraki.io/build/node-red-getting-started-with-cisco-meraki-apis/

colo · ‎Jun 28 2018

Dear Developers, We will be disabling support for TLS 1.0 on June 27, 2018. This may impact third-party integrations using the Captive Portal API, Scanning API, or Dashboard API with these versions of TLS. The third-party service must be updated to use a modern version of TLS. We will not be able to revert these changes due to the pending PCI deadline on June 30, 2018, so if you notice issues with Meraki services or applications failing due to TLS errors, please contact Meraki support immediately. If you need to contact Meraki support please visit this website: https://meraki.cisco.com/support/ This announcement will be sent to technology partners and shared on our developer website here: https://create.meraki.io/build/tls/ Sincerely, Colin Lowenberg Cisco Meraki

colo · ‎Jun 26 2018

Please call Meraki support to enable this new API endpoint. It is only enabled for EU customers at this time. GDPR requires the PII information. Meraki plans to roll out to other regions, but we take into account privacy, scalability, and reliability as we roll out new features.

colo · ‎Jun 26 2018

Chris, That is correct, the Dashboard API does not provide the floor plans. However, our guide on how to integrate Mapwize includes a workaround you will hopefully like. Here are the instructions: https://create.meraki.io/build/wayfinding-mapwize/#getting-the-floor-plans Also with the recent update to our floor plans tool on Dashboard, we've exposed a JSON endpoint which you can find when you view the source code of the page. It looks like this: https://n6.meraki.com/node_groups/566327653141872861/floorplans Your hostname and network ID will be different. The network ID will match your networkId from Dashboard API but without the "N_" attribute- and note it won't match a combined network with the "L_" attribute. Regards, Colin Lowenberg

colo · ‎Jun 18 2018

Check out this article we wrote on deep linking into Dashboard: https://create.meraki.io/build/deep-links/

colo · ‎Jun 4 2018

If you are trying to secure a trunk port, I would typically "blackhole" the native VLAN. I've done that for office deployments where IT was concerned someone could access the AP's cable in the ceiling and just plug in. It was also recommended by @PhilipDAth I think in the balance between ease of deployment and security I convinced the IT sec team to allow the guest VLAN or a special "staging VLAN" to be used as the native VLAN - with no internal access to the network. An alternative to a blackhole for the native VLAN is to put it on the guest network. Note that VLAN tagging and MAC whitelisting are security measures, but they are also both not too difficult to work around. Finally a solution not based on Meraki (thanks MS) that I think we can agree is simple to implement, set your DHCP server to only give out IP addresses to your AP's MAC addresses. Microsoft explains how to do this here: https://technet.microsoft.com/en-us/library/ff521761.aspx

colo · ‎May 30 2018

I've seen nice badges from Piper Networks and Kontakt.io

colo · ‎May 30 2018

Hi @nkarstedt, I would suggest talking to a Meraki sales rep and asking for support from an SE to make sure your use case is clearly defined. It sounds like you want to bill users for access to a network and allow them to start and stop sessions rather than have a single session length. Group policies can be applied at connection time using the RADIUS Accept message, and the group policy can be changed later with RADIUS CoA or using Dashboard API. The API also supports whitelist, blocklist, and even splash authorization and expiration, giving you a little more control than RADIUS. Using a time-based solution that automatically ends the session time (pausing their time remaining) if they disconnect is possible using RADIUS Accounting information. The Dashboard API would allow for this but would require polling the devices API frequently. Several companies have already implemented this type of billing solution, and you can contact them from our App Directory apps.meraki.io I know Purple has this feature.

colo · ‎May 30 2018

No it's not available via API today.

colo · ‎May 25 2018

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

colo · ‎May 25 2018

@JHO We have not implemented the API for ACLs and L3 routing on switches, so it's a feature that needs to be built. The VLAN configuration is available in the API today - it's under the SwitchPort endpoints: https://documenter.getpostman.com/view/897512/meraki-dashboard-api/2To9xm#34a1dd64-081e-ab92-53f0-6564a7ee2444

colo · ‎May 25 2018

@Steven If you are monitoring for changes to the configuration, this data is available as an Email or SNMP Trap today, and you can configure this under Network-wide > Alerts. If you are monitoring for device status try this API endpoint: https://documenter.getpostman.com/view/897512/meraki-dashboard-api/2To9xm#f45ffad7-ad71-44d9-a4b3-c9...

colo · ‎May 25 2018

Awesome! Teamwork! By the way the dashboard's documentation under Help > API Docs did not have this attribute, but the awesome Postman collection did have the answer! Link to Postman: https://documenter.getpostman.com/view/897512/meraki-dashboard-api/2To9xm#f45ffad7-ad71-44d9-a4b3-c9ad74bfd9cc It's a bit ironic when the API is so big that I don't know what's in it. We asked for it.

colo · ‎May 24 2018

Has anyone come up with a solution for monitoring the cellular status at scale? UPDATE: Kudos to PhilipDAth and spankym for the answer. I met with a customer today with 4000+ locations using 4G cellular backup. One of the asks from the customer was to monitor cellular failover with the API in a more scalable way. Without a solution for monitoring/alerting, the sites failover to cellular and rack up huge bills for the Franchise owner. One solution they already use is polling the Dashboard API's Uplink status for a device,. It takes up to 30 minutes to poll all of the devices, one by one, looping through the entire inventory. Another solution is Meraki's Alerts via Email and SNMP Traps, but we all agreed this is not the best solution and prefer to use an API. Webhooks was mentioned as a feature request for Meraki's engineering team. SOLUTION: The recently released API call for getting the device status across all of the organization includes an attribute named usingCellularFailover and the call needs to be made just once for each organization. Request: curl -L -H 'X-Cisco-Meraki-API-Key: <key>' -X GET -H 'Content-Type: application/json' 'https://api.meraki.com/api/v0/organizations/[organizationId]/deviceStatuses' Response: [ { "name": null, "serial": "Q2QN-WVV9-W4KK", "mac": "e0:55:3d:17:c6:87", "publicIp": "64.103.26.54", "networkId": "L_646829496481095933", "status": "offline", "usingCellularFailover": false, "wan1Ip": "10.10.20.70", "wan2Ip": null }, .... Postman Collection: https://documenter.getpostman.com/view/897512/meraki-dashboard-api/2To9xm#f45ffad7-ad71-44d9-a4b3-c9ad74bfd9cc

colo · ‎May 2 2018

Hi Lina, I fixed the link. I am confident it works but I have not personally tested this use case. The AP firmware handles the RTLS functionality, not the Cloud, so the firmware is responsible for the handoff to the Stanley server. Regards, Colin

colo · ‎Jan 25 2018

Amazing work Philip! This same type of script could be used to turn of lights, change HVAC settings, or even automatically book the conference room. Minor note, we no longer use the CMX name to avoid confusion with other products under the same name. CMX location analytics is now Meraki Location Analytics CMX API is now Meraki Scanning API

colo · ‎Jan 8 2018

Noriko, Are you trying to locate a client on the map or link to the dashboard page for the client details? These are two different use cases. If you just want the location of a client MAC address, we have an example: http://live-map.meraki.com/ To build this, follow our detailed guide here: https://github.com/meraki/scanning-api-app If you want to link to the Dashboard's Client details page, you'll need to know the URL including the network's hash and the client's hash which is only available in the UI. We don't have an API that constructs the URL. If you want to check if a client is blocked, you can use this API call: https://dashboard.meraki.com/api_docs#return-the-policy-assigned-to-a-client-on-the-network

colo · ‎Jan 8 2018

2. You can re-create the Meraki dashboard's analytics - but generally the use case is to go further into the data and combine it with other data. You get the real MAC address with the API and you can locate a specific user and link them to Syslog alerts/events, captive portal data with social media / email / SMS / loyalty programs. The best use without extra data sets would be simply ranking all of your sites and identifying trends like a stock ticker showing the increase in traffic over the last day, week, month. Meraki dashboard only let's you compare 2 networks or 2 network-tags or 2 AP-tags. If you want to get your top 10 gains and top 10 losses, like a stock tracker, that would need something like elastic search.

colo · ‎Dec 1 2017

Hi Randy, It sounds like the UI is displaying "Active: " instead of the correct "Active: always" when you add a route via API. I would suggest reporting this to Meraki support. It would also be good to test it and confirm that there is no impact on the functionality of your network. https://meraki.cisco.com/support/

colo · ‎Nov 29 2017

Hi Cybergeek, Meraki / Support generally advise not to reboot APs. If there is an issue that requires a reboot, it’s possibly a bug. Please call or email Meraki support. How can you reboot Meraki APs? You can disable the port (or turn off PoE) on the upstream Meraki switches, which is providing power to the Meraki AP. HTTP REQUEST PUT /devices/[serial]/switchPorts/[number] PARAMETERS enabled The status of the switch port poeEnabled The PoE status of the switch port What if you don't have Meraki switches? However I had to solve this exact problem for a customer without Meraki Switchesand managed to reboot thousands of APs using an API script to remove and add the AP from the network. This forces the AP to reboot and connect to the Meraki Cloud to get it's config. Slow Method - I have tested and used this with customers. Step 1. Remove AP from Network POST /networks/[networkId]/devices/[serial]/remove Step 2. Wait some amount of time and the AP will download a default config. Step 3. Add AP back to the Network POST /networks/[networkId]/devices/claim Step 4. Confirm the AP is now online with the original config. The GET request should be successful. GET /networks/[networkId]/devices/[serial]

colo · ‎Nov 15 2017

All, You can find the latest documentation here: http://developers.meraki.com/docs -> redirects to -> https://api.meraki.com/api_docs I recommend using the Postman collection: http://developers.meraki.com/postman Sometimes the Postman takes a day to get updated but we try out best to keep it up to date! Cheers

colo · ‎Nov 15 2017

Hi Lee, Note that BLE and WiFi tracking and RTLS tracking are different. You can read about the BLE and WiFi tracking on https://create.meraki.io/build/rtls/ and you can read more about the RTLS here: https://documentation.meraki.com/MR/Monitoring_and_Reporting/Real-Time_Location_Services_(RTLS) For RTLS, also known as WiFi RFID Tags, we only support AeroScout and Ekahau formatted RTLS Tags and both are options on our dashboard. If you are interested in other WiFi RTLS vendors like Centrak, Awarepoint, please submit a wish on the dashboard and tell your sales person this is necessary. For BLE beacon location tracking, you can use any Bluetooth low energy device that follows the standard. A few consumer-focused BLE beacon vendors randomize the MAC address for privacy reasons and cannot be tracked. Meraki ignores randomized MAC addresses in our Scanning API. You can get location data with even a single AP but the location will not be accurate. The model of AP should not matter. For the best compatibility with all models of APs, you should make sure your RTLS tags are configured for WDS+IBSS mode. Cheers,

colo · ‎Nov 15 2017

Hey Lee, I suggest emailing support@meraki.com for some extra help. They'll probably start by asking you to test your URL is valid by pasting it into a web browser. Here is the documentation on troubleshooting: https://documentation.meraki.com/MR/Monitoring_and_Reporting/Location_Analytics#Scanning_API_Data_is_not_received Regards, Colin Lowenberg

colo · ‎Oct 17 2017

Hi @Todd_Theoret, We don't expose the module information via API. On Dashboard UI, browse to a switch, and then click on the port on the switch icon. You'll see the SFP module in the Status section - see below. Configuration | Edit configuration Description: Trunk port; allowed VLANs: all RSTP: Forwarding Link negotiation: Auto negotiate (10 Gbps) Port mirroring: Source port Isolation: Disabled Status Connectivity: Usage: 2.41 TB (972.25 GB sent, 1.46 TB received) Traffic: 497.5 Mbps (130.9 Mbps sent, 366.6 Mbps received) SFP module: Meraki - Direct-Attach: 10.3 Gbps (Part: 600-22070-B, Serial: Q2GR-AEFW-QSF6)

colo · ‎Oct 4 2017

You can bulk add administrators through the Dashboard API, but not users. If the users are employees, you might consider granting them all Guest Ambassador privileges (the most limited Admin role). Give it a try and let me know if that is a solution. Alternatively, you can use a RADIUS server or LDAP or Google Apps. Submit a wish on the Dashboard API under Help > API Docs. Meraki is always looking for feedback.

Meraki

Community

About colo

colo

Community Record

Badges

What front-end is best? Vue vs. React vs. Angular vs. Node vs. Bootstrap

Call to Action: Support for TLS 1.0 discontinued

Re: API Dashboard "Return a client" GET doesn't works

Re: Location API Question

Re: How is the URL constructed?

Re: Restrict Switch port to AP

Re: BLE Loyalty Card

Re: Allowing Temporary Access via API

Re: Content Filtering via API

Re: API Rate limit on API key or Org_id?

Re: (VERY) Incomplete dashboard API?

Re: (VERY) Incomplete dashboard API?

Re: Cellular Failover Monitoring via API?

Cellular Failover Monitoring via API? [SOLVED]

Re: Meraki compatible RFID tags

Re: Project: Cisco Meraki CMX Presence Based Remote Control

Re: How to check the blocked clients list

Re: Response other than 200 - scanning API

Re: staticRoutes API call does not update the "Active" field

Re: API Call to Reboot AP

Re: Add Meraki VLAN via API failing

Re: Meraki compatible RFID tags

Re: Response other than 200 - scanning API

Re: Switch Modules - Inventory Report

Re: Meraki Authentication: bulk user creation

Re: How is the URL constructed?

Re: API Rate limit on API key or Org_id?

Re: Meraki compatible RFID tags

Re: (VERY) Incomplete dashboard API?

Re: How is the URL constructed?

Re: Content Filtering via API

Call to Action: Support for TLS 1.0 discontinued

Cellular Failover Monitoring via API? [SOLVED]