New CS 17.1.3 stable release candidate - stack failover and PoE reporting fixes and don't stack 5+!

cmr
Kind of a big deal
Kind of a big deal

New CS 17.1.3 stable release candidate - stack failover and PoE reporting fixes and don't stack 5+!

CS firmware versions CS 17.1.3 changelog

Important notes

  • This version's IOS image is based on 17.12.3 CCO. Upgrades to this version will result in a full system reload.

New feature highlights

  • Client Analytics
  • Device Uptime for MS390s
  • EEE (Energy Efficient Ethernet) Support
  • Multi-auth with support for guest/failed/critical
  • RADIUS Caching
  • VLAN to SGT mapping

General fixed issues

  • Fixed an issue causing switches to restart after stack failovers
  • Fixed an issue that caused incorrect PoE usage data to be shown in dashboard

Ms390 fixed issues

  • Fixed a problem that allowed MS425 devices to perform client sampling on ports directly connected to downstream MS390 switches
  • Resolved an issue that prevented the application of fixed IP assignments if the IP being assigned had an active DHCP lease

C9300 known issues

  • Downstream clients may experience packet loss for 60-200 seconds stack while the standby switch takes over the active stack member role when the active stack member is powered off

General known issues

  • Management plane connectivity may be interrupted when there are a large number of LLDP announcements
  • Meraki native switches move LACP ports to an active forwarding state if configured. This can cause loops when connecting to an MS390 or other Catalyst switch unless the bundles are configured on the Catalyst side first. All Meraki native ports are configured in passive LACP mode so that loops do not occur between Meraki native switches (always present)
  • Stacks of 5 or more switches may experience a configuration mismatch when making multiple consecutive port configuration changes to several interfaces in a row
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