A new beta switchCatalyst firmware is now available on Thu, 16 May 2024

[FirmwareBot]

A new beta switchCatalyst firmware version is available. Firmware CS 17.1.1 was just released on 2024-05-16 and has been in this firmware category since 2024-05-16.

[cmr]

CS firmware versions CS 17.1.1 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 (API Only)
• Multi-auth with support for guest/failed/critical
• RADIUS Caching
• VLAN to SGT mapping

General fixed issues

• Fixed an issue that in some circumstances prevented switches from restoring a safe configuration after incorrect configuration had been applied (i.e. disabling uplink)
• Fixed an issue where an event with system information could be generated when a support data bundle was created

Ms390 fixed issues

• Resolved an issue that could prevent link aggregation configuration from being applied when the active member rebooted in an MS390 stack configured for cross-stack link aggregation

General known issues

• 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)
• Switch Port Packet Counter live tool shows 0 packets on uplinks for all fields except for Live Data

Ms390 known issues

• MS390 stacks may experience an unexpected reboot when both active and standby EHSA are down
• MS390 stack configuration may experience high memory consumption and as a result could lead to authentication failures. Reloading the active switch clears the issue temporarily.
• MS390 stacks may fail to apply new configurations fetched from the network. This results from an issue with the NETCONF application, leading the system to revert to the previously stored configuration.