- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
New MX 19.2.1 beta firmware: announced and hopefully here soon
This will be updated as soon as it makes its way to a dashboard near you (or me)...
Solved! Go to solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Security appliance firmware versions MX 19.2.1 changelog
Important notice
- As of MX 19.1, Cisco Meraki will no longer support USB-based Cellular Failover on the MX and Z platforms.
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.
Executive summary
- The latest release enhances cryptographic capabilities by incorporating advanced Diffie-Hellman groups, DH15 and DH21, into IPSec and AutoVPN solutions.
- These enhancements align with industry best practices, providing robust security for encrypted communications.
What's new
- Added support for Diffie-Hellman Groups 15 (3072-bit ECDH) and 21 (521-bit ECDH encryption) in IPsec and AutoVPN configurations, ensuring interoperability with modern cryptographic standards and enhances security postures for sensitive communications.
- Modem firmware visibility on dashboard - Z4C.
Known issues status
- The list is no longer being updated with new information. Please see the latest available release for new, active updates. Many existing issue reports have not been confirmed to affect MX 19.2 firmware versions.
Known issues
- There is an increased risk of encountering device stability and performance issues on all platforms and across all configurations.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Security appliance firmware versions MX 19.2.1 changelog
Important notice
- As of MX 19.1, Cisco Meraki will no longer support USB-based Cellular Failover on the MX and Z platforms.
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.
Executive summary
- The latest release enhances cryptographic capabilities by incorporating advanced Diffie-Hellman groups, DH15 and DH21, into IPSec and AutoVPN solutions.
- These enhancements align with industry best practices, providing robust security for encrypted communications.
What's new
- Added support for Diffie-Hellman Groups 15 (3072-bit ECDH) and 21 (521-bit ECDH encryption) in IPsec and AutoVPN configurations, ensuring interoperability with modern cryptographic standards and enhances security postures for sensitive communications.
- Modem firmware visibility on dashboard - Z4C.
Known issues status
- The list is no longer being updated with new information. Please see the latest available release for new, active updates. Many existing issue reports have not been confirmed to affect MX 19.2 firmware versions.
Known issues
- There is an increased risk of encountering device stability and performance issues on all platforms and across all configurations.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oof I will skip that one for a bit. I have a big feeling that is it going to be buggy as hell ( even more than MX 19.1 which looks impossible , but never doubt ! )
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I’m testing MX 19.2.1 on one MX68W, MX75 and MX105…..so far it’s an improvement over MX 19.1.7.2 over the past 2+ hours.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Based on what criteria ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My initial observation is that it took less time when re-establishing NMVPN connectivity and 1/2 the time during the install process.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When will we get VRF or VRF lite feature? We are badly need this feature for our current setup
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Suresh_stp I took think this would be useful, but can't imagine it happening any time soon, it goes against the Meraki simple message.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
From the Demo I've seen, it'll most likely be related to Adaptive Policies.
Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution 🙂
All code examples are provided as is. Responsibility for Code execution lies solely your own.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi ,
Do we have an option to select the source Vlan ( interface IP ) for the Syslog server? Currently, it is using the highest-numbered Vlan, which we don't want.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Syslog Server Overview and Configuration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No you can't change it.
