Meraki Firmware Release Process
Firmware Overview
Learn more with these free online training courses on the Meraki Learning Hub:
Cisco Meraki firmware upgrades are designed to be reliable, predictable, and low-risk - whether deployed to a single network or thousands at once.
Before any firmware becomes available in Dashboard, it undergoes extensive internal testing, including regression, stability, performance, and security validation. Each product family (MX, MS, MR, MV, MG, MT) follows a unified firmware lifecycle to ensure consistency and operational safety across deployments.
Firmware Release Stages
Cisco Meraki firmware progresses through three release stages, each representing a different balance between early access and long-term stability.
Beta
Beta firmware provides early access to new features and fixes.
• Intended for labs, pilots, and controlled production validation
• Has already passed internal regression, stability, and performance testing
• Requires explicit opt-in per network
• May receive frequent updates as changes are refined
• Fully supported for the latest beta version
Customers who opt in to beta firmware will automatically receive new beta updates for that product family. These upgrades can be scheduled, rescheduled, canceled, or rolled back using the Firmware upgrades tool in Dashboard.
The latest beta firmware is fully supported by our Support and Engineering teams. Older betas are supported with best effort; an upgrade to the latest beta will ensure full support.
Generally Available
Generally Available firmware is production-ready and fully supported.
- Passed all quality, telemetry, and validation checks
- Includes major, minor, patch, and hot-fix releases
- Suitable for all production environments
- Available for manual upgrades and scheduled deployments
GA firmware represents the latest production functionality and is appropriate when you want to adopt new features soon after release.
The latest Generally Available firmware is fully supported by our Support and Engineering teams. Older versions are supported with best effort; an upgrade to the latest beta, generally available, or recommended release will ensure full support.
Recommended Release
Recommended Release represents the most proven firmware version for each product family.
Selected based on:
- Broad customer adoption
- Stability and performance metrics
- Support case trends
- Designed for enterprise and mission-critical environments
Default firmware for:
- Newly created networks
- Scheduled upgrade campaign by Cisco Meraki
If you are unsure which firmware version to run, Recommended Release is the safest choice.
The latest Recommended Release is fully supported by our Support and Engineering teams. Older Recommended Releases are supported with best effort; an upgrade to the latest Recommended Release will ensure full support.
How Firmware Becomes Recommended
Firmware does not become a Recommended Release immediately.
After a GA version is released, Meraki continuously monitors real-world performance across the install base. Engineering, Support, and Product teams jointly review adoption levels, quality signals, and operational outcomes before designating a version as Recommended.
Each product family typically receives a new Recommended Release approximately every six months.
Upgrade Scheduling and Notifications
When Meraki schedules a firmware upgrade:
• Organization administrators and configured alert recipients receive email notification 7–14 days in advance
• Upgrades are scheduled within the network’s configured maintenance window
• Administrators may view, reschedule, or cancel upgrades at any time prior to execution
If no action is taken, the upgrade proceeds as scheduled.
Critical updates, such as those to address high-impact security vulnerabilities, may be scheduled on a shorter timeline.
Device Upgrade Process
Devices continue normal operation while downloading firmware. Client connectivity is briefly interrupted only during the reboot phase.
Meraki devices maintain two firmware partitions:
- The currently running version
- The new version being installed
If a device fails to reconnect to the cloud or Internet after reboot, it automatically reverts to the previous firmware.
Typical upgrade durations:
- Firmware download: up to ~10 minutes
- Reboot and recovery: ~1 minute
- Dashboard data may take a few additional minutes to refresh
For networks with larger numbers of devices sharing an Internet connection, this process can take longer, as all devices must download the new firmware.
Firmware Upgrade Tools
Firmware upgrades are managed through the Dashboard firmware upgrades tool, which allows administrators to:
- View available firmware versions and release stages
- Schedule, reschedule, or cancel upgrades
- Review firmware change logs
- Roll back recent upgrades when needed
- Additional upgrade status details can also be viewed on the device’s local status page.
More information about this tool can be found in the Managing Firmware Upgrades document.
Deprecated Firmware
To maintain compatibility, security, and cloud reliability, networks running firmware older than supported versions may be scheduled for upgrade.
- Administrators receive advance notification
- Upgrades can be rescheduled using the firmware upgrades tool (see Rescheduling or Canceling a Firmware Upgrade).
- Critical security updates may be scheduled on accelerated timelines
New Product Firmware Compatibility
New Meraki products are released with a supported firmware version appropriate for that device.
If a newly added product requires a newer firmware version than the rest of the network:
- Dashboard automatically applies the correct firmware to that device
- The product operates safely alongside other devices in the network
- The network firmware will converge as future upgrades occur