Summary: Covers the Meraki firmware release cycle, upgrade tracks, how upgrades are scheduled and managed in the dashboard, what happens during an upgrade, and best practice recommendations.
Meraki firmware is released across three tracks. Each network is assigned to one track, and upgrades are offered from that track only.
| Track | Description |
|---|---|
| Stable | Fully tested general availability release. Recommended for production networks. |
| Release Candidate (RC) | Final validation before promotion to Stable. Suitable for networks that can tolerate minor risk in exchange for early access. |
| Beta | Early development builds with new features under active testing. Not recommended for production. |
Track assignment is configured per network in the dashboard under Network-wide > Firmware upgrades > Firmware track. Changing track does not trigger an immediate upgrade — it simply determines which future versions are offered.
Meraki promotes firmware from Beta → RC → Stable on its own schedule. There is no fixed cadence; promotions are driven by soak time and defect rates across the installed base. Stable releases receive an extended soak period at RC before promotion.
Meraki firmware versions follow the format <product> <major>.<minor>.<patch>, for example MX 18.107.2. The dashboard track selector is the authoritative indicator of stability — do not attempt to infer track from the version number alone.
Each product family (MX, MS, MR, MV, MT) is versioned independently. An upgrade to an MX network has no effect on MS or MR firmware in the same network.
Meraki manages firmware at the network level. Each network — whether a standalone site network or a template-bound network — has its own firmware upgrade settings. This means:
⚠️ Template Inheritance
Firmware track and upgrade schedule set on a network template apply to all networks bound to that template. Verify template settings before changing them — an unintended schedule change can trigger upgrades across many sites simultaneously.
Navigate to Network-wide > Firmware upgrades to manage firmware for a network.
When a new firmware version is available for the assigned track, the dashboard displays it with the option to upgrade now or schedule for later. The scheduling options are:
Scheduled upgrades are visible in the dashboard and can be cancelled before they execute.
A maintenance window defines a recurring time slot during which upgrades are permitted to run. Windows are configured per network under Network-wide > Firmware upgrades > Upgrade window.
Settings include:
If a firmware upgrade is available and a window is configured, the upgrade will execute during the next window that falls after the upgrade becomes available. If no window is configured, the upgrade runs at the scheduled time or immediately if set to upgrade now.
If a new firmware version is offered but you are not ready to upgrade, you can defer it. The dashboard allows deferral to a later date. Meraki will continue to offer the upgrade and may eventually enforce it — see below.
Individual networks can be held on their current firmware version using the firmware lock feature (Network-wide > Firmware upgrades > Lock firmware). While locked:
⚠️ Meraki Enforced Upgrades
Meraki reserves the right to push upgrades to networks running firmware below a minimum supported version, particularly for critical security vulnerabilities. A firmware lock does not provide an absolute guarantee against Meraki-initiated upgrades. Monitor Meraki's end-of-support communications for each firmware version your networks are running.
Understanding the upgrade sequence helps predict impact and plan communication.
For a standalone MX:
For an MX with a warm spare (HA pair):