New MX 16.16.9 stable patch - fixes DHCP issue in HA mode

[cmr]

Security appliance firmware versions MX 16.16.9 changelog

Important notice

• While Meraki appliances have traditionally relied on UDP port 7351 for cloud communication and TCP ports 80 and 443 for backup communications, with MX 16 we are beginning a transition to using TCP port 443 as the primary means for cloud connectivity. In order to ensure proper connectivity to the Meraki cloud after this upgrade, please ensure that all “Meraki cloud communication” traffic specified in the Help > Firewall Info page is allowed through any firewalls or security filtering devices that may be deployed upstream of your Meraki appliances. These requirements have been updated on Nov 2022, so it’s important that you review them.
• HTTP proxy, which allows default management traffic from MX appliances to be sent through a proxy, is deprecated on MX 16 and higher firmware versions.

Bug fixes

• Fixed a rare issue that could result in disruptions to DHCP in High Availability configurations.

Legacy products notice

• When configured for this version, Z1 and MX80 appliances will run MX 14.56.

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 MX 15 regressions, USB cellular connectivity may be less reliable on some modems
• Due to an MX 15 regression, the management port on MX84 appliances does not provide access to the local status page
• Client traffic will be dropped by MX65(W), MX67(C,W), and MX68(W,CW) appliances if 1) The client is connected to a LAN port with 802.1X authentication enabled and 2) The VLAN ID of the port is configured to 16, 32, 48, 64, 80, 96, 112, 128, 144, 160, 176, 192, 208, 224, or 240.

[ssbg]

Noticing this patch still shows a "Warning - February 28, 2023" notice on the firmware page. Any plans to push this date out? What are the practical implications of still being on this release past this date? We are not keen on moving to MX 17.x code until the content filtering performance issues are worked out...

[cmr]

@ssbg you'll be fine, support would just advise a newer version if you hit an issue.

[walkman]

Is 16.16.9 already outdated? Its status is showing as critical as of the 28th of February, even though it's still listed as latest stable on the overview page. Haven't updated to 17 yet since lots of people have been having issues. 17.10.4  might be good now but I'll still like to wait a bit.

Edit: Just read the two replies above. Still seems weird to mark it as critical, at most a warning seems more appropriate.