Skip to main content

 

Cisco Meraki Documentation

MR Firmware Release Notes

  1. Last updated
  2. Save as PDF

Firmware Release Stages and Recommendations 

To make firmware upgrade decisions simpler and more predictable, Cisco Meraki groups firmware versions into three release stages. Each stage reflects a different balance between access to new features and long-term stability.

clipboard_eaa819be0f89f07031f35ab59d09105f0.png

Beta 

Beta firmware is intended for testing and early validation.

  • Requires explicit opt-in by network
  • May receive frequent updates as changes are validated
  • Fully supported, but not recommended for production environments
  • Used for labs, pilots, and evaluating new features or fixes
Generally Available (GA) 

Generally Available firmware is production-ready and fully supported.

  • Passed all quality assurance and telemetry checks
  • Includes new releases, maintenance updates, and hot-fixes
  • Suitable for all production networks
  • Eligible for manual and scheduled upgrades
  • Choose GA if you want access to the latest production features.
Recommended Release 

Recommended Release is the most proven firmware version for each product family.

  • Selected based on broad customer adoption, quality metrics, and support experience
  • Designed for enterprise and mission-critical environments
  • Default for newly created networks
  • Default selection for scheduled upgrade
  • If you are unsure which firmware version to run, Recommended Release is the safest choice.
Choosing the Right Version: Quick decision guide 

  • Maximum stability and lowest operational risk → Recommended Release

  • Need the latest production features &/or bug fix? → Generally Available

  • Testing or validating fixes? → Beta

You can upgrade or change firmware versions at any time using the Firmware upgrades tool in Dashboard or by using API automation. 

Bug Fixes vs. Known Issues

  • Bug Fixes: Check if the release resolves specific "pain points" you are currently experiencing (e.g., roaming issues, specific client disconnects, or Radio stability issues).

  • Known Issues: Always cross-reference the "Known Issues" list with your critical infrastructure needs. If a known issue affects a legacy device type prevalent in your office, wait for the next iteration.

New Features

By regularly monitoring the firmware upgrade tool, reviewing release notes, and optionally enabling beta firmware, you can stay informed about and access new features as they become available in Meraki firmware releases.

_____________________________________________________

MR Access Point Release notes 


MR 30.1 changelog 

Important note 

  • While Meraki APs have traditionally relied on UDP port 7351 for cloud communication, and TCP ports 80 and 443 for backup communications, with MR 28+ we are beginning the 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 devices that are deployed upstream of your Meraki APs. These requirements have been updated in November of 2022, so it is important that you review them. (Wi-Fi 6 and Wi-Fi 6E APs) 

Legacy product notice 

  • When configured for this version, MR12, MR16, MR18, MR24, MR26, MR32, MR34, MR62, MR66, and MR72 will run MR 26.8.3 

New feature 

MR 30.2 changelog 

Important note 

  • While Meraki APs have traditionally relied on UDP port 7351 for cloud communication, and TCP ports 80 and 443 for backup communications, with MR 28+ we are beginning the 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 devices that are deployed upstream of your Meraki APs. These requirements have been updated in November of 2022, so it is important that you review them. (Wi-Fi 6 and Wi-Fi 6E APs) 

Legacy product notice 

  • When configured for this version, MR12, MR16, MR18, MR24, MR26, MR32, MR34, MR62, MR66, and MR72 will run MR 26.8.3 

Bug fixes 

  • General stability and performance improvements 

  • Various improvements in DFS behavior for outdoor APs 

