New CS 17.2.1.1 Firmware Release

[Mloraditch]

A few extra bug fixes from 17.2.1 and some different known issues.

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

• The local status page has been enhanced to enable managing the allowed VLANs range using a single configuration option
• Fixed a bug with client analytics on Access switch ports that prevented clients from being correctly listed in Switch Summary, Switch Ports, and Client pages
• Resolved an issue that caused MAC flapping and packet loss on downstream switches
• Introduced measures to significantly decrease occurrences of the Meraki container becoming trapped in a reboot loop while switches maintain data traffic flow. This scenario may still occur in rare cases.
• Corrected an issue that caused stack ports to be incorrectly displayed as "Disconnected" after a stack member was rebooted
• Fixed a bug that caused the Static Gateway IP to display as '0.0.0.0' in the L3 Routing Switch tab
• Resolved an issue that occasionally prevented the uplink port from being identified correctly on the Dashboard. This issue did not affect device connectivity.
• Fixed a bug that caused a brief period of L3 traffic loss after the active member of a stack failed over
• All new LAG configurations will block redundant links if the connected device is not configured for LACP. This change fixes an issue where switches would sometimes move LAG ports to an active forwarding state prior to LACP convergence, creating the potential for loops. The change does not apply to existing LAG configurations.

Ms390 fixed issues

• Resolved an issue that prevented the application of fixed IP assignments if the IP being assigned had an active DHCP lease
• Fixed a bug that would infrequently prevent MS390 stacks from converging after a failover

C9300 known issues

• Some C9300X stacks have been reported to fail due to memory exhaustion, requiring an ios restart to restore service

Ms390 known issues

• In rare circumstances, MS390 stacks may display UDLD loop detection alerts that cannot be cleared by cycling the looping port
• MS390s may display an alert, "A power supply is offline" when a PSU isn't installed in the second slot

[Boston]

will this fix the issue i am having where all my clients show as connected to the firewall uplink port? 

[Mloraditch]

It could be this fix:

• Fixed a bug with client analytics on Access switch ports that prevented clients from being correctly listed in Switch Summary, Switch Ports, and Client pages
  
  

If you've got an open support case tied to a bug, they should be able to confirm if your case matches this. Or if you've never contacted support you can open a new case and they should also be able to match it up.

[dmarsh10]

We have Catalyst C9200 switches and the Meraki Cloud management shows that we need to update our switches from CS 16.9 to CS 17.2.1.1 while the Catalyst C9200 webpage/CLI shows we are running 17.12.5.  I've researched it and the suggested version for the C9200 is 17.12.5, but the warning in the Meraki Cloud management is annoying.  Are these versions interchangeable or why is there a version discrepancy between the Meraki Cloud and Catalyst webpage?  Thank you.

[cmr]

@dmarsh10 the upgrades refer to the cloud managed version and you are using cloud monitored which is on the next tab.  All switch networks have a CS and MS version even if they only have cloud monitored switches.

[cmr]

17.12.5 is the IOS-XE version.

[dmarsh10]

Thank you.   I believe our C9200s are only cloud monitored and can't be cloud managed.  So 17.2.1.1 wouldn't work even though the Meraki cloud tells me to upgrade to it?  Having 2 versions is somewhat confusing.  

[AndrewManning]

I have several MS390 all on this new firmware but they still say an update is available 

Is this a known issue?

[cmr]

It's the IOS-XE versions.