Meraki

rhbirkelund · ‎Dec 7 2023

I honestly think this is a lost opportunity, that it is not already available to MR and MX platform as well. Org-level RADIUS - just only for MS switches. Btw, is it meant by design, that we can only select one radius server on the MS access policies? So if you have multiple PSNs you'll hgave to still enter them manually?

Inderdeep · ‎Nov 21 2023

Perfect, Thanks for sharing @ShawnHu

ShawnHu · ‎Nov 20 2023

The troubleshooting console feature is available on all monitored Catalyst switches.

ShawnHu · ‎Nov 20 2023

Explore the newest additions to the Meraki hardware lineup: Z4C – The latest secure gateway with a built-in cellular module MS130R - The layer 2 Meraki switch is designed for ruggedized environments CW9163E - The outdoor-rated, enterprise-class 802.11ax on-prem or cloud-managed access point To find these models, simply visit the inventory pages on either the Launchpad🚀 or Cisco Meraki Platform demo environments and search for their model names. Datasheets: Z4C, MS130R, and CW9163E.

ShawnHu · ‎Nov 15 2023

Attention Meraki Launchpad🚀 demo environment users! We're excited to announce a significant update to our interactive demo widget. Here's what's new: We've renamed the widget to 'Meraki Demo' for a clearer identity. A feedback feature is now enabled, allowing you to share your comments directly through the widget. We've added automation steps to all flows, enabling you to start any flow from anywhere. Enjoy these enhancements designed to improve your Meraki demo experience!

ShawnHu · ‎Nov 15 2023

As of Oct 2023, on Meraki Launchpad🚀 , we extended the existing Adaptive Policy demonstration from the MS390 switching platform to include MX and MR products. This update lets demo users showcase an end-to-end adaptive policy and secure group tag solution across the Meraki Secure & SD-WAN, switching, and wireless platforms. Demo org: Meraki Launchpad🚀 Networks: San Francisco - Adaptive Policy and Sydney Meraki Launchpad is covering the following scenarios: Dynamic SGT assignment on the MS390 platform based on RADIUS attributes (Adaptive Policy clients) Per-port SGT assignment on the MX (Port 6 > 18: employees-sales) SGT transport over AutoVPN (VPN settings > Peer SGT capable) Static SGT assignment based on the MR SSID (mCLOUD-RETAIL-SYD-Sales SSID) Verification As illustrated, ICMP traffic was initiated between clients. To verify the Adaptive Policy solution in this demonstration, two packet captures were done on points A and B (see the locations in the above topology). Point A: port#1 of the MS390-24UX, uplink of both MS390 switches Point B: port#2 of the MS390-24UX, the interconnection between two MS390s Conclusion: As illustrated in the Wireshark screenshot above, both the wired and wireless interfaces of the client, Billy Merchant, from the Sydney network were sending ICMP Echo requests to the client Sam Colt (172.26.10.17) in the SFO-ADP network. The SGT 18 was successfully transmitted over the AutoVPN. However, due to the presence of a deny policy between SGT 17 and 18, the client Sam Colt did not receive these Echo requests, resulting in the absence of captured Echo replies. Conclusion: As depicted in the Wireshark screenshot above, the client Mary Anderson (172.26.10.19) was able to communicate with the client Sam Colt (172.26.10.17) despite the encapsulation of different SGTs(17 vs 19). Conversely, the client Elijah McCoy (172.26.10.18) was prevented from sending traffic to Sam Colt, even though they are within the same local LAN. This restriction arises from the presence of a traffic denial adaptive policy between SGT 17 and 18. For more information about this feature and configuration guides for each product, please consult the documentation Adaptive Policy Overview.

ShawnHu · ‎Nov 15 2023

MT15 is the advanced air quality sensor that offers a CO2 sensor in addition to the metrics MT14 monitors: temperature, humidity, PM2.5, TVOC, and ambient noise. Expectedly, both the temperature and noise level are unsuitable for work in our data center environment. You can find the demo units in the networks below. Meraki Launchpad🚀 > San Francisco or London Cisco Meraki Platform > San Francisco or London Other resources: MT15 public announcement blog.

ShawnHu · ‎Nov 15 2023

At Cisco, we are committed to providing you with the best tools and resources to streamline your experience with Cisco Meraki throughout the See-Try-Buy buying model. We have created and maintain serveral demo platforms to cater to various requirements, from Meraki prospects to partner sales and solution architects at Cisco. To eliminate any confusion and ensure you can access the right demos effortlessly, we are pleased to introduce our dedicated demo platforms: Cisco Meraki Platform, Cisco Meraki Launchpad🚀and more. Your access permissions on Cisco.com will determine the availability of these instant demos on dcloud.cisco.com. Cisco Meraki Platform: Tailored for Customers The Cisco Meraki Platform is specifically crafted for our customers, particularly those interested in exploring Meraki. It provides access to the latest products and essential features of the Meraki platform, making it ideal for Customer test drives. With this platform, you can become familiar with the intuitive Meraki dashboard even before your first Meraki deployment. Cisco Meraki Lauchpad🚀: Designed for Partners and Cisco Employees In addition to featuring the latest hardware and firmware, this demo platform offers access to the most advanced Meraki solutions and cross-platform integrations. It's not just a standalone platform – it's also the powerhouse behind a series of Meraki instant demos on dcloud.cisco.com. We strongly encourage Cisco partners and employees to utilize this toolkit to showcase the true potential of the Meraki platform. Both demo platforms feature real hardware, clients with emulated traffic, and support multiple languages. Explore more dedicated demo platforms for special use cases (Cisco partners and employees only) : Cisco Meraki for US Government Platform Meraki GO Meraki Subscription Licensing Meraki Enterprise Agreement Licensing You can also locate the links to our frequently used demo environments in the 'Useful Demo Links' section of the forum page.

