Luckily I think 99% of our AnyConnect deployments are leveraging SAML and not using certificate auth so not vulnerable to this! ... View more

Check your Cloud Firewall rules are allowing Private traffic between the sites. ... View more

We might finally be getting the right pair of eyes on the issue, update from support this morning: I was able to replicate this behavior on my side as well, therefore I have opened an internal investigation with our Support Product Specialist team to investigate further. ... View more

We are 3 weeks into the issue now, I don't suppose you can find out if a resolution is in sight? ... View more

Raised one before making this post 🙂 ... View more

We have taken a step forward - there is a "2025 platform optimization" update: Cisco Secure Connect - Design Best Practices - Cisco Meraki Documentation   We are in discussions with support finalising our requirements but it looks like we will be going for Design B in the linked article and this should allow spoke<>spoke traffic to traverse the Secure Connect backbone, but spoke<>vMX Hub to go direct.   ... View more

Wouldn't hold out much hope, if your solution depends on having this feature then you need to look elsewhere. ... View more

I like it - but we are still lacking a column/filter for the Org name the case is raised against. As an MSP with access to over 100 Orgs this would be really useful. 🙂 ... View more

Does make you wonder how this was not caught during QA of the change in Dev/UAT environments 🙂 ... View more

Yes - we have experienced the same across multiple Orgs and have used the same workaround as you have already discovered.   Ticket logged with support since 21st May and no meaningful update since then other than: "This is a known issue that our Development Team is still investigating and working on a fix in the new page so you can see the Password" ... View more

I can only relay what we have been told, no way to prove it one way or the other! Perhaps raise a ticket and see what they say about your devices utilisation? ... View more

We noticed the same and received feedback from Meraki support that there is a cosmetic issue in the dashboard relating to how the utilisation is measured and reported on MX 19.1.8, making it appear higher than it is. ... View more

My understanding is that the L7 Geo only blocks outbound initiated sessions, so whilst it will block inbound attempts to your NAT rules from those countries, it is only doing it because the response from the server gets dropped.   Solved: MX GEO IP filtering on Port Forward rules - The Meraki Community   EDIT: The documentation also states: "The Layer 7 Firewall can be used to block traffic based on the destination country of outbound traffic and the source of return traffic."   MX Firewall Settings - Cisco Meraki Documentation ... View more

No sorry, it is shared with a confidentiality notice - you should raise a ticket with Meraki support and they will send it with you. ... View more

Thanks for the heads up - we have just received the RCA from support after asking. ... View more

@MiriamK love the new look but we are still lacking a column/filter for the Org name the case is raised against. As an MSP with access to over 100 Orgs this would be really useful. ... View more

That is just a thing with Secure Connect on any MX, not just vMXs! ... View more

Either NMVPN from every network to the 3rd party, or install a second MX into HQ, have the NMVPN from there and then static route to it from the main HQ MX. ... View more

Now on the Meraki status page: Meraki Status - EMEA Cloud Monitored Catalyst Switches appearing offline in the Dashboard ... View more

Yes - we are experiencing the same this morning. Interestingly out of 8 switches, 1 has recovered and is displaying online again but the other 7 are not.   No feedback yet on our Meraki support ticket. ... View more

Sounds like you need to be ringing Meraki support and having them assist in getting your network back online. ... View more