Meraki

rhbirkelund · ‎Jun 18 2020

You'll also need to convert the reply, since it is returning an object with json. Try including this; import json from pprint import pprint [...] r = requests(...) if r.status_code == 200: rjson = r.json() pprint(rjson) else: raise SystemExit(f"Unexpected status code {r.status_code}")

rhbirkelund · ‎Jun 17 2020

An MX is a security appliance - a firewall with a dash of router. https://meraki.cisco.com/products/security-sd-wan/ Specifically regarding the MX64/MX65, here is an overview of the device: https://documentation.meraki.com/MX/MX_Overviews_and_Specifications/MX64_and_MX65_Overview_and_Specifications

rhbirkelund · ‎Jun 17 2020

From what I've seen, it's also not possible to remove yourself as an admin of an organization, via Dashboard. I'm unsure, however, if it's possible via API. But as @BrechtSchamp correctly states, in order to delete an organization, you'll have to go through of the process of removing devices from networks, unclaim devices from inventory, deleting networks, removing all admins other than yourself _before_ you'll be able to delete an organization. Same goes for Dashboard as for API.

rhbirkelund · ‎Jun 15 2020

Can you not use the Default block message, by setting it manually, to "Please see servicedesk", and then use the Provision Network Clients endpoint, setting the client to Blocked?

rhbirkelund · ‎Jun 15 2020

In Network-Wide -> Configure -> General, you can set a default block message for the network. This should then appear, when you provision the network client. Unfortunately, I don't think there is an endpoint for updating it, so you'll probably have to set the default message, manually. Also, if you need a special message for at certain client, you'll probably need to set it manually, aswell. Hope that helps. 🙂

rhbirkelund · ‎Jun 15 2020

Check out the APIv1 endpoint POST /networks/{networkId}/clients/provision https://developer.cisco.com/meraki/api-v1/#!provision-network-clients For APIv0: https://developer.cisco.com/meraki/api/#!provision-network-clients

rhbirkelund · ‎Jun 15 2020

Why would you like to receive a notification every time a client connects to an AP? Depending on the client, over the course of a day, a client would reassociate and reauthenticate multiple times. Especially for an iPhone. And then multiply that up, with the number of clients trying to associate.

rhbirkelund · ‎Jun 15 2020

Can you check payload, and see what attributes is has? What if you simply remove "contentLength": payload.length,?

rhbirkelund · ‎Jun 9 2020

You might also want to take into account that Meraki requieres internet connectivity.

rhbirkelund · ‎Jun 9 2020

You can also see the Python definition for getNetworkLatencyStats here.

rhbirkelund · ‎Jun 5 2020

After CMNA you get a three year license, with the opportunity to get a renewal for another three years, by attending an online training session/webinar.

rhbirkelund · ‎Jun 5 2020

See this article about setting up High Availability on MX'es. https://documentation.meraki.com/MX/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair

rhbirkelund · ‎Jun 5 2020

I have previously done something like this. Some of the elements could match yours. It might not be the prettiest, but under the circumstances that were given to me, it works. Been running for the last two years, and so far haven't heard anything from it. Ignore the blue line. It was for a telephone service provided directly to the LAN. In your case HX1-SW1 would be your MS425 stack.

rhbirkelund · ‎Jun 5 2020

As far as I understand, it's the CMNO that's been replaced by the ECMS1. According to the FAQ, ECMS1 doesn't give any gear. The CMNA is still there, and this will qualify for a full stack, with a one-time three year renewal. Now whether or not it's possible to get a new kit, by resitting the course, no idea. Best guess is to contact your local Meraki SE, and see what she/he says.

rhbirkelund · ‎Jun 4 2020

Is it correct to assume, that the MS120 acting as a "wan switch", is connected back to the LAN side, to allow management? Could you perhaps try to draw up the topology?

rhbirkelund · ‎Jun 2 2020

You need to be able to uniquely identify the device you are working with. That's why you need the serialnumber. Imagine, you have access to multiple organizations, each with a main switch that's called HX-Sw1. How would you then be able to distginguish between devices, when matching on the hostname?

rhbirkelund · ‎Jun 1 2020

The message means, that there is something upstream, that is blocking tcp\7734. It can be either the ISP router, or another device upstream from the MX, depending on the network topology. Either make sure that port 7734 is open, or call Your ISP and have them ensure that port 7734 is not being firewalled.

rhbirkelund · ‎May 29 2020

Perhaps you could see this post who, oddly enough, seems to have exactly the same project... https://community.meraki.com/t5/Wireless-LAN/When-to-use-multiple-wireless-LAN-controllers-High-density/m-p/85856

rhbirkelund · ‎May 28 2020

Fair enough, then. 🙂

rhbirkelund · ‎May 28 2020

You really need to remove that API key, from the example, ASAP! You do not share an API key on the internet, as it can be used malicously!

rhbirkelund · ‎May 20 2020

