Update: I tried rolling back the firmware update and still encountered the same issue with SFPs not enabling after MX reboot. It seems the issue is not related to 19.2.7, it was just revealed when the MX rebooted for firmware upgrade.   I ended up removing the copper RJ45 SFPs, disabling backup WAN 3 and reverting back to using the RJ45 ethernet ports on the MX. We lose the benefit of WAN 3, but at least we can reboot the MX ok without the SFPs going offline. ... View more

Updated MX105 to 19.2.7 and lost both WAN 1 and WAN 2 SFP connections but device is still up and running on WAN 3 which is not ideal.   We have RJ45 to SFP adapter modules installed in WAN 1 and WAN 2 since the RJ45 WAN ports are disabled when using WAN 3.   Luckily, we had WAN 3 connected, but without WAN 3 and the RJ45 SFPs we probably wouldn't have run into this issue in the first place. Anyone else seeing issues with WAN ports showing down after upgrade to 19.2.7? ... View more

Has anyone seen upgrade failures when going to 17.15.4? We've had some issues upgrading  C9300-48UXM and C9300-48P from 17.15.3.   After the upgrade, the switch goes offline in the dashboard but still appears to be switching traffic. In the dashboard event log we see:   "Image Install failed - Device is unreachable" and "Dashboard Upgrade Final Status - unreachable".   I'm able to access the local status page and it says "Something's not right" "Device is not connected to the Internet." event though it appears to have a valid uplink configuration.   Sometimes rebooting the switch gets it to go back online in the dashboard. Other times it has to be level 3 reset. ... View more

Is anyone able to packet capture on MS320 or MS220 running 17.2.2?  I get the following errors but it works on MS425.   Capture failed: 500. Unknown   Capture failed: 507. Net::ReadTimeout with #TCPSocket:(closed) ... View more

Interestingly my MS320 switches seem to have been able to upgrade to 17.2.2 even though they were not able to run 17.2.1  I assumed 17.1.4 was the last version for MS320 but it looks like 17.2.2 put some more life back in them just in time for me to replace them anyway. ... View more

Another possible oddity. The release notes now state "Instead, those switches will remain on their previously configured firmware version."  Does this mean that if your switch was not previously running 17.1.4 it's now stuck on whatever old version was previously configured?  Again, this seems different from access points which will update to the latest version that can run on the older hardware when the network is configured for a newer version. ... View more

Looks like the documentation has been updated as well. https://documentation.meraki.com/General_Administration/Firmware_Upgrades/Product_Firmware_Version_Restrictions#MS   Odd behavior to have the dashboard display "Not running configured version" because there no longer seems to be a way to see what version is running currently since that text replace the firmware version. For out of support access points this doesn't happen. For APs the dashboard displays whatever old version the access point is running. ... View more

Thanks for looking into this. The response I got on my support case was: " Unfortunately, the dashboard will not be changed. As mentioned, the MS320s have passed the end of support date, and the development team won't make any changes due to the devices no longer being supported."   Is this correct or will they still fix it anyway? ... View more

17.1.4 ... View more

Does it actually show 17.2.1 if you check the switch in the dashboard? The scheduled firmware upgrade shows complete but all our MS320-48FP are stuck at "Not running configured version". No recent changes in the network. The switches did not reboot after starting the upgrade. ... View more

Sounds like the documentation is wrong. Here's the response I got from Meraki support:  "Unfortunately, id does not look like the MS320s will be able to upgrade to 17.2.1. Since, these are end of support, they are no longer providing updates for these switches. The documentation may be outdated and will need to be updated." ... View more

Thanks for confirming. Glad to hear I'm not alone! ... View more

Let me know how it goes. Our MS320 switches are all stuck at:   Firmware Not running configured version Upgrade Status — ... View more

It's been several hours now and the MS320 switches are still showing "Not running configured version". I'll ask Meraki support but previously they said "these switches are end of support and we will not be able to troubleshoot" ... View more

Upgraded one of our networks. The MS425 took a while but eventually updated. The MS320 stayed on Upgrade Status: Started for a long time and eventually changed to Upgrade Status: -   They still show Firmware Version: Not running configured version.  Does this mean the update failed? Was MS 17.2.1 intended to be made available to the out of support MS320 or were they supposed to stay on an older version? ... View more

Have you tried the new 17.2.1 version? I noticed "Fixed a bug that prevented MS120-48 switches from correctly forwarding multicast traffic on ports 25-48" in the changelog. Not exactly what you're describing but sounds somewhat similar. ... View more

Not sure if this is related, but I wanted to share our experience with this Zyxel IDS detection. We were having issues with a DMVPN connection dropping out randomly and found that this Zyxel detection was showing Blocked action. I have whitelisted it as it appears to be a false positive for our environment. Just wanted to share in case anyone else sees false positives with this detection. ... View more

The official update says: "The Snort rules have been removed to reduce the impact. "  Was there another rule other than 1-60381 that was contributing to the issues? ... View more

Perhaps your Microsoft RDS VPN issue is unrelated to this IDS rule. Do you see any other rules in the security center relating to the impacted clients? ... View more

No, we saw the same thing and others have been reporting that as well. Adding it to one network seems to unexpectedly add it to all networks in the organization. ... View more

Latest update on the MO411804 incident: August 10, 2022 1:56 PM · Quick update The firewall partner is currently reviewing options to remediate impact. This quick update is designed to give the latest information on this issue. ... View more

Same here. It displays null, but everything is working. ... View more

Agreed, I don't think this should be marked as solved just yet.   Edit: Sorry, I see it was only marked as solved for visibility, not actually considered solved. ... View more

Same issue here. Looks like users on reddit reporting the same https://www.reddit.com/r/Windows11/comments/patot6/vpn_and_slow_speeds/ ... View more