New MS 15.9 beta firmware - SecureConnect and reliability fixes

cmr
Kind of a big deal
Kind of a big deal

New MS 15.9 beta firmware - SecureConnect and reliability fixes

Switch firmware versions MS 15.9 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.
  • MS390 ports are not disabled when configured to do so in dashboard (present since MS 15.1)
  • 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 upgrades from MS 15.8 or later will result in minimal impact to client traffic

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

  • MS120/125 series switches with a storm control configuration do not correctly police traffic (always present)
  • When dashboard authentication services for SecureConnect are unreachable, ports may report the incorrect status
  • MRs may fail to authenticate via SecureConnect if dashboard connectivity is not established at the time of the authentication request
  • MS390 platform switches send excessive client deauthentication event log messages
  • SecureConnect fails on MS355 platform switches (present since MS 15.1)
  • Custom IPv6 DNS servers would not be correctly applied
  • Stack members may go offline and require a reboot to regain connectivity (present since MS 12)

Known issues

  • Port isolation fails to isolate traffic between ports (present since MS 15.9)
  • 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)
  • 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)
  • 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)
  • Cable tests run on 100Mbps connections may return the wrong information (predates MS 9)
  • 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)
  • 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)
  • 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

MS12x

  • Ports with an odd-numbered MTU value fail to initialize for MS120/125 series switches (predates MS 11)
  • In rare instances, MS120 series switches may have empty packet captures until they are rebooted
  • 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)
  • 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)

MS2xx

  • 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)

MS3/4xx

  • MS350-24X and MS355 series switches do not negotiate UPoE over LLDP correctly (predates MS 10)
  • 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)
  • Enabling Combined Power on MS350/355 switches results in events being logged once per minute (present since MS 11)
  • 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.
  • 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)

MS390

  • MS390 stack members may experience a full system restart
  • When the MS390 management plane experiences a restart, LACP flapping can occur
  • 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)
  • Packet loss is observed when pinging the MS390 management IP (present since MS 12)
  • MS390 "Port Up/Down" events will be shown across all members
  • MS390 series switches do not support loop detection
  • MS390 series switches do not support warm spare/VRRP
  • 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 (present since MS 15.1)
  • Rebooting an MS390 switch in a stack via the UI will result in the entire stack rebooting
0 REPLIES 0
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