Are most of the MS390 issues fixed yet?

[Flembot]

Towards the end of September 2022 our office which uses x2 MS390s and the other switches are MS225s - the switches in the entire office kept losing connectivity every once in a blue moon. It was terrible. The entire office used to go down unpredictably maybe once a week for about 10 minutes. 

This was detailed in my thread that the time 

To fix this - Cisco kept the 225s on 14.33.1 firmware, whilst upgrading the two 390s to Beta firmware. This solved the issue. 

Now the time is approaching whereby 14.33.1 is becoming more and more out of date and so is the beta firmware on the 390s. 

I'm planning to email Cisco to ask them to remove the firmware lock and allow all of our switches to upgrade. 

My question is, since the beta firmware 15.14.2 - have Cisco fixed up most of the issues on the MX390s now? 

[cmr]

@Flembot if you follow my firmware posts, either in the switch forum, or the firmware feed, you can see many many MS390 fixes since 15.14.2.

[cmr]

15.15, 15.16 and 15.17 combined contained the below list of fixes, since then we have had 15.18, 15.19, 15.20 and 15.21:

• MS390 management plane may hang and fail to restart until the entire system reboots (present since MS 15)
• MS390s will report a stack topology change erroneously (present since MS 15)
• MS390s will intermittently track clients on the uplink with uplink sampling disabled when the uplink is flapping between ports or on initial bootup (always present)
• MS390 modules may fail to be reflected in dashboard (present since MS 15)
• Event log isn't generated if an MS390's configuration was rolled back or reverted (present since MS 15)
• MS390 IPv6 interfaces do not have RA suppression configured by default
• MS390 AMI duplicate address detection will fail (present since MS 15)
• MS390 management plane in rare instances will restart when configuring port-channels
• Removing ACLs from MS390s can silently fail when network boundaries are not correct (always present)
• MS390 management plane may experience boot loops (present since MS 15)
• MS390 ports fail to be configured with static speeds resulting in ports always staying in auto-negotiation mode
• Client authentications may fail on MS390 during periods when there's multiple authentication attempts, such as, during a reboot (present since MS 14)
• MS390 port status is not correctly reflected in dashboard (present since MS 15.14)
• MS390s will show different information on the "Switch > DHCP Servers & ARP" page depending if it's configured to act as a server or not (always present)
• MS390 Storm Control configuration is not applied correctly if multicast along with other traffic types are configured (present since MS 14)
• MS390s retain their Storm Control configurations after it's removed from dashboard (always present)
• MS390s in some circumstances will fail to populate all DHCP clients that it's serving (always present)
• MS390 switches do not learn traffic details from IPv6 traffic
• Access policies removed on dashboard may not fully remove the configuration on MS390s which could result in conflicts if a new policy is configured
• DHCP may become disabled on MS390s with very specific and unique pool configurations set (present since MS 12)
• MS390 series switches may experience rare management plane restarts due to dashboard statistics syncing (present since MS 15.14.1)
• MS390 event logs are misleading for port security violations when clients move between ports (always present)
• MS390 LLDP system name is incorrect (present since MS 15.15)
• MS390 deauthentication messages are displayed for all received MAC addresses, regardless of if they were authenticated or not (always present)
• Changes made to MS390 switches may take a long time to apply, or completely fail (present since MS 15.15)
• MS390 IPv6 QoS does not take effect (always present)

[Brash]

From my understanding, the MS390 is far more stable than previously but still has its issues.

That said, I don't have any MS390's deployed so take that opinion with a grain of salt.

As @cmr mentioned, there's been a mountain of MS390 fixes in the last few firmware drops.

Given your previous issues, it might be worth engaging support early on to advise of any known issues (other than those documented in the release notes) on the version you're jumping to.

[Flembot]

Sounds good. Thank you all !