AVB is supported just on Catalyst 3K and Catalyst 9000. ... View more

Just edit Wan interface configuration And you will be able to disable It. ... View more

  https://documentation.meraki.com/?title=MX%2FNetworks_and_Routing%2FIPv6_Support_on_MX_Security_%26_SD-WAN_Platforms_-_LAN ... View more

What type of authentication are you using?   https://hcsonline.com/images/PDFs/Wi-FI_Apple_Devices.pdf Look on page 4. ... View more

I guess so. ... View more

I had the same issue, I rollback the firmware too. ... View more

It can be a possibility. ... View more

License Flexibility Our Licensing Team has been working hard to ensure a smooth transition between Modes (DNA and Meraki) from the licensing perspective. For the common hardware perspective, to migrate the Cisco Catalyst 9300 switch to a Meraki mode, a valid DNA license is required. You can choose between Meraki Enterprise or Advanced license depending upon enabled features during license renewal. The Cisco Catalyst 916x series APs can be purchased with the appropriate licenses based on the management platform: DNA license for Cisco DNA Center or Meraki license for Meraki mode. On the visibility/monitoring front: A valid DNA Essentials (for switch visibility) or Advantage license (client visibility) is required to be onboarded into the Meraki dashboard. The device can be managed by other tools such as Cisco Prime, CLI or 3rd party tools. Customer Use Cases Cloud Monitoring Catalyst customers not using Cisco DNA Center as the operational platform: You will be able to gain immediate value with cloud monitoring, providing a view of your network from anywhere, anytime, giving them a low-effort way to experience Meraki Cloud Dashboard. Customers who are running a hybrid network of Meraki and Catalyst: Benefit by moving their Catalyst hardware into view on the Meraki dashboard with monitoring. Cloud Management Customers with network refresh network: Customers who already have Meraki platforms; upon refresh, they can choose to adopt Catalyst into their existing infrastructure (APs and switches) Current Cisco Catalyst 9300 customers looking to move to cloud operations and the features available in the Meraki Dashboard satisfy their use cases.   https://blogs.cisco.com/networking/your-network-your-way-a-journey-to-full-cloud-management-of-cisco-catalyst-products ... View more

It's still a Catalyst switch, just with a firmware that you can manage through the Meraki Dashsboard. You will still have access via CLI, etc.   Sorry, Once a Catalyst switch is fully managed by Meraki it will no longer be an IOS device. It will run Meraki software. But if it is a monitored switch, it can still be accessible via CLI. ... View more

https://www.youtube.com/watch?v=bJCOOo9Zwco ... View more

Man, you have to install It on switch 😉 ... View more

Supported Platforms & Licensing Today, the Catalyst 9200, 9300 and 9500 switching platforms will be supported in the Meraki dashboard with two options: Cloud Monitoring (monitor only) Cloud Management (monitor and configuration) The minimum firmware version to run on these switches is IOS-XE 17.3 or higher. What about licensing? Fully managed Catalyst switches will need to have DNA Advantage (DNA-A) or DNA Essentials (DNA-E). Monitored Catalyst switches will use a Meraki license. ... View more

Yeah, I know, but I think It's a good information too save. But the second link contains the informations that you need. Right? ... View more

@redsector    There is the information that you need:   https://documentation.meraki.com/Cloud_Monitoring_for_Catalyst/Onboarding/Cloud_Monitoring_for_Catalyst_Onboarding_Guide   https://rowelldionicio.com/manage-cisco-catalyst-in-meraki-cloud/ ... View more

Yep, 🙂 ... View more

MX and MX I've already tested it in practice and I can guarantee that it will continue to work, but the access points (MR) I'm not 100% sure. ... View more

The 802.11w amendment applies only to a set of robust management frames that are protected by the Protected Management Frames (PMF) service. These include Disassociation, Deauthentication, and Robust Action frames.   Some legacy devices that do not support 802.11w may not be able to connect to an SSID even if in mixed mode. This may be due to the device improperly handling the advertised information contained within the beacons.   Can you share how is configured your RF profile? ... View more

The Meraki Cloud is an out of band architecture, meaning that no client data flows through the Cloud. The system is also designed to handle connectivity failures gracefully.   If a Meraki data center experiences an outage, your network will automatically fail over to another Meraki data center. During the fail-over time your network will experience connectivity loss as described above. Assuming you have setup email alerts, you will receive an email when a Meraki node loses connectivity to the Cloud, allowing you to take corrective action if necessary. For more information on local device management, see Using the Cisco Meraki Device Local Status Page. Overview Safe Configuration Safe configuration means that “the device has connectivity to cloud and hasn't rebooted for 30 minutes following a configuration change.” That is, the safe configuration is the last configuration the device received from the cloud that was not followed by a reboot within 30 minutes.   https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Behavior_during_Connection_Loss_to_Cisco_Meraki_Cloud ... View more

What firmware version are running? In that case my suggestion is open a case with Meraki team support to investigate it. ... View more

@drago,   Look this exemple.  The ATT router is your internet link, and the Cisco 3650 is your network's Core. You will have to create a link between the Router and the switch core and create a default route in the siwtich Core pointing to the IP of the Router, Ex: ip route 0.0.0.0 0.0.0.0 192.168.100.1 Going back to the example your local network is 192.168.200.0/24 So, you would have to create a return route on your router, which I believe is not possible. So I don't think it will work.   ... View more

Go to Organization > monitor > Firmware upgrades on all networks select your Switch network then schedule it:     Selec the firmware version then select perform the upgrade now.     The last 2 hours is the minimum that you can filter. ... View more

Windows Error 809 If this error appears, the Event Log won't have any relevant logs, as the traffic doesn't reach the MX's WAN interface. Possible causes and solutions: Client behind NAT devices ​​​​​Solution: Modern Windows devices do not support L2TP/IPsec connections when the Windows computer or VPN server are located behind a NAT. If the Windows VPN client fails with Error 809 when trying to establish a VPN connection to an MX located behind a NAT, add the "AssumeUDPEncapsulationContextOnSendRule" DWORD value to the Windows registry. This DWORD value allows Windows to establish security associations when both the VPN server and the Windows-based VPN client computer are behind NAT devices. For Windows XP: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IPSec RegValue: AssumeUDPEncapsulationContextOnSendRule Type: DWORD Value data: 2 Base: Decimal For Windows Vista, 7, 8, 10, and 2008 server: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent RegValue: AssumeUDPEncapsulationContextOnSendRule Type: DWORD Value data: 2 Base: Decimal Note: that after creating this key you will need to reboot the machine. For more information, reference this Microsoft Support knowledge base article. Note: Some third-party network programs can also cause Windows Error 809 to occur. SmartByte is one such program known to cause this issue. Disabling the program should resolve the issue and allow the VPN to connect. ... View more

In my opinion Python is the best way to do that:   https://github.com/meraki/automation-scripts   https://developer.cisco.com/meraki/build/meraki-postman-collection-getting-started/#!introduction/basics ... View more