That's a lot of fixes! 😎
Upgrading just now.
Edit: looking good so far!
Do you do any VPN or 1:1 I have rescheduled my update because the last time Meraki did a auto update it broke VPN and 1:1.
I updated two networks from 18.208 to 18.211 last night and one of them lost autovpn site to site connectivity completely. Rolled it back this morning.
Still a lot of stability issues, hopefully the fix list won't shrink...
MX18.2.11 was supposed to be the first 'stable' version. Wonder what happened.
It needs to reach at least 15% global network saturation prior to being promoted to stable (Meraki Firmware Release Process - Cisco Meraki Documentation). We've seen at least a dozen customer orgs have an auto-upgrade scheduled for this version overnight, so it seems Meraki will push this one out quite aggressively to reach this limit in order to get it to stable.
Yes you are right. forgot about that part.
Which also means that MX18.2.11 will be the only stable version. Other fixes will only be included in patches ( 18.2.11.X )
Yes 😄
18.210 has been pretty solid for us, hoping for the same from .211!
We still have a large number of devices that are 4G only on 16.16.9 due to mobile connectivity issues on 17.xxx
Is that resolved here or does it fall under this known issue?
I updated one of my test sites that had this similar issue on 18x running the 4G SIMs. Are you using static or dynamic APNs? I updated mine to 18.211 using a static APN and associated with the proper location and worked perfect. the 18.210 broke this
· West: WE01.VZWSTATIC
· Midwest: MW01.VZWSTATIC
· Northeast: NE01.VZWSTATIC
· South: SO01.VZWSTATIC
I had a customer that had to rollback to 18.210 this morning because 18.211 broke site-to-site AutoVPN.
He told me Meraki TAC told him that they have a number of customers experiencing issues with this version today.
I installed it on all of my company's MX and it is working fine for us and we have one AutoVPN connection that is also working
fine. My advice is to test it on non-production networks first to see if your environment is impacted.
I've installed it on an MX68 that is acting as an AutoVPN spoke and it seems to work okay, being stable and performing normally. It is only running the enterprise feature set, so issues might be related to advanced licensing?
We YOLO'd this update to our "test" site which is our corp office. MX95. So far so good...we got burned hard on the last "stable" RC so we're taking a bit of a gamble here but I liked the fix list.
For me, SNMP stopped working with this release.
What version of firmware were you using prior? I heard mention of possible snmp issues here. We are on 18.210.
Had to roll back to 18.210, had vpn issues on the site I tested it on.
I was on 18.210 and many other older versions. 18.211 is the version that broke SNMP for me. I have a ticket opened up on this version.
I have a scheduled upgrade for 4 sites for this weekend, are there any known issues with this present release MX 18.211 apart the one mentioned above. Thanks
@bdeen from the release notes the below are all known issues, hopefully there aren't too many more:
Ever since the upgrade to this version, all our Meraki switches' DNS entries were changed to 1.1.1.1 and 8.8.8.8. Causing intermittent disconnections across our switches now. Anyone have similar issues or how can I revert back to the older version?
After the upgrade to 18.211 large portion of our clients were not able to use internet because of DNS problems on the MX gateway: Client made a request to the DNS server, but it did not respond (no_dns_response).
We use DNS passthrough option: Client -> MX Gateway -> Google DNS. There are two gateway in hot-standby mode
We rolled back to 18.208 and the DNS issue seems to be gone.
Edit: We do have one high priority traffic shaping rule enabled.
Release notes have been updated with:
Wow @jimmyt234 that is a bit of a major bug! Glad we'd only updated a home user Z3 so far that doesn't have traffic priority rules set 😬
Hey awesome people in the Community,
Thank you for the discussion and feedback here!
We have also provided some guidance regarding the issue with traffic being dropped in this post.
Please tag us here if there's anything else we can assist with, and make sure you raise a case with Support for tracking 🙂
Thank you!
Giac