New MS 15.8 beta firmware - MS390 management plane restarts fixed!

cmr
Kind of a big deal
Kind of a big deal

New MS 15.8 beta firmware - MS390 management plane restarts fixed!

Switch firmware versions MS 15.8 changelog

Alerts

  • HTTP proxy is no longer supported on MS 15+. Nodes that use HTTP proxy without any other means to connect to dashboard may fail to connect.
  • SecureConnect fails on MS355 series switches (present since MS 15.0)
  • MS390 ports are not disabled when configured to do so in dashboard
  • Moving or re-provisioning an MS390 stack in dashboard can cause the management plane of at least one member to stay offline until rebooted (present since MS 15.0)
  • If SecureConnect is enabled on the network, MS390 access ports will not be a part of STP or receive broadcast traffic
  • MS390 upgrades to this version will result in a full system reload

Branch additions

  • STP anomaly detection support for MS390 series switches
  • IPv6 static routing support for MS390 series switches
  • Additional client analytics added for MS390 series switches
  • Meraki authentication support for MS390 series switches
  • Alternate Management Interface (AMI) support for MS390 series switches
  • UDLD support for MS390 series switches
  • Group policy ACL support for MS390 series switches
  • IPv6 management interface support
  • URL redirect support for MS390 series switches
  • UPoE (802.3bt) support for MS390 series switches
  • Critical/failed authentication support for MS390 series switches
  • Multi-auth with voice VLAN bypass support
  • MAC flap detection support for MS390 series switches
  • Named VLAN support for MS120/125/210/225/250/350/355/390 series switches
  • Stack power is supported by default for MS390 series switches
  • Netflow and Encrypted Traffic Analytics (ETA) support for MS390s

Bug fixes

  • MS390 series switches may experience management plane restarts, which would affect RADIUS authentication and dashboard connectivity (present since MS 14.26)

Known issues

  • When the MS390 management plane experiences a restart, LACP flapping can occur
  • Stack ports may fail to initialize properly upon reboot. A subsequent reboot of the switch would be needed (present since MS 14)
  • If the voice VLAN authenticates before the data VLAN, the voice VLAN will stop working after the data VLAN authenticates (present since MS 14.28)
  • MS390 stacks may send frequent DHCP requests despite having a valid static IP address, which can result in IP flapping (present since MS 14)
  • In rare circumstances, MS390 series switches may disconnect from dashboard until rebooted. Data plane traffic is not impacted unless RADIUS authentication is used (present since MS 14.28)
  • When applying an access policy to a port, voice VLAN clients will not be updated in the MAC table without bouncing the port (present since MS 14.28)
  • MA-SFP-1GB-TX links may fail to reconnect after link loss (present since MS 12)
  • Connecting a stacking cable to a stack that is online may result in a stack member going offline (present since MS 12)
  • In rare instances, MS120 series switches may have empty packet captures until they are rebooted
  • Packet loss is observed when pinging the MS390 management IP (present since MS 12)
  • In rare instances MAC addresses will fail to be relearned on ports configured with Access Policies. This is currently scoped to only impact MS210/250 models (present since MS 12)
  • Links being established on an MS120 can result in neighboring ports to flap (present since MS 11)
  • MS120 series switches in extremely rare instances will experience reboots every few minutes (present since MS 11)
  • MS390 "Port Up/Down" events will be shown across all members
  • Enabling Combined Power on MS350/355 switches results in events being logged once per minute (present since MS 11)
  • Networks containing a large number of switches may encounter issues saving changes on the Switch Settings page
  • Stack members may experience delays in updating their configuration for up to an hour after a config change (present since MS 9)
  • mGig switches will have an amber light for all physical ports that do not negotiate to the highest supported speed. Dashboard will continue showing a light green status for all ports above 100Mbps. For example, MS355 switch ports will incorrectly show an amber light for 1G, 2.5G, and 5G, but will show a green light for 10G.
  • The "clone from" list may fail to load when cloning a switch in an organization with 1,000+ switches or networks
  • Changes made to SVIs may result in connectivity loss for one or more SVIs until reboot (present since MS 14.31)
  • In rare instances, a stack member may go offline until rebooted (present since MS 12)
  • Broadcast types of traffic can leak into the Guest VLAN if a port that fails authentication has a voice VLAN configured, and dashboard has a Guest VLAN defined (present since MS 11)
  • MS120s switch ports with MAB authentication may randomly deauthenticate clients. In order to resume client authentication on that port, a switch reboot is required (present since MS 12)
  • MS390 series switches do not support loop detection
  • MS390 series switches do not support warm spare/VRRP
  • MS350-24X and MS355 series switches do not negotiate UPoE over LLDP correctly (predates MS 10)
  • AMI IP addresses do not send gratuitous ARP packets which can lead to packet loss if the AMI address has aged out in the network
  • Meraki authentication does not work with guest VLAN
  • Moving or re-provisioning an MS390 stack in dashboard can cause the management plane of at least one member to stay offline until rebooted (present since MS 15.0)
  • MS390 ports are not disabled when configured to do so in dashboard
  • SecureConnect fails on MS355 series switches (present since MS 15.0)
  • Ports with an odd-numbered MTU value fail to initialize for MS120/125 series switches (predates MS 11)
  • When an SFP module is inserted/removed on MS420/425 series switches, BPDUs can be delayed leading to STP transitions in the network (predates MS 12)
  • MS350/450 series switches in a stack configuration will lose dashboard connectivity if a "Deny Any Any" ACL is added without having higher "Allow" rules in place for dashboard connectivity (predates MS 12)
  • MS390 series switches will go offline if a "Deny Any Any" ACL is added without having higher "Allow" rules in place for dashboard connectivity
  • Rebooting an MS390 switch in a stack via the UI will result in the entire stack rebooting
1 REPLY 1
nl_aus
New here

Hi

 

Referring to this specific bug below:

 

  • In rare circumstances, MS390 series switches may disconnect from dashboard until rebooted. Data plane traffic is not impacted unless RADIUS authentication is used (present since MS 14.28)

 

I work in a large organisation that has just rolled out hundreds of MS390s (they were purchased well before i was involved in the project) - and this issue has been causing us major problems. I now read that this has been ongoing for quite some time and have been pushing it with Cisco support for a resolution ever since. Do you know if there is any kind of ETA to resolve this? Rebooting stacks at the cores of our many sites is not a viable solution.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels