Sorry to reopen this thread, but I want to see if I understand how UDLD and STP guard should be set up on my topology. Here's the high level image from the dashboard. Very simple hub-spoke. Single uplinks from IDFs (either a stack of two or just a single switch) run back to MS425. Do I enforce UDLD and loop guard both ends, or just the uplink port for the IDF?   ... View more

Hi,   Thanks@MarcAEC for sharing, I stumbled upon this and the solution still seems to work good.   And it looks like the sharing of the 'disabled' routes is expected behavior as also described in the knowledge base:   https://documentation.meraki.com/MX/Networks_and_Routing/MX_Routing_Behavior   Advanced Configurations->Static Route Tracking: The route tracking mechanism only has local significance, which means, that the status of the route doesn't influence whether the route is advertised or not and it won't affect the routing on the remote end of the VPN.   Cheers ... View more

I can't believe three years later, that this is STILL a problem. I am losing faith in Cisco products related to security. I have the same problem with false positives other Cisco products with AMP and their support is horrid for these features.  ... View more

I usually make less use of the per client limit function unless it is a really slow link, or perhaps a strictly policed link. I do concentrate more on the 8 traffic matching rules you can define and make sure each goes into the correct queue.   If you do severely limit per client, then the speedburst alone is not enough, you'd need to match certain traffic types and let them go beyond the limit. ... View more

Sorry, I meant this option:   ... View more

@WillN  I had that same thought because of the short amount of time it was online.  I use templates to push out my configurations and my template uses version MX14.45 which is stable release.  I did not look to see what version is shipped so I'll have to wait for my replacement (RMA was initiated yesterday).  I am wondering if I should upgrade my code on the template to 14.50 but found these not so satisfying entries in the code notes.    Although 14.50 did say it fixed this:   Resolved an issue that could result in MX67(W) and MX68(W,CW) appliances entering a reboot loop if 802.1X port authentication was configured while wireless was also enabled.   The caveats still show this: "We have recently become aware of an issue introduced in this firmware version that may result in communication issues between devices connected to ports 3-7 and devices connected to ports 8-12 on MX68(W,CW) appliances. We are working to provide an updated firmware version that resolves this issue as quickly as possible. Until that version is available, we will not be scheduling any further upgrades to MX 14.50 and we advise customers take additional caution before upgrading further MX68(W,CW) appliances to this version."   MX67C, MX68CW, and Z3C units must be connected to the Meraki Dashboard initially to retrieve an update to allow for proper use of the integrated cellular connectivity. This is most likely to be an issue when bringing the units online for the very first time.     Edit:  Meraki shipped replacement with 14.40 so I downgraded my template to 14.40 and then tried again to add the MX.  Could have been just a coincidence and I did not have the luxury of trying to brick another one so I just downgraded before plugging it in.  But all worked out now but I do have my suspicions on the 14.45 code, which is no longer available.   Thanks all for the input! ... View more

Definitely would like to see API access to the Insight tool.  I just enrolled in another demo and I have seen several revisions of the GUI over the lifespan of the product.  Getting better but still struggle with getting timely data.  My use case is that I currently pull API data on the "UPLINK" to Google DNS but that only tells me if I have a problem with my link to my provider and if they are blocking ICMP to Google.   My real want would be to pull Loss & Jitter numbers and then maybe Latency & MOS.  These numbers are closer to what I see in my VPN statistics and show me when a provider decides to route my traffic out of state "around a problem".  Because UPLINK looks fine and does not drop but latency, Jitter and MOS take a beating.    Have submitted a /maw but will try and add context here in the hopes the Dev team might see.  ... View more

Thanks for opening the case. The more people that do that, the better the firmware will be for everyone 😃 ... View more

>then adding a voip rule there *would* prioritize my voip traffic as it leaves the MX and into my internal network?     Hopefully all your sensitive traffic is already DSCP marked.  AutoVPN preserves these markings.  Your internal switches should be able to use these to provide internal QoS.   This is independent of using the QoS option on the head end. ... View more

I also have this wish. ... View more

For customers where downtime is an issue, I only use the "stable" release train.  This does not get updated that often.  Maybe a couple of times a year, depending on the product line. ... View more

Thanks I did run across that but initially it looked like a setting for the uplink stats to 8.8.8.8.  But definitely pointed out in the documentation and also when you hover over the (i) icon in the dashboard, I see where it says applies to security updates including Malware.  Thanks PhilipDAth!! ... View more

This topic comes up enough that it would be beneficial for Meraki to include some information in the specs.  There are different types of fans, software is involved, some power supplies have fans, some fans are removable, noise levels, etc. ... View more

Hope this helps.  ... View more

@Charlie This is an AMA thread about managing Meraki's corporate networks. You should start a new thread in the relevant forum for your questions.  ... View more