Known issues 

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs) 

  • In high capacity wireless networks APs may experience instability when the “Client Balancing” or "Band Steering" feature are enabled 

  • DNS test failure results in no connectivity (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

  • AKM suite missing w/ OWE (Wi-Fi 5 Wave 2) 

MR 30.3 changelog 

Important note 

  • While Meraki APs have traditionally relied on UDP port 7351 for cloud communication, and TCP ports 80 and 443 for backup communications, with MR 28+ we are beginning the 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 devices that are deployed upstream of your Meraki APs. These requirements have been updated in November of 2022, so it is important that you review them. (Wi-Fi 6 and Wi-Fi 6E APs) 

Legacy product notice 

  • When configured for this version, MR12, MR16, MR18, MR24, MR26, MR32, MR34, MR62, MR66, and MR72 will run MR 26.8.3 

Bug fixes 

  • General stability and performance improvements 

  • APs reporting other in-network APs as spoofs 

Known issues 

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs) 

  • In high capacity wireless networks APs may experience instability when the “Client Balancing” or "Band Steering" feature are enabled 

  • DNS test failure results in no connectivity (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

MR 30.4 changelog 

Important note 

  • While Meraki APs have traditionally relied on UDP port 7351 for cloud communication, and TCP ports 80 and 443 for backup communications, with MR 28+ we are beginning the 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 devices that are deployed upstream of your Meraki APs. These requirements have been updated in November of 2022, so it is important that you review them. (Wi-Fi 6 and Wi-Fi 6E APs) 

Legacy product notice 

When configured for this version, MR12, MR16, MR18, MR24, MR26, MR32, MR34, MR62, MR66, and MR72 will run MR 26.8.3 

Bug fixes 

  • General stability and performance improvements 

  • LAN packet capture fix (MR57, MR52) 

  • APs stop forwarding RTP traffic (MR45) 

Known issues 

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs) 

  • In high capacity wireless networks APs may experience instability when the “Client Balancing” or "Band Steering" feature are enabled 

MR 30.5 changelog 

Important note 

  • While Meraki APs have traditionally relied on UDP port 7351 for cloud communication, and TCP ports 80 and 443 for backup communications, with MR 28+ we are beginning the 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 devices that are deployed upstream of your Meraki APs. These requirements have been updated in November of 2022, so it is important that you review them. (Wi-Fi 6 and Wi-Fi 6E APs) 

Legacy product notice 

  • When configured for this version, MR12, MR16, MR18, MR24, MR26, MR32, MR34, MR62, MR66, and MR72 will run MR 26.8.3 

