New MX 18.107.4 Stable Release - fixes for advanced feature CPU overutilisation, still not available

cmr
Kind of a big deal
Kind of a big deal

New MX 18.107.4 Stable Release - fixes for advanced feature CPU overutilisation, still not available

Security appliance firmware versions MX 18.107.4 changelog

Important notice

  • USB modems with MX/Z series devices running firmware MX 18 or newer will be limited to best effort support and will not be receiving any future firmware fixes or improvements.

Bug fixes

  • Corrected a rare issue that could result in excessive device utilization when intrusion detection and prevention was enabled.
  • Resolved an MX 17 regression that resulted in MX appliances no longer re-authenticating 802.1X clients.
  • Fixed a very rare issue on MX 18.1XX that could result in AutoVPN connections to devices on older firmware versions and teleworker VPN connections to periodically drop.

Legacy products notice

  • When configured for this version, Z1 and MX80 devices will run MX 14.56.
  • When configured for this version, MX400 and MX600 devices will run MX 16.16.9.

Known issues

  • After making some configuration changes on MX84 appliances, a brief period of packet loss may occur. This will affect all MX84 appliances on all MX firmware versions
  • Due to an MX 15 regression, the management port on MX84 appliances does not provide access to the local status page
  • MX appliances will now properly validate that DBD packets conform to the appropriate MTU size. If the MX's OSPF peer has an improper MTU configured, it may cause the OSPF adjacency to fail to properly form. The updated behavior properly conforms to RFC. Please ensure these settings are
If my answer solves your problem please click Accept as Solution so others can benefit from it.
4 Replies 4
DarrenOC
Kind of a big deal
Kind of a big deal

but you can't upgrade to it @RaphaelL  🙄☹️

Darren OConnor | doconnor@resalire.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.
Brash
Kind of a big deal
Kind of a big deal

  • Corrected a rare issue that could result in excessive device utilization when intrusion detection and prevention was enabled.

 

This is an interesting one.

Not sure how rare it was as it's definitely popped up a few times in the forums.

ww
Kind of a big deal
Kind of a big deal

> this one is missing some words 

 

 

 

  • MX appliances will now properly validate that DBD packets conform to the appropriate MTU size. If the MX's OSPF peer has an improper MTU configured, it may cause the OSPF adjacency to fail to properly form. The updated behavior properly conforms to RFC. Please ensure these settings are ...
CyberDingo
Getting noticed

MX 18.107.4 is now able to be upgraded from 18.107.2 in the dashboard.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels