Meraki

jimmyt234 · ‎Mar 25 2024

https://documentation.meraki.com/General_Administration/Firmware_Upgrades/Product_Firmware_Version_Restrictions

jimmyt234 · ‎Mar 22 2024

https://sites.google.com/meraki.net/merakitechtuesdays/recordings

jimmyt234 · ‎Mar 1 2024

I would go up to .8, not down to .2

jimmyt234 · ‎Feb 29 2024

+1, I believe locally sourced traffic will not abide by your layer 3 policies.

jimmyt234 · ‎Feb 29 2024

The firmware status for 18.107.x seems broken to me, as if you're running 18.107.2 it will say you're good whereas if you're running anything from .3 - .7 it will say warning/critical because there is a .8 patch available.

jimmyt234 · ‎Feb 28 2024

We've had 18.208 pushed to a lot of customers and had a myriad of issues which were resolved by rolling back to 18.107.X: - 1:1 NAT issues - non-Meraki VPN peer issues - random reboot issues

jimmyt234 · ‎Feb 28 2024

We've experienced the same problem and had to rollback to 18.107.x

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.

About jimmyt234

jimmyt234

Community Record

Badges