You can review the source IOS XE RNs here: https://www.cisco.com/c/en/us/support/ios-nx-os-software/ios-xe-17/products-release-notes-list.html
While IOS-XE features do not directly map to Meraki any new features added in 17.10, 17,11, and 17.12 would now exist in the base code and be able to be Merakified if desire existed.
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
- 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.
- 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
If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
