We updated several MX-100 and one vMX100.  the vMX100 (virtual) updated to 16.16 without issue and is currently still on that version with a scheduled upgrade scheduled.  The issue we had was with our physical MX100.  When upgrading to 16.16 all of our MX100's would drop out, consistently, every hour for about 10-20 minutes, consistently.  We were able to roll them back successfully.  I tried several times but eventually updated them to version 17.6 which resolved the issue.  The issue had to do with an upstream SFP connection at the DMARC.  We have been running version 17.6 without issues for several months.  We have not had any bandwidth issues on 17.6 and will upgrade to 17.8 this next week. ... View more

I was able to update to 17.6 which fixed the issues with the upstream SFP port.  This is currently working for us.   Also, not sure but the rollback option for Security devices is a bit different. I believe you have to go to Organization > Monitor > Firmware Upgrades and then on the overview tab you have to look under most recent changes, go back to where you updated to 16.16.1 and then select the rollback icon from there.  I know trying to schedule an update and targeting a previous version will not allow you to select next. ... View more

This has been escalated to engineers. ... View more

firmware updates were completed over the weekend to 28.6.1. with no resolution in the senor issue.   The three sensors that I have appear to come up for a while and then no longer report to the dashboard.  I have also pulled the batteries, factory reset them, and removed and added them back to the network.  Same issue.  Still working on it and I have opened a case.  Meraki is slow to work on this through the case so I will probably have to call them. ... View more

Thank you. We also updated our wireless firmware during that same maintenance period.  I have opened a case with Meraki.  We are new to the sensors and oddly the sensor gateways are not devices that are nearest to the sensors.  I also don't see a way to manually set the gateway device.  They both are connected to MR33 on version MR 28.6.  We have the firmware update scheduled for MR 28.6.1 this weekend. ... View more

I have to strongly agree.  How can a release with significantly reduced VPN throughput as a known bug be a stable release candidate?  This statement is concern enough to cause pause. We saw issues with MX16.16 and the SPF issue, reverted all our sites to MX15.44 and then updated one site, low risk, to MX17.6.  I would like to know what significant means before updating our major sites. ... View more

Do you by chance have a link to this bug or something I can read more?  Thanks ... View more

It was an MX100 and I don't since it is one of our smallest (in sqft) offices.  It was our test site and we have two other, much larger, sites to update.  I will take a look and see if there is anything worth reporting to the community. ... View more

Updated one site to 17.6 and it's been over an hour with no issues.  Looking promising, Thanks!   ... View more

The more I think about it I bet there is an upstream SFP port.  Thank you.  I may try and update to 17.6 and see what the results are. ... View more

Interesting.  We are not running any SFP ports on our Firewalls though and it appears to be affecting our internet ports only.  Digging into the way back, I have seen something similar when we had an issue with the smart jack (timing maybe).  I wonder if I put a switch between the smart jack and the firewall if I get the same issue. ... View more

Interesting.  The timing seems to be very consistent.  I tried a single site tonight to see if maybe doing all of them relatively close together may have caused an issue with our point to point vpn's.  Same issue. ... View more

We have not and attempted our second update tonight.  Same issue and rolled back to MX15.44.  We did successfully install update on vMX100 and MX64.  All of our MX100's have had the same issue. ... View more

We have updated a virtual vMX100 and an MX64 to version MX16.16 successfully.  Not sure that helps. ... View more

We also have had an issue with MX16.16 on MX100 devices being unstable.  We have had an experience were the device will reboot every 55 minutes for about 10 minutes and then repeat.  We have had to rollback twice.  We will be scheduling an update with Meraki on our next attempt. ... View more

We experienced an issue after updating to MX16.16 where the appliance would reboot/go offline about every 55 minutes and take about 20 minutes to come back up.  We experienced this over 4 hours before rolling back, successfully.  We were able to successfully update our software MX device in the cloud but our physical MX100's failed at three sites.  I have an active ticket open with Cisco. ... View more