Release notes Important notice This version, and subsequent MR 27.x versions, are only supported on the 802.11ac Wave 2 and 802.11ax MR product portfolio. 802.11ac Wave 1 and older products will not upgrade, should they be in networks configured for MR 27.x versions, and thus the new features will not be available and the bug fixes listed will not apply. New WPA3 Support https://documentation.meraki.com/MR/WiFi_Basics_and_Best_Practices/WPA3_Encryption_and_Configuration_Guide Meraki Health wireless performance metrics and client timeline https://documentation.meraki.com/zGeneral_Administration/Cross-Platform_Content/Meraki_Health Firmware Upgrade Strategy https://documentation.meraki.com/MR/Other_Topics/Access_Point_Firmware_Upgrade_Strategy Network-based Application Recognition “NBAR” https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/Network-Based_Application_Recognition_(NBAR)_on_MR (802.11ax MRs) iPSK without RADIUS https://documentation.meraki.com/MR/Encryption_and_Authentication/IPSK_Authentication_Without_RADIUS NOTE: Careful consideration must be made if the network is downgraded to a previous MR26.x release. The SSID using iPSK without RADIUS should be reconfigured to use an appropriate SSID configuration supported on MR26.x. Otherwise, the SSID will remain enabled as an “Open” SSID. Meraki Local Auth https://documentation.meraki.com/MR/Encryption_and_Authentication/Meraki_Local_Authentication_-_MR_802.1X Adaptive Policy https://documentation.meraki.com/zGeneral_Administration/Cross-Platform_Content/Adaptive_Policy/Adaptive_Policy_Overview NOTE: Careful consideration must be made if the network is downgraded to a previous MR26.x release. The switch interfaces must have tagging disabled for the access points to establish cloud reachability post downgrade. Bug fixes General performance, stability, and security improvements. MR sent management frames as well as broadcast & multicast frames at the incorrect bit rate after a channel change. Wireless Health latency stats were not being reported for the MR45 & MR55. (MR45/55) Modification of RADIUS Accounting Start delay timer enabled by Meraki Support was not taking effect (MR45/MR55) MR would not send traffic to a client that did not first send a packet after receiving an IP address (802.11ac Wave 2/MR45/MR55) MR would not forward EAP-TLS Server Hello packets from Authentication Server to Supplicant if configured for minimum bit rates less than 12mbps MR in CE regulatory domain does not send EAPOL Key 3 message to 802.11b/g clients on PSK SSIDs (MR45/55) Successful client authentications on a MAC-auth SSID resulted in authentication failures reported in Wireless Health Traffic between multiple wired clients connected to an MR30H LAN port would exhaust the memory on the MR, leading to instability (MR30H) MR could become unstable while taking packet captures from Dashboard and reboot (802.11ax MRs) MR was intermittently logging 802.1x authentication failures as PSK authentication failures VLAN tag received via RADIUS response was not being properly ignored for MAC authentication SSIDs when configured to do so High latency could be encountered on mesh link (802.11ax MRs) Known issues Wired clients connected to MR30H LAN ports are unable to pass unicast traffic (MR30H) Some client roaming scenarios may result in periods of inaccurate data in the client connectivity bar and client history Downstream VOIP RTP Packet Loss (MR42/MR42E/MR52/MR53/MR53E/MR84) Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's Reduced aggregate upload throughput on 2.4 & 5GHz radio for Windows clients (MR45/MR55)

rhbirkelund · ‎May 18 2020

Hey, When downloading the MS Fmaily datasheet from https://meraki.cisco.com/product/switches/access-switches/ms120-24/ you instead end up dorwnloading a datasheet for MV family.

rhbirkelund · ‎May 17 2020

As @MerakiDave says, there is no specific How-To, since every deployment is different. However, then I'm out deploying a Full Stack Meraki, I usually prioritize getting the MX up and running as the first thing. I even wait before powering and uplinking any device further down, untill the MX is up. All Meraki devices upon firsttime boot will contact the dashboard, and perform firsttime upgrade. So also before setting the MX up, make sure you've set whatever firmware you wish to be running in the Dashboard. Then make sure all basic settings are made (Mgmt DHCP), downlink ports an so on. After the MX is up, I go about uplinking the switches in the chained way that I have designed, and then work my way through the topology. One could connect it all as once, and go get lunch while it's everything is contacting the dashboard, upgrading, rebooting, and so on. But I prefer doing one device at a time. When all switches are online, I go about the rest. AP's, client facing ports and so on, as part of the comfiguration process. When all the basics are done, I go about doing all the finetuning, with everything online. Those are just my 2 cents..

rhbirkelund · ‎May 16 2020

When we do P2P links between sites, we usually go with Ubiquity's airMax product line..

rhbirkelund · ‎May 12 2020

Interesting. I'd actually might let Meraki Support know then. Probably not something important, but seems something is broken in their end.

About rhbirkelund

rhbirkelund

Community Record

Badges