Notably acknowledgement that the container can crash causing management connectivity loss. Wonder how much time they will really spend on this.
Important notes
- This version's IOS image is based on 17.12.4 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
- Support for Multicast in Live Tool
- VLAN to SGT mapping
General fixed issues
- Fixed a bug that caused stack ports on standby switches to incorrectly appear to be disconnected
- Resolved a bug during upgrades from CS16 to CS17 that sometimes caused PoE settings to change during the upgrade process
- Resolved an issue that sometimes prevented storm control settings from being correctly applied to member and standby switches in stack configurations
- Fixed a bug that caused inconsistent information to be displayed in the "Adaptive policy group" column when reloading the Network-wide > Clients page in Dashboard
- Resolved a bug that prevented the STP blocking icon from being correctly displayed in Dashboard when an alternate port was blocked by STP
- Resolved an issue that prevented clients and client traffic from being correctly displayed after moving the Uplink role between switch ports
- Fixed a bug that sometimes caused firmware upgrades to fail on stacks upgrading from CS16 to CS17
Ms390 fixed issues
- Fixed a bug that sometimes caused UDLD loop detection alerts that could not be cleared
General known issues
- The Meraki container may reboot in rare circumstances, resulting in temporary loss of connectivity to Dashboard
- Client traffic reporting may fail on high-speed (greater than 10Gbps) or trunk ports
C9300 known issues
- In rare circumstances, high levels of MAC flapping can lead to memory exhaustion in C9300X switches in stack configurations. An iosxe restart is required to restore service to affected switches.
Ms390 known issues
- MS390s may display an alert, "A power supply is offline" when a PSU isn't installed in the second slot
- Clients may fail to obtain a fixed IP address if their DHCP discover packet doesn't contain a client identifier field. These clients will instead be assigned an IP address from the DHCP pool.
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.