Meraki

Mloraditch

Factory-default VLAN range is now 1-995, instead of 1-1000 as in previous firmware versions. Resetting the device to factory settings will apply this new VLAN range.
This version's IOS image is based on 17.12.4 CCO. Upgrades to this version will result in a full system reload.

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 caused uplink ports to become stuck in an Uninitialized state
Fixed a bug that caused a brief period of L3 traffic loss after the active member of a stack failed over

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

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

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)

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

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.

Community