New CS 16.6 stable release candidate - config and RADIUS fixes, almost no known issues!

cmr
Kind of a big deal
Kind of a big deal

New CS 16.6 stable release candidate - config and RADIUS fixes, almost no known issues!

CS firmware versions CS 16.6 changelog

Important notes

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

New feature highlights

  • 802.1X Control Direction
  • Adaptive Policy ACL hit counter live tool
  • MAC Allow list on access ports
  • Named VLAN

General fixed issues

  • Configurations fail to apply when Encrypted Traffic Analytics is enabled (present since CS 16.5)
  • RADIUS authentication can fail to correctly send packets to the RADIUS server when AMI is configured (present since CS 16)

General known issues

  • DHCP options longer than 180 characters may fail to be configured on the device resulting in the configuration being reverted (always present)
  • DHCP server information is incorrectly reported, such as, the subnet mask and "Last Seen" fields (always present)
  • 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)
  • Switches may fail to fully initialize after initial onboarding and migration. Devices encountering this will require an RMA (always present)
3 Replies 3
DarrenOC
Kind of a big deal
Kind of a big deal

That last one’s a doozie!

 

  • Switches may fail to fully initialize after initial onboarding and migration. Devices encountering this will require an RMA (always present)
Darren OConnor | doconnor@resalire.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.
cmr
Kind of a big deal
Kind of a big deal

@DarrenOC that's why you need an active hardware support subscription to onboard them 🙃

DarrenOC
Kind of a big deal
Kind of a big deal

Might as well just skip the whole on-boarding process and just ship out the Meraki replacement switch!

Darren OConnor | doconnor@resalire.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.
Get notified when there are additional replies to this discussion.