New CS 17.2.3 stable firmware: fixes a container crash issue and occasional slow/incomplete booting

cmr
Kind of a big deal
Kind of a big deal

New CS 17.2.3 stable firmware: fixes a container crash issue and occasional slow/incomplete booting

CS firmware versions CS 17.2.3 changelog

Important notes

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

New feature highlights

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

Fixed issues

  • Resolved a bug that occasionally caused the Meraki container to reboot and temporarily lose Dashboard connectivity
  • Fixed a bug that sometimes caused longer than expected boot times, and in very rare circumstances could cause switches to fail to communicate with Dashboard

General known issues

  • 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 my answer solves your problem please click Accept as Solution so others can benefit from it.
5 Replies 5
Jay14
New here

How does this fall in regards to C9300-M in regards to CVE-2025-20352

cmr
Kind of a big deal
Kind of a big deal

As the CVE state is currently this:

 

Workarounds: No workarounds available
 
I would suggest that if you have SNMP enabled on the switches, it is vulnerable.  The beauty of Meraki is most networks I have dealt with don't need the additional monitoring of SNMP as the dashboard and APIs provide enough detail.  In that case SNMP is disabled so the switches should not be vulnerable.
If my answer solves your problem please click Accept as Solution so others can benefit from it.
cmr
Kind of a big deal
Kind of a big deal

And for clarity, this release is based on 17.15.4 and the fixed release is 17.15.4b 

If my answer solves your problem please click Accept as Solution so others can benefit from it.
CKnetworking
Here to help

Hi,

 

unfortunately, I need to correct you here.

 

CS 17.2.3 is based on IOS XE 17.12.4 and the fixed release would be 17.12.6.

 

IOS XE 17.15.4 and 17.18.1 are "natively" available in the Meraki Dashboard as stable release candidate (17.15.4) and beta (17.18.1) and their fixed releases would be 17.15.4b respectively 17.18.1a.

 

Best regards,

Chris

cmr
Kind of a big deal
Kind of a big deal

Apologies there, I misread the notes and went down the wrong rabbit hole!  Either way it isn't fixed yet, so best to restrict, or turn off SNMP!

If my answer solves your problem please click Accept as Solution so others can benefit from it.
Get notified when there are additional replies to this discussion.