Bug fixes 

  • General stability and performance improvements 

  • When using VLAN profiles, APs may have failed to associate clients (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

  • WPA3 OWE AKM suite information was not included in AP beacons (Wi-Fi 5 Wave 2 APs) 

  • When using L2 isolation, Windows clients may have experienced connectivity issues (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

  • When using WPN, DHCP requests did not include option 55 (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

  • In high capacity wireless networks, APs may have experienced instability when the “Band Steering” feature was enabled (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

Known issues 

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs) 

  • In high capacity wireless networks, APs may experience instability when the “Client Balancing” feature is enabled (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

  • APs ignore AutoChannel and manual channel changes despite reporting they changed their channel (Wi-Fi 6E APs) 

  • DNS test failure results in no connectivity (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

  • Instability when using iPSK w/ RADIUS (MR36H) 

  • AMI not sending RADIUS traffic 

  • The FastCGI process is unresponsive, which causes issues with affected APs downloading their configuration and returning live stats like current clients, utilization, etc. (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

MR 30.5.1 changelog 

Important note 

  • While Meraki APs have traditionally relied on UDP port 7351 for cloud communication, and TCP ports 80 and 443 for backup communications, with MR 28+ we are beginning the 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 devices that are deployed upstream of your Meraki APs. These requirements have been updated in November of 2022, so it is important that you review them. (Wi-Fi 6 and Wi-Fi 6E APs) 

Legacy product notice 

  • When configured for this version, MR12, MR16, MR18, MR24, MR26, MR32, MR34, MR62, MR66, and MR72 will run MR 26.8.3 

Bug fixes 

  • General stability and performance improvements =

Known issues 

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs) 

  • In high capacity wireless networks, APs may experience instability when the “Client Balancing” feature is enabled (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

  • DNS test failure results in no connectivity (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

  • Instability when using iPSK w/ RADIUS (MR36H) 

  • AMI not sending RADIUS traffic 

MR 30.6 changelog 

Important note 

Legacy product notice 

  • When configured for this version, MR12, MR16, MR18, MR24, MR26, MR32, MR34, MR62, MR66, and MR72 will run MR 26.8.3 

Bug fixes 

  • General stability and performance improvements 

  • AP not returning to original channel after a DFS channel change event occurred (MR45/55) 

  • Large mDNS packets can cause loss of wired connectivity (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

  • User-Name and Calling-Station-Id in different format consuming additional license on ISE (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

  • UDN ID not properly assigned to clients for "iPSK w/ RADIUS" configuration (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

  • Incorrect IPSK-EAPOL VSA data for Easy PSK (Wi-Fi 5 Wave 2 APs) 

  • Exclude Beidu/GLONASS constellations from GNSS receiver when used for AFC location (Wi-Fi 6E APs) 

  • 6 GHz radio not turned off when AFC expires (CW9163E-MR) 

  • APs utilizing WPA3 are shown as "Open" in RF Spectrum > Interfering APs UI (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

  • Clients getting dropped before DHCP lease time expiry during L3 roam and disconnected for more than 30 sec (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

  • AP failed to change channel (Wi-Fi 6 and Wi-Fi 6E APs) 

Enhancement 

  • Add 6 GHz support for regulatory domains with new 6 GHz approvals (Wi-Fi 6E APs) 

  • Keep 6 GHz radio off for outdoor APs when no configuration provided (CW9163E-MR) 

  • Upgrade CiscoSSL from 7.3 to 7.3a 

Known issues 

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs) 

  • In high capacity wireless networks, APs may experience instability when the “Client Balancing” feature is enabled (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

  • DNS test failure results in no connectivity (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

  • AMI not sending RADIUS traffic 

  • The FastCGI process is unresponsive, which causes issues with affected APs downloading their configuration and returning live stats like current clients, utilization, etc. (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

MR 30.7 changelog 

Important note 

Legacy product notice 

  • When configured for this version, MR12, MR16, MR18, MR24, MR26, MR32, MR34, MR62, MR66, and MR72 will run MR 26.8.3 

New feature 

  • Adding 5 & 6 GHz radio support for additional countries 

Bug fixes 

  • General stability and performance improvements 

  • AP sends RADIUS traffic out of the primary management interface when the alternate management interface is enabled 

  • AutoRF channel auto-updates not occurring on MR20 APs 

  • Failure of DNS test results in no connectivity 

  • MR36 APs fail to auto-negotiate link with 100Mbps cable 

  • L3 Roaming tagging client traffic with non-existent VLAN ID 

  • Apple devices can’t connect to APs using SSIDs set for WPA3 and 802.11r (Wi-Fi 5 Wave 2) 

  • Reduced throughput on Wi-Fi 6 APs 

  • APs experience poor performance after extensive uptime (Wi-Fi 6 APs) 

  • In high-capacity wireless networks, APs may experience instability when the “Client Balancing” feature is enabled (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

  • Suspected false positive DFS alerts 

  • APs fail to receive RadSec certificates 

  • APs not broadcasting beacon frames for Site Survey SSID on 6GHz 

  • The FastCGI process is unresponsive, which causes issues with affected APs downloading their configuration and returning live stats like current clients, utilization, etc. (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) 

Security fixes 

  • Upgraded lighttpd to v1.4.67 (CVE-2022-41556) 

Known issues 

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs) 

  • Client balancing rejects clients when the 10th SSID is enabled 

MR 30.7.1 changelog 

Important note 

Legacy product notice 

  • When configured for this version, MR12, MR16, MR18, MR24, MR26, MR32, MR34, MR62, MR66, and MR72 will run MR 26.8.3 

Bug fixes 

  • General stability and performance improvements 

  • Client balancing rejects clients when the 9th or 10th SSID is enabled 

  • AP instability when RADSec is enabled (Wi-Fi 5 Wave 2 APs) 

  • VLAN override fails on SSIDs configured to use VLAN ID tagging 

Known issues 

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs) 

MR 31.1.1 changelog 

Important note 

New feature 

  • Additional RF Temetries and NDP support for AI-RRM 

  • Adding 6 GHz Radio support for 20 Countries 

Bug fixes 

  • General stability and performance improvements 

  • In high-capacity wireless networks, APs may experience instability when the “Client Balancing” feature is enabled (Wi-Fi 6 and Wi-Fi 6E APs) 

Known issues 

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 6 APs) 

  • Clients may experience intermittent re-auth issues on MR45/55 APs 

  • AFC not available on CW9163E APs 

  • Roaming-related issues with 802.11r configured SSID on MR45/55 APs 

MR 31.1.2 changelog 

Important note 

Bug fixes 

  • General stability and performance improvements 

  • HTTPS redirection does not work for LSP on wired interface 

  • Channels missing for rogue detection 

Known issues 

  • Roaming-related issues with 802.11r configured SSID on MR45/55 APs 

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 6 APs) 

MR 31.1.3 changelog 

Important note 

New feature 

  • Intelligent Capture for Wireless Proactive packet capture support 

Bug fixes 

  • General stability and performance improvements 

  • Client balancing rejects clients when 9 SSIDs are created 

Security fixes 

  • libxml2 upgraded to 2.11.7 (CVE-2024-25062) 

Known issues 

  • Roaming-related issues with 802.11r configured SSID on MR45/55 APs 

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 6 APs) 

MR 31.1.4 changelog 

Important note 

Bug fixes 

  • General stability and performance improvements 

  • Roaming-related issues with 802.11r configured SSID (Wi-Fi 6 APs) 

Known issues 

  • APs may experience OOM with NBAR enabled (Wi-Fi 6 APs) 

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 6 APs) 

MR 31.1.5.1 changelog 

Important note 

Bug fixes 

  • General stability and performance improvements 

  • Potential crash loops for 6GHz in non-US regulatory domains (Wi-Fi 6E APs) 

  • CW916X APs are requesting 40W PoE power when USB is disabled 

Known issues 

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 6, Wi-Fi 6E APs) 

MR 31.1.6 changelog 

Important note 

  • Wi-Fi 5 Wave 2 MRs support - This version and subsequent MR 31.x.x are only supported on 802.11ax (Wi-Fi 6) and newer MR models. 802.11ac Wave 2 and older products will only upgrade to the backup version (MR 30.7.1) if they are in networks configured for MR 31.x.x versions, and thus, the new features will not be available. The bug fixes listed below will also not apply to Wi-Fi 5 Wave 2 and older MRs. (https://documentation.meraki.com/MR/Other_Topics/Cisco_Meraki_MR_Firmware_Restrictions_Overview_and_FAQ) 

Bug fixes 

  • General stability and performance improvements 

  • MR56 ethernet port flaps occur when connected to C9300-48UN(V04) at 5Gbps speeds 

  • MR57 ethernet port flaps occur when connected to MS355 at 5Gbps speeds 

  • MR46 not responding to Probe Requests from clients 

  • Channel & power not configurable via LSP on CW9163E APs 

  • Wildcard NAS-IPv6-Address AVP sent on config change (Wi-Fi 6, Wi-Fi 6E APs) 

  • NAS-IP-Address discarded (Wi-Fi 6, Wi-Fi 6E APs) 

  • RADSec authentication failures (Wi-Fi 6, Wi-Fi 6E APs) 

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 6, Wi-Fi 6E APs) 

  • DHCP offer is not forwarded if broadcast flag is set (Wi-Fi 7 APs) 

  • mDNS traffic blocked (Wi-Fi 7 APs) 

  • SSIDs broadcast on 6Ghz despite being disabled when using WPA3 transition mode (Wi-Fi 7 APs) 

MR 31.1.7 changelog 

Important note 

  • Wi-Fi 5 Wave 2 MRs support - This version and subsequent MR 31.x.x are only supported on 802.11ax (Wi-Fi 6) and newer MR models. 802.11ac Wave 2 and older products will upgrade to the backup version (MR 30.7.1) if they are in networks configured for MR 31.x.x versions, and thus, the new features will not be available. The bug fixes listed below will also not apply to Wi-Fi 5 Wave 2 and older MRs. (https://documentation.meraki.com/MR/Other_Topics/Cisco_Meraki_MR_Firmware_Restrictions_Overview_and_FAQ) 

Bug fixes 

  • General stability and performance improvements 

  • False positive DFS alerts in Japan on MR56 APs 

  • APs stop transmitting on wired interfaces due to exception (Wi-Fi 6 APs) 

  • Clients disconnect with error code 17 (Wi-Fi 6, Wi-Fi 6E, Wi-Fi 7 APs) 

  • Clients disconnect with reason code 0 (reserved) (Wi-Fi 6, Wi-Fi 6E, Wi-Fi 7 APs) 

  • Association ID mismatch (Wi-Fi 6, Wi-Fi 6E, Wi-Fi 7 APs) 

  • 2.4GHz 802.11n clients unable to connect (Wi-Fi 7 APs) 

Known issues 

  • 6GHz/160MHz mesh not forming on MR57, CW9166I, CW9166D1, CW9164I APs 

MR 31.1.7.1 changelog 

Important note 

  • Wi-Fi 5 Wave 2 MRs support - This version and subsequent MR 31.x.x are only supported on 802.11ax (Wi-Fi 6) and newer MR models. 802.11ac Wave 2 and older products will upgrade to the backup version (MR 30.7.1) if they are in networks configured for MR 31.x.x versions, and thus, the new features will not be available. The bug fixes listed below will also not apply to Wi-Fi 5 Wave 2 and older MRs. (https://documentation.meraki.com/MR/Other_Topics/Cisco_Meraki_MR_Firmware_Restrictions_Overview_and_FAQ) 

Bug fixes 

  • General stability, performance, and experience improvements 

  • BPDUs not forwarded to LAN ports when using VLAN tagged SSIDs (MR36H APs) 

  • MAB-based wired clients not re-authenticated after port reset (Wi-Fi 6, Wi-Fi 6E, Wi-Fi 7 APs) 

  • SGT source & destination tags swapped (Wi-Fi 6, Wi-Fi 6E, Wi-Fi 7 APs) 

Known issues 

  • 6GHz/160MHz mesh not forming on MR57, CW9166I, CW9166D1, CW9164I APs 

MR 31.1.8 changelog 

Important note 

  • Wi-Fi 5 Wave 2 MRs support - This version and subsequent MR 31.x.x are only supported on 802.11ax (Wi-Fi 6) and newer MR models. 802.11ac Wave 2 and older products will upgrade to the backup version (MR 30.7.1) if they are in networks configured for MR 31.x.x versions, and thus, the new features will not be available. The bug fixes listed below will also not apply to Wi-Fi 5 Wave 2 and older MRs. (https://documentation.meraki.com/MR/Other_Topics/Cisco_Meraki_MR_Firmware_Restrictions_Overview_and_FAQ) 

New feature 

Bug fixes 

  • General stability, performance, and experience improvements 

  • 6GHz/160MHz mesh not forming on MR57, CW9166I, CW9166D1, CW9164I APs 

  • APs do not send beacon frames on the 5GHz radio (Wi-Fi 7 APs) 

  • Increased CPU & memory utilization on MR57 APs 

MR 31.2.1 changelog 

Bug fixes 

  • General stability and performance improvements 

Known issues 

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 6, Wi-Fi 6E APs) 

MR 31.2.2 changelog 

Bug fixes 

  • General stability and performance improvements 

Known issues 

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 6, Wi-Fi 6E APs) 

MR 31.2.3 changelog 

Bug fixes 

  • General stability and performance improvements 

  • COA+11r Client session goes to terminated state after roam 

MR 31.2.4 changelog 

Bug fixes 

  • General stability and performance improvements 

  • Intra-AP roam between radios not triggering client delete to MCG 

  • AP not updating lease record and causing traffic blackhole when mandatory dhcp is enabled 

MR 31.2.5.1 changelog 

Bug fixes 

  • General stability, performance, and experience improvements 

MR 32.1.1 changelog 

New feature 

  • Support for AAA accounting + Fast roaming (802.11r) 

  • Support for Mandatory DHCP + Fast roaming (802.11r) 

  • Support for Client Exclusion Policies (Manual) 

  • Support COA Support + Fast roaming (802.11r) 

  • Enables Wi-Fi 7 APs with an embedded UWB radio to conduct sub-centimeter level ranging measurements to improve placement accuracy and flexibility in location-based services 

Enhancement 

  • 6GHz Support for Transition mode with SAE SSIDs 

  • MLO Support with 802.3at power for CW9178 

  • Safe Config Override for Site Surveying 

  • Support for AP name in beacon without CCX 

  • Dashboard support for Zebra devices to report Serial Number, Device Type/Model Number, OS, and Recent disconnect codes 

Important note 

  • MR45/55 APs are not supported on MR 32.x.x and will instead upgrade to the backup version (MR 31.1.7) if they are in networks configured for MR 32.x.x versions, and thus, new features will not be available. 

Bug fixes 

  • General stability, performance, and experience improvements 

  • MAB-based wired clients not re-authenticated after port reset (Wi-Fi 6, Wi-Fi 6E, Wi-Fi 7 APs) 

  • Gateway MR to source RADIUS traffic from AMI (Wi-Fi 6, Wi-Fi 6E, Wi-Fi 7 APs) 

Known issues 

  • 6GHz/160MHz mesh not forming on CW9166I APs 

MR 32.1.2 changelog 

New feature 

  • Support for DHCP Option 82 

Important note 

  • MR45/55 APs are not supported on MR 32.x.x and will instead upgrade to the backup version (MR 31.1.7.1) if they are in networks configured for MR 32.x.x versions, and thus, new features will not be available. 

Bug fixes 

  • General stability, performance, and experience improvements 

  • Dashboard channel utilization incorrectly reported above 100% (Wi-Fi 7 APs) 

Known issues 

  • 6GHz/160MHz mesh not forming on CW9166I APs 

MR 32.1.3 changelog

Important note 

  • MR45/55 APs are not supported on MR 32.x.x and will instead upgrade to the backup version (MR 31.1.7.1) if they are in networks configured for MR 32.x.x versions, and thus, new features will not be available. 

Bug fixes 

  • General stability, performance, and experience improvements 

  • APs do not send beacon frames on 5GHz radio (Wi-Fi 7 APs) 

  • MAC auth fails with RADIUS servers that do not supply Message-Authenticator in Access-Accept reply (Wi-Fi 6, 6e, 7 APs) 

MR 32.1.4 changelog 

Important note

  • MR45/55 APs are not supported on MR 32.x.x and will instead upgrade to the backup version (MR 31.1.8) if they are in networks configured for MR 32.x.x versions, and thus, new features will not be available. 

  • LSP speed test deprecated 

New feature 

  • The Per SSID toggle for 802.11be (Wi-Fi 7) feature allows WiFi 7 access points to operate some SSIDs in 802.11ax mode while others operate in 802.11be mode. This is also called "ax/be mixed mode", "per-SSID 11be." 

Bug fixes 

  • General stability, performance, and experience improvements 

  • APs intermittently stop sending beacons & responding to clients on 5GHz (Wi-Fi 6e) 

  • APs not responding to probe/auth requests from clients on 2.4 & 5GHz (Wi-Fi 6, 6e) 

  • Multi/Broadcast packets (RA/DHCP) not forwarded by APs (Wi-Fi 7) 

  • Mesh not forming 6GHz 160MHz (Wi-Fi 6e) 

MR 32.1.5 changelog 

Important note 

  • MR45/55 APs are not supported on MR 32.x.x and will instead upgrade to the backup version (MR 31.1.8) if they are in networks configured for MR 32.x.x versions, and thus, new features will not be available. 

Bug fixes 

  • General stability, performance, and experience improvements 

  • APs that require 802.3bt PoE for full capability request greater than 30W via CDP when connected to 802.3at (30W-capable) switch port (Wi-Fi 7) 

  • AP disassociates previously disassociated client with reason code 2 (Wi-Fi 6, 6e, Wi-Fi 7) 

MR 32.1.6 changelog 

Important note 

  • MR45/55 APs are not supported on MR 32.x.x and will instead upgrade to the backup version (MR 31.1.8) if they are in networks configured for MR 32.x.x versions, and thus, new features will not be available. 

Enhancement 

  • Enhancements to Ethernet link negotiation mechanisms have been implemented to detect temporal link degradation and attempt link recovery when a degraded state is identified. 

Bug fixes 

  • General stability, performance, and experience improvements 

  • APs not using configured SGT tag (Wi-Fi 6, 6e, Wi-Fi 7) 

  • RADSec authentication stuck (Wi-Fi 6, 6e, Wi-Fi 7) 

  • Wi-Fi calling not working (Wi-Fi 6, 6e, Wi-Fi 7) 

  • WebEx DeskPro connectivity issues (Wi-Fi 6, 6e, Wi-Fi 7) 

MR 32.2.1 changelog 

New feature 

  • Cisco Spaces Connect on Meraki – Enables APs to efficiently and securely transmit BLE data to the Spaces cloud. 

Enhancement 

Bug fixes 

  • General stability, performance, and experience improvements. 

MR 32.2.2 changelog 

Bug fixes 

  • General stability, performance, and experience improvements. 

  • APs don’t forward mDNS traffic out wireless interface when using named VLANs (Wi-Fi 7) 

MR 32.2.3 changelog 

Bug fixes 

  • General stability, performance, and experience improvements. 

  • Intermittent ACK frames ignored due to devices not honoring SIFS backoff (Wi-Fi 7) 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Reference
  2. Tags
    This page has no tags.