Meraki

jimmyt234 · ‎Feb 26 2024

Anyone else getting a new Assurance menu today? Seems to be collating a few bits from under Network-wide...

jimmyt234 · ‎Feb 26 2024

This may do something similar (haven't tried it, so can't verify): Francisco-1088/merakiLifecycleReport - Cisco Code Exchange

jimmyt234 · ‎Feb 23 2024

There is still no way to do this other than the workarounds already discussed.

jimmyt234 · ‎Feb 23 2024

You can also cancel it completely, rather than keep moving it.

jimmyt234 · ‎Feb 23 2024

Probably not quite what you're after, and a bit of a hack: but if you've got more than 1 MX in the network then you can configure the VPN client differently on each one and get the specific users only to connect to the relevant MX.

jimmyt234 · ‎Feb 23 2024

For anyone reading, I have been able to convert the public IP SKU from Basic to Standard by doing the following: Turn off vMX virtual machine Disassociate the public IP from the NIC Set IP assignment type to static from dynamic (this step may or may not be required) Do the upgrade from basic to standard by clicking the banner in Azure Associate IP back to the NIC of the vMX Turn on vMX

jimmyt234 · ‎Feb 23 2024

To expand on this, create a layer 3 outbound firewall policy to block these ports that @RaphaelL says above:

jimmyt234 · ‎Feb 23 2024

This is a back-end Meraki setting that you will have no visibility of and need to ask Meraki support to set.

jimmyt234 · ‎Feb 20 2024

Did anyone ever sort this? It's just coming across my radar now and we have several deployments for customers that appear to be using the Basic Public IP SKU in Azure.

jimmyt234 · ‎Feb 16 2024

There is some discussion happening over in this thread: Re: MX 18.208 release being pushed - Performance improvements added to the ... - The Meraki Community

jimmyt234 · ‎Feb 15 2024

It came out with 18.207, the previous stable release candidate version

jimmyt234 · ‎Feb 14 2024

See the FAQ at the bottom of this page: AnyConnect on the MX Appliance - Cisco Meraki Documentation In short, you cannot establish AnyConnect from within the network.

jimmyt234 · ‎Feb 1 2024

Wasn't jealous before, but now I am! 😆

jimmyt234 · ‎Jan 31 2024

Nice! Next up, Meraki branded headphones 🎧

jimmyt234 · ‎Jan 24 2024

Thanks for bringing this back, Ana. Really enjoyed the first series and have signed up for Season 2! 😄

jimmyt234 · ‎Dec 1 2023

What..................................................... I really wish all these secret options they can configure for us is made public knowledge somewhere. How are we supposed to know?!

jimmyt234 · ‎Nov 8 2023

https://status.meraki.net/incidents/dp7jydl8v5c4 Probably related to this ongoing incident.

jimmyt234 · ‎Sep 26 2023

Yes, grab the logs before you reboot.

jimmyt234 · ‎Sep 20 2023

I think you'll struggle / experience weird things if you try to have 2 Azure VPN tunnels to the same remote subnet. What you can do, and we have done a lot of, is peer the Azure VPN to the MX's DDNS hostname. This will resolve to the primary uplink IP during normal operation and then if WAN failure it will update and the Azure VPN should re-establish to the other WAN IP. This will be a lot slower and is less elegant and flexible than deploying a vMX, however.

jimmyt234 · ‎Sep 8 2023

In your diagram the offices are connected to the same switches in Area 1 and 2, does that mean they are in the same layer 2 broadcast domain and share the same LAN subnets? If so, you could run the MX105 firewalls in HA, with the one with 2 WAN connections being the primary unit and the other the spare.

jimmyt234 · ‎Sep 8 2023

Are the switches still online in the dashboard with the same LAN IP? DHCP or static?

jimmyt234 · ‎Sep 8 2023

You can achieve this with group policy rules against the client, best implementation is done via AnyConnect with RADIUS auth: https://documentation.meraki.com/MX/Client_VPN/AnyConnect_on_the_MX_Appliance#Group_Policies

jimmyt234 · ‎Sep 7 2023

Yes, traffic should automatically fail back to WAN 1 when it is up. You may need to change WAN failover behaviour to Immediate rather than Graceful (Connection Monitoring for WAN Failover - Cisco Meraki) Other that that, reach out to support as you have already suggested. No show tech required, just give them a ring and they will troubleshoot with you!

jimmyt234 · ‎Sep 7 2023

Yep - learnt about this the hard why like you did by having routing issues and Meraki support informing me of this secret back end route summarisation configuration that was enabled, issue was resolved after them disabling.

jimmyt234 · ‎Sep 4 2023

No, but I am sure any SNMP platform of your choosing could easily do this job.

About jimmyt234

jimmyt234

Community Record

Badges