Cisco Meraki MR84 End-of-Life: Migration Guide to the MR86

The Cisco Meraki MR84 (PID MR84-HW) was the rugged, high-density member of Meraki's outdoor wireless line: a 4x4:4 802.11ac Wave 2 access point with an IP67-rated enclosure, external N-type antenna connectors, and cloud management through the Meraki dashboard. It earned a place on stadium catwalks, campus quads, logistics yards, ports, and waterfront sites where coverage had to survive heat, cold, dust, and driven rain. That deployment longevity is now the problem: the MR84 went End of Sale on May 7, 2021, and reaches its Last Day of Support (LDoS) on July 21, 2026. After that date the hardware does not stop transmitting, but Cisco's obligations to keep it safe and serviceable do. This guide explains exactly what the milestones mean for the MR84, why the Wi-Fi 6 MR86 is the engineered successor rather than a generic swap, and how to run the refresh without a coverage gap or a compliance finding.

Why July 21, 2026 is a hard deadline, not a suggestion

Cisco's lifecycle milestones are a deliberate wind-down, and the MR84 is now in its final stretch. Understanding what each date removes is the difference between planning a refresh and discovering you needed one.

• End of Sale (already passed, May 7, 2021): the MR84-HW can no longer be ordered new through Cisco. Any 'new' unit on the secondary market is either old stock or used, and neither carries a fresh warranty or a transferable support entitlement.
• End of Software Maintenance (not separately published for this SKU): in the Meraki model, firmware is delivered from the cloud, so feature and bug-fix firmware for the MR84 effectively tails off as the platform approaches LDoS. The dashboard will continue to manage the AP, but you should not expect new capabilities or non-critical fixes.
• Last Day of Support, July 21, 2026: the decisive date. This is the last day Cisco provides any support for the MR84-HW. After it, there are no PSIRT security fixes, no TAC cases, and no RMA hardware replacements for failed units.

The security consequence is the one that turns an operational nuisance into an audit problem. After LDoS, if a vulnerability is found in the MR84's firmware or in a protocol it implements, there will be no patch. An access point sits at the literal edge of the network, often physically reachable, terminating client traffic and bridging it onto your wired VLANs. An unpatchable edge device is exactly the kind of finding that surfaces in a CMMC, FedRAMP, HIPAA Security Rule, or PCI-DSS assessment, where 'vendor no longer provides security updates' maps directly to control gaps around flaw remediation and supported software. Running MR84s past July 2026 is a documented, dated risk acceptance, not a quiet deferral.

The recommended replacement: Meraki MR86 Wi-Fi 6 Outdoor AP

Cisco maps the MR84 to the Meraki MR86 (PID MR86-HW), and it is a true successor for this product type, not a lateral move. The MR86 keeps everything that made the MR84 deployable outdoors, the same managed-by-dashboard model, an IP67-sealed enclosure rated for extreme temperature and weather, and external antenna connectors for shaping long-range or sectorized coverage, while moving the radio and the uplink forward a full generation.

What actually improves, and why it matters outdoors

• Wi-Fi standard: 802.11ax (Wi-Fi 6) replaces the MR84's 802.11ac Wave 2. The headline gain is not raw single-client speed but efficiency under load, which is precisely the MR84's job profile.
• OFDMA and improved MU-MIMO: Wi-Fi 6 subdivides each channel so the AP can service many small frames from many clients in a single transmission. In a packed stadium concourse or a logistics yard full of handheld scanners, OFDMA cuts airtime contention and raises usable aggregate throughput far more than a spec-sheet PHY rate would suggest.
• Multigigabit uplink: the MR86 carries a 2.5GbE (mGig) Ethernet port versus the MR84's 1GbE. Wi-Fi 6 radios can realistically push past a gigabit aggregate, so a 1GbE uplink becomes the bottleneck. The 2.5GbE port removes the wired-side choke without a fiber run, and it works with existing Cat5e/Cat6 cabling.
• Client density and battery: target wake time (TWT), a Wi-Fi 6 feature, lets battery clients schedule radio sleep, which matters for outdoor IoT, asset tags, and barcode guns. BSS coloring reduces co-channel interference in dense AP layouts, a common outdoor problem when you blanket a large area.
• Operational continuity: both APs live in the same Meraki dashboard, so there is no controller to stand up and no management-plane migration. SSIDs, group policies, RF profiles, and firewall/traffic-shaping rules are organization- and network-level constructs that the MR86 inherits.

