Security appliances software versions MX 19.2.7 changelog   Important notice As of MX 19.1, Cisco Meraki will no longer support USB-based Cellular Failover on the MX and Z platforms. Starting with MX 19.1 firmware on vMX platforms, Meraki has begun to deprecate the use of 3DES encryption for Phase 2 (IPsec) of Client and IPsec VPN connections due to its insecure nature. Subsequent firmware releases will continue to deprecate it on all platforms. New feature highlights 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. Added support for Active-Active Non-Meraki VPN peer connections. Modem firmware visibility on dashboard - Z4C. Expanded the list of built-in APNs for Z3C, Z4C, MX67C, and MX68CW appliances. Executive summary This is the first Stable / Recommended release for MX 19.2. It contains new functionality that continues to expand the available choices for VPN connectivity and strengthens cellular serviceability. For customers already running MX 19.2, this maintenance release contains a range of fixes across AnyConnect VPN and Site-to-Site VPN. It also improves device stability and the consistency of network performance. Please read through the full details below. This release contains fixes and improvements for the C8455-G2-MX that launched at the end of 2025. Please read through the full details below. Additionally, MX 19.2 contains several important fixes for MX85 appliances that have been shown to significantly reduce cases of unexpected device reboots. We strongly encourage customers on versions prior to MX 19.2 to consider upgrading. With the promotion of MX 19.2 to Stable / Recommended release, we strongly encourage customers to begin their process of migrating from older releases. We do not intend for additional fixes to become available through future MX 19.1 releases. Bug fixes - general fixes Resolved several cases that could result in an unexpected device reboot. (MX-42084) (MX-42484) (MX-41540) (MX-43044) (MX-44148) (MX-44723) Resolved a rare issue that could result in AutoVPN traffic being dropped. (MX-43737) Fixed a rare issue that could result in AnyConnect Client VPN incorrectly rejecting valid authentication attempts. (MX-34380) Corrected a rare issue that could result in disruption to AnyConnect client VPN connectivity if Mobile Device Management (MDM) had ever been enabled in the organization. (MX-44403) Corrected an issue that could result in some devices connected via client VPN not being displayed in the Clients page on the Dashboard. (MX-21479) Corrected an issue with the VPN status reporting for IPsec VPN peers when a primary and secondary tunnel configuration was in place. (MX-41539) Fixed a rare issue that could result in a temporary network performance reduction in cases where a previous large burst of flow all expired at the same time. (MX-45842) Fixed a rare issue that could result in firewall rule configurations being unnecessarily reloaded. This may have introduced momentary reductions in network performance, especially when complex firewall rule sets were in use. (MX-45846) Fixed a very rare issue that could result in elevated device workload when processing HTTP traffic with out of order packets. (MX-44666) Resolved a regression that could result in traffic being incorrectly dropped when 1) a port forward, 1:1 NAT, or 1:M NAT was configured, 2) a static default route (0.0.0.0/0) was also configured, and 3) a LAN client was responding to a WAN-initiated connection. (MX-43847) Fixed an issue that could result in periods of incomplete data when viewing a 2-hour window of Dashboard latency graph data on the Appliance Status page. (MX-21351) Bug fixes - limited platform fixes Resolved an issue that could result in network routing problem when 1) C8455-G2-MX appliances were configured for warm spare (HA) and 2) an administrator swapped the primary and spare roles of the two appliances. (MX-44412) Fixed an issue that could result in IPsec VPN traffic failing on C8455-G2-MX appliances. (MX-45847) Corrected an issue that resulted in C8455-G2-MX appliances being unable to start the processes for performing ThousandEyes monitoring. (MX-45840) Resolved an issue that resulted in XDR flows not being exported correctly on C8455-G2-MX. (MX-45844) Resolved an issue that resulted in C8455-G2-MX appliances sending additional, unneeded ARP responses (MX-45841) Corrected an issue that could result in some SFP modules failing to be recognized on C8455-G2-MX appliances. (MX-45843) Corrected an issue that resulted in MX85 appliances erroneously dropping CDP and LLDP frames. (MX-44332) Legacy products notice When configured for this version, MX64(W), MX65(W), MX84, MX100, and vMX100 devices will run MX 18.107.13. Known issues status This list is being reviewed and updated. Other The product complies with EN 18031-1:2024 and EN 18031-2: 2024 Clarified the wording for the Cellular Override options in the Local Status Page. (MX-29835)   ... View more

