Meraki

dfurasek · ‎Jan 10 2023

In general, we were purchasing the MR42 from 2016 through 2018. I realize that some of these will be ten years old in 2026, but what bothers me is that the amount of time between the end-of-sales announcement and the end-of-support date is significantly less for the MR42 when compared to what it was for the MR34. For what it's worth, I was told on the phone by a Meraki rep as recently as late 2020 that nothing had been said (internally or externally) about the retiring of the MR42, but that conversation unfortunately ended up being not long before the MR42 end-of-sales announcement. One way or another, we'll deal with it, but I'm just a bit surprised by the timeline. The other piece of the puzzle for us is that these AP replacements are typically something that we like to do while our schools are out for summer, but the end-of-support date in July (versus October for the MR34) might make things a little tight...

dfurasek · ‎Jan 6 2023

I have to say that this is not cool on Meraki's part. With the MR34, the period between end-of-sale (10/2016) and end-of-support (10/2023) was seven years. With the MR42 (the designated replacement model for the MR34), that period has indeed been reduced to four years, as outlined here: https://documentation.meraki.com/@api/deki/files/18680/MR42_EOS_Notice_updated_June_2022.pdf Interestingly, that very same document contradicts itself by stating the following: "End-of-Support Date (EOST): The last date a product will be affirmatively supported by Cisco Meraki, typically five (5) years following the EOS Date." We're replacing our last remaining MR34 devices this year, and we could really use an extra year to get all of our MR42 devices replaced. I'm typically not one to complain, but I think I would really like to try pushing to get end-of-support for the MR42 pushed out one more year until 2027. Are there any recommendations on how to best and most effectively go about making such a request?

dfurasek · ‎Feb 3 2021

It seems like Meraki is really anxious to get this update out the door. Unless I missed it (entirely possible), I think they skipped public beta and went straight to RC for this one. Also, they've already auto-scheduled it twice for us, even before moving it into the stable release bucket, and since I don't recall that ever happening before, I've cancelled it both times. Of course, RC is better than beta, but stable is better than RC, as we were bitten once in the past by a premature RC update. In any case, I'm running it on just one of our networks, with no problems seen so far, but I'm a little leery about pushing it out to the others before it's finally declared stable, especially if they did indeed skip the beta stage. The release notes do mention two jQuery related CVEs that are classified as "medium" severity, but that doesn't seem to be enough to warrant this level of urgency. Anyone have any commentary on what I might be missing in all of this?

dfurasek · ‎Dec 11 2019

Here are the "wishes" that I've submitted from within the dashboard in the past. So far, none of them have been implemented, but here's hoping... 🙂 1. I wish the "Firewall & traffic shaping" page for wireless networks provided the ability import/export a set of layer 7 firewall rules, which would eliminate the need to manually rebuild our entire list of rules when creating a new SSID. 2. I wish the "Access control" page for wireless networks would offer a "strict priority order" versus "round robin" option for RADIUS server load balancing when using WPA2-Enterprise with our own RADIUS servers, similar to the feature that you already offer when using your splash page RADIUS features. 3. On the client detail page for a MR wireless client, there is a link to the MDM client detail page. I wish this page would do the same thing in the other direction, by linking directly to the wireless client detail page for any MDM client is also a wireless network client. 4. My dashboard account allows me to access multiple organizations, but I spend the greatest portion of my time working with just one of them. I wish that I was able to choose a "default" organization in my account profile, such that I would not be presented with the "choose organization" page every time that I log in. From there, I could easily switch to one of the other organizations from the navigation pane if/when needed. 5. I wish the block page that is triggered by a layer 7 firewall rule could be customized, such that more information about our policies could be communicated to the end-user via that same page.

Meraki

Community

About dfurasek

dfurasek

Community Record

Badges

Re: End of support for MR's - was 7 years now only 4 years ?

Re: End of support for MR's - was 7 years now only 4 years ?

Re: New stable release candidate firmware 27.6: PSK connection reporting bu...

Re: A Guest Community Challenge!