Meraki MR18 End of Life: Migration Guide to the MR36 Wi-Fi 6 AP

If you still have Cisco Meraki MR18 access points (PID MR18-HW) bolted to the ceiling, they are now running on borrowed time. The MR18 hit End of Sale back on February 13, 2017, and its Last Day of Support (LDoS) passed on March 31, 2024. As of today these radios are fully out of the support lifecycle: no firmware, no security fixes, no TAC, and no RMA. This guide explains what each milestone actually means for an operator, why the gap is a compliance problem and not just an aesthetics problem, and how to move cleanly to the recommended successor — the Wi-Fi 6 Cisco Meraki MR36 (PID MR36-HW).

Why an out-of-support MR18 is a live risk, not a someday problem

The MR18 was a strong access point for its era: a dual-band 2x2:2 MIMO 802.11n radio set delivering up to roughly 600 Mbps aggregate, with the then-novel third dedicated radio for wireless intrusion detection and spectrum analysis, all at a tiny ~9.8 W power draw over 802.3af PoE. But 802.11n is two Wi-Fi generations behind current, and more importantly the platform no longer receives code.

Once a Meraki AP passes LDoS, Cisco stops shipping firmware to it. That means any newly discovered vulnerability in the wireless stack — a WPA2 key-reinstallation-class flaw, a management-plane bug, a TLS issue in the cloud tunnel — will never be patched on an MR18. There is no Cisco PSIRT remediation path and no engineering fix coming. For a regulated buyer this is the part auditors care about: you cannot demonstrate that a device is patched to a supported baseline when the vendor has formally ended support.

What each milestone date actually means

End of Sale — February 13, 2017

The date Cisco stopped selling the MR18 through normal channels. Anything you buy now is used, refurbished, or NOS gray-market stock — and a unit's existing Meraki license does not automatically transfer with a resold AP. End of Sale started the support clock.

End of Software Maintenance — n/a

Meraki's cloud-firmware model does not publish a separate software-maintenance milestone the way Cisco's on-box IOS products do; for the MR18 the practical software cutoff is LDoS. After that, the AP is frozen on whatever firmware it last received and is no longer carried forward in new firmware trains.

Last Day of Support — March 31, 2024

The hard line. After LDoS there is no TAC case support, no advance replacement / RMA, no firmware, and no security patches. A failed MR18 today cannot be replaced under warranty, and the Meraki dashboard will increasingly flag the model as unsupported. Every day past this date is operating without a safety net.

The recommended replacement: Meraki MR36 (MR36-HW)

The MR18's original successor was the MR32, but that model is itself now end-of-life, so current refreshes target the Cisco Meraki MR36 — the Wi-Fi 6 indoor AP that sits in the same role and price/power tier as the MR18 did. It is a near drop-in physically while being a generational leap in capability.

What you actually gain

• Wi-Fi 6 (802.11ax) instead of 802.11n. The MR36 is a 2x2:2 dual-band 802.11ax AP rated up to 1,201 Mbps on 5 GHz and up to ~287 Mbps on 2.4 GHz, for a ~1.7 Gbps aggregate — roughly triple the MR18's ~600 Mbps ceiling.
• OFDMA and MU-MIMO. The single biggest real-world win: OFDMA lets one transmission carry many small client frames at once, which is exactly what dense rooms full of phones, laptops, IoT and medical telemetry look like. The MR18's 802.11n had no equivalent, so it serialized clients and collapsed under density.
• WPA3 and Enhanced Open (OWE). The MR36 supports WPA3-Personal, WPA3-Enterprise, and OWE for open networks — modern crypto the MR18 firmware never received.
• Four radios. Dual client radios plus a dedicated WIDS/WIPS/RF-optimization radio (carried over and improved from the MR18 concept) plus an integrated Bluetooth Low Energy radio for beaconing and IoT scanning that the MR18 lacked.
• Target Wake Time (TWT) for battery-powered IoT, and better airtime efficiency overall — meaningful for healthcare carts, badge readers, and sensors.

A practical migration plan

1. Assessment and inventory

Pull the full MR18 list from the Meraki dashboard (or filter by model) and export serials, network assignments, and mounting locations. Note any AP doing something special — a dedicated scanning radio role, a high-density area, an outdoor-adjacent spot. Map current SSIDs, RF profiles, and group policies; these are network-level in Meraki and will carry to the MR36 automatically once the new AP joins the same network. Confirm switch ports are 802.3af-capable (they are if they powered an MR18) and that you have spare PoE budget for any added APs.

2. License transition

Meraki is subscription-licensed per AP. When you add MR36 units to a network you apply new Meraki licenses (co-termination or per-device, matching your org's licensing model) for the new serials. MR18 licenses do not migrate to the MR36 — budget for fresh MR36 licenses sized to the term you want, and time the cutover so you are not paying twice for long. An authorized partner can co-term the new licenses to your existing renewal date so everything lines up on one anniversary.

3. Config and feature parity

Because configuration lives in the cloud network, not on the box, the MR36 inherits SSIDs, RADIUS/identity settings, group policies, traffic shaping, and RF profiles the moment it claims into the same network. Use this as the moment to modernize: enable WPA3 (or WPA3 transition mode) where clients support it, turn on OFDMA-aware RF profiles, and review channel width — Wi-Fi 6 lets you use 5 GHz capacity the MR18 simply could not reach.

4. Physical, power, and uplinks

The MR36 uses the same low-profile indoor form factor and 802.3af PoE, so most existing mounts, drop cables, and switch ports are reusable. Verify each uplink negotiates at 1 Gbps (not 100M) so you do not bottleneck the new radios, and keep the existing Cat5e/Cat6 — no optics or stacking considerations apply to APs.

5. Phased cutover

Do not big-bang it. Stage MR36s in a pilot area, mount alongside or in place of MR18s, claim them into the network, and let them adopt config and self-optimize RF. Validate roaming, voice/telemetry, and authentication, then sweep building by building. Because both generations cohabit the same Meraki network, you can run a mixed estate during the transition without splitting management.

6. Secure decommission

Remove retired MR18s from the dashboard, release/return their licenses per your agreement, and physically wipe nothing-special (APs hold config in the cloud, not locally) but do account for chain of custody. For federal and DoD sites, dispose of hardware through your approved e-waste/asset-disposition process and keep the disposal record for audit.

Procurement notes for government and enterprise buyers

• TAA compliance: confirm country-of-origin and TAA status on the MR36 units and licenses for federal orders before you cut a PO.
• GPC / purchase-card friendly: small-quantity refreshes and license renewals can typically be transacted on a government purchase card through an authorized partner.
• Lead times: Wi-Fi 6 APs are mainstream stock, but bundle hardware with the right license term up front to avoid a gap where APs are online but unlicensed.
• Source from an authorized partner: buying MR36-HW and Meraki licensing through an authorized Cisco partner like uniqcli protects warranty, ensures genuine licensing, and keeps you clear of gray-market units that may not license or update.

For the full lifecycle record on this exact model, see the MR18-HW end-of-life detail page, or browse the broader Cisco EoL hub to check the rest of your fleet against published dates. You can compare and configure the replacement on our catalog as well.

The MR18 served its decade. With support fully ended, the cost of waiting is measured in unpatched exposure and audit findings — not just slower Wi-Fi. Plan the MR36 refresh now while it can be done on your schedule. Get a refresh quote.