Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Security appliances software versions MX 19.2.9 changelog Important noticeAs of MX 19.1, Cisco Meraki will no longer support USB-based Cellular Failover on the MX and Z platforms.Starting with MX 19.1 firmware on vMX platforms, Meraki has begun to de...
Access points software versions MR 30.7.3 changelog Important noteThis release includes support for Wi-Fi 5 APs only.SecurityAs part of Cisco's ongoing commitment to proactive security and product quality, the MR engineering team has conducted a comp...
Hi ,Just saw minutes ago this new menu :Creating a Network Group requires a MCG/CG. I couldn't find the documentation yet , so I'm not sure what is the purpose of this menu.
Security appliances software versions MX 26.1.7 changelog Executive summaryMX 26.1.7 is the first Recommended release in the MX 26.1 release family.We recommend planned, phased production adoption in accordance with normal change-control and platform...
Hi ,Any plans to add new bells and whistles to the Meraki integration with XDR ? The integration is very poor at the moment. 1- Can't view basic info such as network name in an Incident...2- Can't do proper filtering on sources. I want to exclude som...
Yeah just saw that also. but I still think this is not intended or simply a odd way of releasing a product. No post on linkedin or here, it just slips into the documentation.
So we don't know the CVE that were found by their internal AI but everyone is disclosing these on the same day... Cisco , Arista , Palo Alto and probably more vendors. This is very suss...Advisories & Notices - Security Advisory - Arista
@karbabif https://documentation.meraki.com/?title=SASE_and_SD-WAN/MX/Design_and_Configure/Architectures_and_Best_Practices/MX_Sizing_Guide_%26_Principles I think "you" should revert that change. I don't have access to webex to alert Raul or the oth...
Hi ! From what I have just tested you can "trust" getNetworkSwitchQosRules.I have a simple rule base on my test network and I tried moving rules around and getNetworkSwitchQosRules always returned the payload in the correct order. getNetworkSwitchQos...