New MX 18.211.5.1 stable firmware - just one high load fix..

[cmr]

Security appliance firmware versions MX 18.211.5.1 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 - limited platforms

• Fixed an MX 18.211.5 regression that could result in MX75, MX85, MX95, MX105, MX250, and MX450 appliances servicing many clients to experience intermittent periods of heightened packet drops and latency.

Legacy products notice

• When configured for this version, Z1 devices will run MX 14.56.
• When configured for this version, MX400 and MX600 devices will run MX 16.16.9.
• When configured for this version, MX64(W), MX65(W), MX84, MX100, and vMX100 devices will run MX 18.107.12.

Known issues status

• This list is being reviewed and updated.

Known issues

• Trusted traffic exclusions will not function on Z4(C) appliances if AMP is configured.
• Due to a rare issue, MX appliances may fail to initiate non-Meraki site-to-site VPN connections when IKEv2 is used. This is most likely to occur when there are mismatched VPN subnets configured between the MX and the non-Meraki VPN peer. This will be resolved in MX 19.1 releases.
• Due to an issue under investigation, VMX-XL appliances fail to add local networks into the routing table.
• Due to an issue under investigation, MX appliances may incorrectly report 100% loss on the SD-WAN monitoring page.
• In rare cases MX75, MX85, MX95, MX105, MX250, and MX450 appliances may encounter an unexpected device reboot.
• Due to an issue under investigation MX75, MX85, MX95, MX105, MX250, and MX450 appliances may report an erroneous spike in network traffic usage.
• Z4(C) appliances fail to forward ARP messages that have a VLAN tag, even if the VLAN tagging correctly matches with the Z4(C)'s port configuration.
• Due to issues under investigation, MX75 and MX85 appliances may encounter unexpected device reboots.
• Z4(C) appliances fail to properly forward STP frames received on its LAN interfaces.

[rhbirkelund]

Does anyone have more details on what this bugfix is about?

[Mloraditch]

I don't have info on the specifics, but I see that 19.1.7 also now has a note about this bug existing in that code as well and thought it'd be worthy to mention.

[TyShawn]

I noticed the loss of POE on Z4 device was not added to the prior known bug list and is not addressed in this changelog. 

[Rhyskil]

I originally had the issue that this fixed back in December, but was told by support it was a fault with my connections (despite being two different carriers on two different networks happening at the same time).

Was semi-relieved to see I was only being gaslit, in that there was a firmware patch addressing this exact issue.

Upgraded, ran fine for two weeks, but having the uplinks briefly spike in latency / high loss for the last week again, 3 times just this morning. 

Issue's not fixed.