Skip to main content

 

Cisco Meraki Documentation

MR Firmware Release Status and Nomenclature

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.

Current MR firmware release matrix

Release stage Current release
Beta release MR 33.1.3
Generally Available release MR 32.2.4
Cisco Recommended release MR 32.2.4
  • Was this article helpful?