ShawnHu · ‎Oct 10 2023

Great video! If you want to do a live demo in front of customers, Cisco employees or our partners can use the exact same environment in this video to run a firmware upgrading demo. Check out the Meraki Launchpad🚀 instant demo on dCloud. Customers can take the Cisco Meraki Platform instant demo platform to test drive the great features of Cisco Meraki cloud-managed IT.

PhilipDAth · ‎Jul 20 2023

ps. Googles Bard (bard.google.com) is very good at writing code using Python and the Meraki API

ShawnHu · ‎Jan 4 2023

@RandomTable1 Can you share the whole error message from the interactive API documentation？ I don't see the same message in the Python library. Also, you don't need to set every single parameter in the JSON body if you don't need to change it. I recommend you perform the GET uplink setting first and only include the parameters you want to change in the JSON body. For example, below is a JSON body that changes the uplink WAN2 with a static IPv4 address and gateway. Other parameters will remain the same. { "interfaces": { "wan2": { "svis": { "ipv4": { "assignmentMode": "static", "address": "1.2.3.4/24", "gateway": "1.2.3.1", "nameservers": { "addresses": [ "1.2.3.1" ] } } } } } }

ShawnHu · ‎Dec 27 2022

@Cliff92I assume you meant the endpoint returned an empty list ([]), but the call was successful. Please try the following endpoints to get the client info for a specific Meraki device or a network. https://developer.cisco.com/meraki/api-latest/#!get-device-clients https://developer.cisco.com/meraki/api-latest/#!get-network-client https://developer.cisco.com/meraki/api-latest/#!get-network-clients --> Filters are available for querying specific clients such as wireless or online clients. For a given network, here is an example of retrieving wireless clients for the last 2 hours connected to the network. {{baseUrl}}/networks/:networkId/clients?timespan=7200&recentDeviceConnections[]=Wireless

mikehopkins · ‎Dec 27 2022

Many thanks for this information! It is actually really great if "stopped_reporting" and "started_reporting" works and is consistent across all device types. We are integrating with AlertOps and really need a consistent signal to indicate down and up status of devices.

meilenstein · ‎Dec 27 2022

I claimed the device to a network and the updateDevice function worked! Thank you @ShawnHu

PhilipDAth · ‎Dec 11 2022

That is clever thinking. If could be a template for you with all your standard settings.

ShawnHu · ‎Dec 6 2022

@Techniche I verified these two endpoints on our demo environment and can confirm the document is correct. Endpoint get-organization-appliance-uplink-statuses doesn't provide the uplink info for MG. Besides this, both endpoints return the same parameters for each MX or Z device.

sungod · ‎Sep 15 2022

You can use https://developer.cisco.com/meraki/api-v1/#!get-organization-admins to identify admins and detect which have API key(s). Then as above get the requests and see which admin(s) are using the API.

AutomationDude · ‎Aug 29 2022

You might have IP restrictions enabled on who can use the API with this organization. Do check out that configuration in the Organization settings on dashboard.

dawydiuk · ‎Aug 19 2022

Thanks that worked, so I went back to the meraki-cli and by running the exact same command and not changing anything it worked... Not sure what to think but it's working today, thanks 🙂

ShawnHu · ‎Jul 31 2022

We are also pleased to share a lately published eLearning course on this topic. Check out the below curriculum. https://learning.meraki.net/#/curricula/ee146e6c-5d90-4627-a87b-758627e388a6 Module 1: The Journey to Cloud Management for Catalyst (15 min) Module 2: Cloud Monitoring for Catalyst (20 min) Module 3: Cloud Management for Catalyst (Coming soon)

ShawnHu · ‎Jul 22 2022

Both are valid points. So the Access privilege options are based on the target network selected. When using the network tag to scope network(s), there will be only four default privileges, given different networks might contain different device types. You are right about no API support for port management privilege setting. And unfortunately, the Update an Administrator endpoint currently does not support the custom access privilege either (in your case Packet_Capture) . I bet there is some good reasons for this, but it may be worth reaching out to your Meraki sales team and submitting a feature request to evaluate. { "errors": [ "'access' must be one of: 'full', 'read-only', 'guest-ambassador' or 'monitor-only'" ] }

ShawnHu · ‎Dec 21 2021

Hi RJ, You are right, API needs to be toggled per organization. The bonus point is now you can activate the API by using the API. Use the below endpoints to get your organization IDs first and then enable API on the organization level. (Replace the <key> and {organizationId} with your own values.) curl -L -H 'X-Cisco-Meraki-API-Key:<key>' -H 'Content-Type: application/json' -X GET 'https://api.meraki.com/api/v1/organizations' curl -L -H 'X-Cisco-Meraki-API-Key: <key>' -H 'Content-Type: application/json' -X PUT --data-binary '{"api": {"enabled": true}}' 'https://api.meraki.com/api/v1/organizations/{organizationId}'

ShawnHu · ‎Nov 28 2021

You can also leverage the 'Meraki Tools' to get the network appliance uplink usage and use google sheet to generate whatever chart you prefer. https://workspace.google.com/marketplace/app/meraki_tools/11340767263

John_on_API · ‎Oct 29 2021

204 No Content means the MAC wasn't found.

ShawnHu · ‎Sep 21 2021

Just ran and it worked for me with both generic base URL and direct shard URL. Can you confirm you have signed up for the Developer Early Access Program on your target dashboard organization? You can find the link in the original post.

About ShawnHu

ShawnHu

Community Record

Badges