WAN uplink change events are in the event log and can also be configured to send an alert via email or webhook.   You may also want to check out this tool and see if it provides the info you want https://developer.cisco.com/docs/meraki-tools-google-sheets-add-on/ ... View more

Assume you’re asking due to your proposed design of landing MPLS on a MX LAN port. While you can land MPLS on LAN that route is then primary and only upon failure will it take the internet/autovpn path.  You should consider landing the MPLS connection on a WAN port. Then you get SDWAN and autovpn over the MPLS path.  There are a number of docs that cover the topic both on our site as well as user sites like this one  ... View more

Does the event log or Security Center show anything? Maybe IDS/IPS or AMP are catching something and blocking it? Or, even content filtering?   The server and clients are all behind/on the inside of the MX? ... View more

as long as the security policies and included subnets match on either end it should work. a google search found a few blogs in which people got it working. some even included screenshots of both the meraki and fortigate configs. ... View more

I'm the "support" guy  😉 Actually, just a field TSA (SE) pitching in where possible to get folks back up and running.   Anyway, in this case due to a prior support case firmware was statically set or pinned we call it. For whatever reason it was only pinned on one of the two MX's in the HA pair. That's no good and the HA pair was seeing lots of VRRP transitions and dual master situations.   @IllinoisCollege to your point about load on the MX that is something I noticed and might be an issue. You look to be at the upper limit of clients we recommend on a MX450. You might want to engage Support again as they can see more info than I can with regards to flow counts etc that would show the true load on the MX. ... View more

cmr is pretty close here. At times supplies/suppliers need to change subcomponents and it means a hardware rev change. Key here is functionality and performance are expected to be the same regardless of rev.   And no, it's not beta nor did it get mGig. The MX250 already has 10G WAN and LAN ports anyway 😉 ... View more

https://documentation.meraki.com/General_Administration/Licensing/Meraki_MX_Security_and_SD-WAN_Licensing#:~:text=Can%20you%20move%20from%20one%20MX%20license%20edition%20to%20another%2C%20for%20example%2C%20Enterprise%20to%20Advanced%20Security%20or%20SD-WAN%20Plus%3F ... View more

screenshot? ... View more

did you get this resolved? if not, can you send me your dashboard URL via direct message? ... View more

yeah sounds like a voltage dip (or spike) freaking out the power supply maybe ... View more

my primary feedback would be that this page https://meraki.cisco.com/support/#policies:eol and this page https://documentation.meraki.com/General_Administration/Other_Topics/Product_End-of-Life_(EOL)_Policies are often not in sync with regards to the product list.    for example right now the first link ends at the poe injector while the other page has more recent EoX announcements. more than once customers have pointed to one doc and i gave to steer them to whatever the most recent link is to get accurate EoX info. ... View more

I've seen cases in which downgrading to older 25.x releases helps with stability on the older AP's. It's often case by case based on config and usage.   The last case I see on this opened by you was Dec 2020. Perhaps open a new case online and request a downgrade to 25.14 to test stability. You could have Support downgrade just a single AP (or however many you want) to the older release so you can contain the testing to an area before downgrading all AP's. ... View more

26.8.2 is the stable release for the MR34. I would recommend upgrading to that and see if it resolves the issue. In dashboard the current stable is 27.7.1, but it will run the MR34 at it's max which is 26.8.2.   You might want to also shoot a case over to Support so they can look at the logs and see if something more obvious is occurring.  ... View more

The 2 ethernet port AP design was relatively short lived by Meraki and all Enterprise AP vendors. It predated mGig and offered a way to get a little more bandwidth to an AP. It also brought downsides: requires 2 cable runs =$, 2 switchports =$, and the AP only received PoE on one port so it didn't provide any level of resiliency should that upstream switch go down.   1Gbps is still sufficient to the AP in many deployments. As mentioned though most mid-tier and higher Wi-Fi 6 AP's include mGig. Pair that with a Meraki mGig switch (or any vendors mGig capable switch) and you have the extra bandwidth you need.   Entry level Wi-Fi 6 AP's typically top out around 1 gig of actual real world throughput and that's why you'll see them have a 1Gbps port. The higher end 4x4 and 8x8 AP's can have real world throughput numbers in the 2-3 gig range hence why we include either 2.5Gbps or 5Gbps mGig ports on them.   And it's a bit forward looking, but when Wi-Fi 6E comes out it will bring even higher throughputs and really drive the use cases for mGig switches. ... View more

i've had a customer test it and it worked as advertised. note it's still in beta and needs to be enabled by support or a meraki se.   https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MX_Security_and_SD-WAN/Meraki_SD-WAN#SD-WAN_over_Cellular ... View more

how often are you seeing this event? it typically occurs when a config change is made and for a brief moment the configs are out of sync. so it's typically a benign message in warm spare configs. ... View more