One planning note specific to outdoor: confirm antenna continuity. Both APs use external antennas, but validate that your existing MR84 antennas and their gain/pattern are supported and appropriate on the MR86, or budget for new ones. The mounting hardware and the move to 2.5GbE PoE are the two physical items most likely to need attention. You can review current MR86 configurations and stock on our catalog and confirm the exact PID and antenna options before you commit a design.

A practical MR84-to-MR86 migration plan

Because Meraki keeps the management plane in the cloud, this refresh is mostly a hardware and licensing exercise rather than a configuration rebuild. That is an advantage only if you sequence it correctly.

1. Inventory and assessment

Pull the full list of MR84-HW units from the dashboard, including serials, firmware, mount locations, and the switch port and PoE budget each one draws. Note which APs use external antennas and which are on critical coverage. The dashboard's location and topology views give you the authoritative map; export it. This inventory is also your decommission checklist later. Our EoL hub tracks the MR84 milestone alongside the rest of your fleet so you can batch refreshes by date instead of reacting one device at a time.

2. Licensing transition

Meraki is subscription-licensed per device. Each MR86 needs its own wireless license (per-device or co-termination, matching your existing model) for the term you choose. The MR84's license does not transfer to the MR86, so plan the new licenses to align with your existing co-termination date to avoid orphaned renewal cliffs. If you are on per-device licensing, sequence license claims with the hardware so APs do not go unlicensed mid-cutover. Get the license term and tier into the quote from the start, because the subscription is a real multi-year line item, not an afterthought.

3. Physical, power, and uplink readiness

• PoE: the MR86 is designed for 802.3at (PoE+). Verify each upstream switch port and any midspan injector can deliver PoE+ at the full feature set; some MR84s ran on plain 802.3af with reduced function, and that will not be adequate.
• Uplink: to realize the MR86's throughput, the upstream switch port should be mGig-capable (2.5GbE). A 1GbE port works but caps the AP. If you are also refreshing access switches, this is the moment to land mGig.
• Mounting and cabling: reuse mounts and weatherproof cable glands where mechanically compatible; inspect outdoor cabling and gaskets while you have a lift or tower crew on site.
• Antennas: re-terminate or replace external antennas per your validated design.

4. Phased cutover with feature parity

Add the MR86s to the same network in the dashboard so they inherit SSIDs, RF profiles, and policies automatically. Stage and burn-in indoors if possible, then do a like-for-like physical swap zone by zone. Because both generations coexist in one network, you can run mixed during transition and validate coverage, roaming, and client experience on the MR86 before pulling the matching MR84. Walk-test or use the dashboard's RF and client-health data to confirm parity before decommissioning each old radio.

5. Secure decommission

Remove each retired MR84 from the dashboard so it stops counting against licensing and can no longer rejoin. For federal, DoD, and healthcare environments, follow your media-sanitization and asset-disposition process for the removed hardware and document chain of custody. Reconcile the dashboard inventory against your physical removal log so no MR84 quietly stays on the network past LDoS.

Procurement notes for regulated buyers

For US federal, DoD, and SLED purchases, the MR86 should be sourced to meet Trade Agreements Act (TAA) compliance and, where applicable, fit GSA and government purchase card (GPC) thresholds. As an authorized Cisco partner, uniqcli supplies new, warrantied MR86-HW with valid, transferable Meraki licensing, which is the entitlement chain an auditor and a Cisco TAC case both depend on, and the one you cannot reconstruct from secondary-market gear. Plan for lead time: wireless refreshes that include mGig switching, antennas, and licensing have a longer procurement tail than a bare AP, so start the order well ahead of the July 21, 2026 LDoS. Buying through an authorized partner also keeps your support contract, license co-termination, and refresh roadmap aligned in one place.

The MR84 served outdoor and high-density coverage well, but July 21, 2026 ends Cisco's support for it, and an unpatchable, unserviceable edge radio is a liability rather than an asset. The MR86 keeps the rugged, dashboard-managed, external-antenna model you already operate while adding Wi-Fi 6 efficiency and a 2.5GbE uplink that the next decade of outdoor clients will actually use. Confirm your specific MR84 list on our EoL hub and request your migration quote at /get-a-quote.