Switch firmware versions MS 18.1.5.1 changelog Important notes This firmware release only includes updates for MS150 switches. All other MS switches on MS 18.1.5.1 will run firmware identical to MS 18.1.3.1. New feature highlights Group Policy ACL on MS130 & MS150 Maximum MAC support in MAC Allowlists 802.1x limited access mode with pre-auth GPACL Local Status Page connectivity diagnostics enhancements Layer 2 multicast live tool Traffic Mirroring: RSPAN & VLAN Based SPAN Fixed issues   Ms150 fixed issues Resolved an issue that resulted in some MS150 switches setting a port into a discarding state after a stack member reboot Fixed a bug that caused some clients to experience reduced upload speeds while connected to an MS150 switch that was connected to an MX68 gateway Fixed a bug that sometimes caused MS150 switches in stack configurations to experience unicast traffic floods Resolved an issue that sometimes caused MS150 switches in stack configurations to fail to learn the default gateway’s correct MAC address, which resulted in packet loss for clients on those VLANs Known issues   General known issues MS130 and MS150 switches may not properly display IPv6 RA packets in dashboard packet captures In rare circumstances switches may experience uplink instability when IPv6 link-local addresses are enabled. If this issue is encountered it can be resolved by enabling IPv6 RA Guard to block ICMPv6 neighbor discovery messages. MR access points may be incorrectly assigned to the Default profile instead of the preconfigured Access Point profile when initially connected to a switch port that uses Smartport Automation Some clients may fail to authenticate and resolve DHCP in voice VLANs Ms120 known issues Switches may fail to provide PoE power to legacy access points (always present) Cable tests may report incorrect cable lengths Ms130 known issues MS130X mGig ports may fail to establish a link when both sides are forced to 100 Mbps full-duplex. If either side of the connection uses auto-negotiation the link will be established normally Switches may incorrectly remove or update SGT tags when no policy or VLAN mapping is defined. Until a firmware fix is available, correct SGT tags can be preserved by defining a policy for the SGT group in Adaptive Policies, and binding the SGT group to a VLAN using VLAN profiles. Ms150 known issues When a stacking cable is disconnected from MS150 switches in stack configurations the disconnected port will incorrectly continue to be marked as connected while the still-connected stacking port will incorrectly be marked as disconnected MS150 switches may intermittently negotiate USB-C Ethernet adapters at 10 Mbps half-duplex instead of the expected speed for the switchport, requiring a physical reseat to correct the issue. In some circumstances MS150 switches in stack configurations may fail to blocking redundant links, resulting in looped packets Ms350x known issues Switches may experience an unexpected reboot (present since MS 15) Ms355 known issues Switches in stack configuration may experience some ports failing to reconnect after a firmware upgrade Ms410 known issues Some MS410 switches may encounter alerts for fan failures that will eventually self-resolve Ms425 known issues In rare circumstances MS425 switches may encounter a software crash that results in a reboot In rare circumstances MS425 switches in stack configurations may encounter a software crash that results in a reboot ... View more

Camera firmware versions MV 7.2 changelog Bug fixes Resolved an issue on MV84 series cameras where a short recording disruption could occur immediately after a firmware upgrade Resolved an issue where privacy windows might not appear on the video stream when using Standard video quality settings on MV84X General Improvements to video recording stability on MV84X Improvements to Image Quality for MV84X Notice When configured for this version, MV21 & MV71 cameras will run MV4.15 MV7.2 is the last supported firmware branch for MV12, MV2, MV22, MV32, MV52 and MV72 series. Future updates for these models will be limited to maintenance and security patches ... View more