If your Cisco Meraki device fails and the problem cannot be resolved by troubleshooting, contact Support to address the issue. Once Support determines that the device hardware is in a failed state, they can process an RMA and send out a replacement device free of charge. In most circumstances, the RMA will include a pre-paid shipping label so the faulty equipment can be returned.
Note that, for end-customer device security, RMAs may only be requested by Organization Admins (Read Only or Full), or Network Write Admins (only for devices in networks of which they are Admins). Meraki Support will not process RMAs unless the support agent can verify the requester has sufficient network permissions.
If you have not received a pre-paid shipping label in the box, please check your email inbox and spam folders 24-48 business hours after the replacement has been received for an email from FedEx or UPS to print the return label.
For more information about Cisco Meraki returns, please refer to our Return Policy.
Note: Return policy terms may vary by region. Please refer to the Regional Return Policies section of the Return Policy documentation for region-specific terms.
If you are experiencing hardware issues, please contact Cisco Meraki support by logging in to Dashboard (Help > Get help) or by calling us.
To request a Return Materials Authorization (RMA), please call Cisco Meraki technical support. Unless you have purchased Meraki Now, advance replacement orders will ship within 1 business day on a best case effort basis.
Additional information about Cisco Meraki’s hardware warranty can be found in Cisco Meraki’s End Customer Agreement.
Note: Devices that are dormant (grey status) and not connected or seen by the Meraki Dashboard require a photograph of the device with the serial number to process the RMA.
This does not apply to devices that have failed and show as recently offline in Dashboard (red status), or devices that are being RMA’ed for other reasons.
Warranty Coverage Period
Cisco Meraki stands behind its products. Hardware products generally come with a 1-3 year warranty or lifetime warranty, as specified on the relevant Cisco Meraki data sheet.
Some general warranty term lengths can be found below:
|MX/Z (e.g. MX100, Z3)||Lifetime**|
|MG (e.g. MG21, MG21E)||Lifetime**|
|MS (e.g. MS120, MS350)||
|Indoor MR (e.g. MR30H, MR52)||Lifetime**||Applies to MR device and ethernet cables in box|
|Outdoor MR (e.g. MR74, MR84)||1 Year|
|2nd and 3rd Gen MV (e.g. MV12, MV32, MV63)||5 Years||Does not include MV2|
|All other MV||3 Years||Includes MV21, MV71, MV2|
|MT Sensors||3 Years||Includes all MT sensors|
The following are considered accessories:
SFP Modules, twinax/SFP+ cables, stacking cables, all mounting kits and stands, antennas, interface modules, additional power cords, PoE injectors
*Original and replacement modular power supply units and fans for MS and MX Products are included in lifetime warranty and not the 1-year warranty for accessories.
**Product lifetime ends concurrently with product End-of-Support (EOST) Date as described in Cisco Meraki's End of Life (EOL) Policy.
***The Warranty Period commences on the date Hardware is shipped to the original purchaser as outlined in Article 5.4 of the Meraki Supplemental End User License Agreement
Note: Causes of performance issues that are beyond the reasonable control of Cisco Meraki are not included in the scope of the warranty.
Note: The above table is a general guideline for warranty terms and is not final. Warranty terms are subject to printed warranty information on the relevant data sheets.
Note: a warranty is not the same as a license.
Example: MR74 can have a valid 3-year Enterprise MR license, but that is separate from the 1-year warranty coverage period. In the given scenario, the MR device is not replaceable after the coverage period ends, regardless of license validity.
Troubleshooting before Returns
Prior to performing an RMA, Cisco Meraki Support will need to verify that some basic troubleshooting has been performed to resolve common issues. Please refer to the following articles for common symptoms and troubleshooting steps:
Product Trial Returns
If you would like to return units from a product trial, please go to your product trial webpage (using the link your rep provided you with) and go to the returns tab to fill out the RMA request form. If your trial hardware was shipped to the US, Canada, or an EU member country you will be able to print out a return shipping label and ship the product back to Cisco Meraki at no charge to you.
Effective January 30, 2022, all new Cisco and Meraki orders submitted for hardware, and any attached software, will be non-cancellable and cannot be modified starting 45 days prior to the current estimated ship date. Orders comprised of only Meraki licensing are not impacted by this policy change. Non-cancellable orders are not eligible for RMA credit and are not eligible for an RMA exception. For additional information, please contact your Meraki representative.
To request a refund for your license-only order, the following criteria must be met:
- You purchased the product through an authorized Cisco Meraki reseller or directly from Cisco Meraki
- You are the original purchaser of the product
- You submit your refund request within 30 days of purchase
Once you have logged out of all Dashboard accounts (or using an alternate/incognito browser), you can navigate to our RMA request form by entering "dashboard.meraki.com/rma" in your browser. Look up the license-only order and select which items you'd like to return. You can contact your Cisco Meraki sales rep or your reseller for assistance with this process and/or to make the corrected purchase.
If your refund request is approved, Cisco Meraki will email you an RMA number and we will process your return. If you purchased through a Cisco Meraki reseller, your refund will be issued by that reseller. If you purchased directly from Cisco Meraki, we will issue a refund, typically within 15 days of processing the return. (If you paid by credit card we will credit the original credit card. If you paid by any other method, we will send you a check.
After returning licenses, the original license key will be invalidated. If any licenses from the order were not returned, a new license key will be generated for the remaining licenses. This new license key will be emailed to the individual(s) who submitted the RMA request. If the original key was previously claimed to an organization, the new license key will automatically take its place (no need for further action).
Note that there are no exchanges for incorrect license purchases. Please utilize the refunded credit to purchase the correct licensing required for your device.
If you receive the error message: "Did not find an order that matches that order number, or you do not have access to that order. Please review and try again.", redirect to "dashboard.meraki.com/rma" after you've logged out of all Meraki Dashboard accounts and/or opened an incognito/alternate browser page.
- Please return units in their entirety. That is, include all power supplies, antennas, and other components along with the original product box.
- Please use the original shipping carton and packaging material. If this is not possible, use another shipping carton with padding to protect the units from damage during shipping. DO NOT ship a product without a carton.
- The customer will be charged for product that is damaged due to insufficient packaging.
- Once you have received your RMA number from Cisco Meraki via email, write this RMA number in large letters on the exterior of the shipping carton. Shipments to Cisco Meraki without an RMA approval will not be processed.
- If Cisco Meraki approves your RMA request, you will receive a confirmation email containing an RMA number within two business days. The address to which the product should be sent will also be included in that email.
- Cisco Meraki will provide a pre-paid return shipping label for warranty replacement return shipments. Cisco Meraki will also provide a pre-paid return shipping label for free trial return shipments from US (including Puerto Rico), any EU member country, Australia, Canada, Chile, Colombia, Costa Rica, Ecuador, Indonesia, Japan, Mexico, New Zealand, Panama, Peru, the Philippines, Singapore, South Korea, Thailand, the United Arab Emirates, and the United Kingdom. For all other returns it is your responsibility to coordinate and pay for return shipping back to Cisco Meraki using the carrier of your choice. Cisco Meraki recommends that the return package be given a tracking number and is insured for the proper value of its contents. Cisco Meraki is not responsible for packages lost by carriers.
Avoiding Licensing Issues After Replacing Device
Once the replacement device has been added to a network, it is recommended to remove the faulty device from its Dashboard network. The faulty device may remain in your inventory, but as long as it is not currently in a network it will not count toward your device limit.
Product End-of-Life (EOL)
Cisco Meraki may find it necessary to discontinue products for a number of reasons, including product line enhancements, market demand, technology innovation, or if the product simply matures over time and needs to be replaced by something functionally richer. We have set our end-of-life (EOL) policy to help customers better manage their product end-of-life transition.
Please refer to the Product End-of-Life (EOL) Policy page for more information.
End-of-sale (EOS) announcement: Date of official end-of-sales notice, typically six months prior to the last order date.
- End-of-sale date: The last date to order the product through Cisco Meraki point-of-sale outlets. After this date, the product is no longer available for sale via any channel.
- End-of-support (EOST) date: The last date a product will be affirmatively supported by Cisco Meraki, typically five years following the EOS date.
|Product||Announcement||End-of-Sale Date||End-of-Support Date|
|MA-MNT-MR-11||Aug 18, 2023||Feb 19, 2024||Feb 19, 2029|
|MA-MNT-MR-10||Aug 18, 2023||Feb 19, 2024||Feb 19, 2029|
|MA-MNT-MR-9||Aug 18, 2023||Feb 19, 2024||Feb 19, 2029|
|MA-MNT-MR-8||Aug 18, 2023||Feb 19, 2024||Feb 19, 2029|
|MA-MNT-MR-7||Aug 18, 2023||Feb 19, 2024||Feb 19, 2029|
|MA-MNT-MR-6||Aug 18, 2023||Feb 19, 2024||Feb 19, 2029|
|MA-MNT-MR-5||Aug 18, 2023||Feb 19, 2024||Feb 19, 2029|
|MA-MNT-MR-4||Aug 18, 2023||Feb 19, 2024||Feb 19, 2029|
|MA-MNT-MR-3||Aug 18, 2023||Feb 19, 2024||Feb 19, 2029|
|MA-MNT-MR-2||Aug 18, 2023||Feb 19, 2024||Feb 19, 2029|
|MA-MNT-MR-1||Aug 18, 2023||Feb 19, 2024||Feb 19, 2029|
|MR70||Aug 18, 2023||Feb 19, 2024||Feb 19, 2029|
|Z3C-HW-WW||Aug 11, 2023||Feb 11, 2024||Feb 11, 2029|
|GS110-8P (UK)||Feb 24, 2023||Aug 24, 2023||Aug 24, 2025|
|GS110-8P (EU)||Feb 24, 2023||Aug 24, 2023||Aug 24, 2025|
|GS110-8P (US)||Feb 24, 2023||Jun 1, 2023||Aug 24, 2025|
|GS110-24P (UK)||Feb 24, 2023||Jun 28, 2023||Aug 24, 2025|
|GS110-24P (EU)||Feb 24, 2023||Jun 28, 2023||Aug 24, 2025|
|GS110-24P (US)||Feb 24, 2023||Jun 1, 2023||Aug 24, 2025|
|GS110-48P (UK)||Feb 24, 2023||Mar 9, 2023||Aug 24, 2025|
|GS110-48P (EU)||Feb 24, 2023||Aug 24, 2023||Aug 24, 2025|
|GS110-48P (US)||Feb 24, 2023||Jun 1, 2023||Aug 24, 2025|
|GS110-8 (UK)||Feb 24, 2023||Aug 24, 2023||Aug 24, 2025|
|GS110-8 (EU)||Feb 24, 2023||Aug 24, 2023||Aug 24, 2025|
|GS110-8 (US)||Feb 24, 2023||Aug 24, 2023||Aug 24, 2025|
|GS110-48 (UK)||Feb 24, 2023||Aug 24, 2023||Aug 24, 2025|
|GS110-48 (EU)||Feb 24, 2023||Aug 24, 2023||Aug 24, 2025|
|GS110-48 (US)||Feb 24, 2023||Jun 1, 2023||Aug 24, 2025|
|GS110-24 (UK)||Feb 24, 2023||Aug 24, 2023||Aug 24, 2025|
|GS110-24 (EU)||Feb 24, 2023||Aug 24, 2023||Aug 24, 2025|
|GS110-24 (US)||Feb 24, 2023||Aug 24, 2023||Aug 24, 2025|
|MA-MNT-MR-H3||Dec 19, 2022||Jun 13, 2023||Jun 13, 2028|
|MA-MNT-MR-H1||Dec 19, 2022||Jun 13, 2023||Jun 13, 2028|
|MR20||Dec 19, 2022||Jun 1, 2023||Jun 13, 2028|
|GR10 (UK)||Oct 21, 2022||Apr 24, 2023||Apr 24, 2025|
|GR10 (EU)||Oct 21, 2022||Apr 24, 2023||Apr 24, 2025|
|GR10 (US)||Oct 21, 2022||Apr 24, 2023||Apr 24, 2025|
|GR60 (UK)||Oct 21, 2022||Apr 24, 2023||Apr 24, 2025|
|GR60 (EU)||Oct 21, 2022||Apr 24, 2023||Apr 24, 2025|
|GR60 (US)||Oct 21, 2022||Apr 24, 2023||Apr 24, 2025|
|MR42||Jan 27, 2021||Jul 14, 2022||Jul 21, 2026|
|MR33||Jan 27, 2021||Jul 14, 2022||Jul 21, 2026|
|MR30H||Mar 25, 2022||May 31, 2022||Jul 26, 2027|
|MR42E||Apr 22, 2022||Apr 22, 2022||Jul 21, 2026|
|MR55||Feb 15, 2022||Apr 7, 2022||Aug 1, 2028|
|MR53E||Feb 15, 2022||Apr 7, 2022||Jul 21, 2026|
|MR52||Feb 15, 2022||Apr 7, 2022||Jul 21, 2026|
|MX64, MX64W||Jan 26, 2022||July 26, 2022||July 26, 2027|
|MA-INJ-4-XX (AU, CN, EU, UK, US)||Oct 29, 2021||Nov 30, 2021||Nov 30, 2022|
|MS390 4x10GE Module (MA-MOD-4x10)||Aug 30, 2021||Nov 1, 2021||TBD|
|MX100||Aug 10, 2021||Feb 1, 2022||Feb 1, 2027|
|MX84||Aug 10, 2021||Oct 31, 2021||Oct 31, 2026|
|MA-INJ-5||Jun 1, 2021||Jun 29, 2021||N/A|
|MR84||May 3, 2021||May 7, 2021||Jul 21, 2026|
|MR74||Jan 27, 2021||Jul 21, 2021||Jul 21, 2026|
|MR53||May 3, 2021||May 7, 2021||Jul 21, 2026|
|MR45||Jan 27, 2021||Jul 21, 2021||Jul 21, 2026|
|vMX100||Sep 29, 2020||Dec 22, 2020||Dec 22, 2027|
|MV21 & MV71||Mar 19, 2019||Jun 19, 2019||Jun 19, 2026|
|MX65||Nov 20, 2018||May 28, 2019||May 28, 2026|
|MC74||Sep 27, 2018||Oct 1, 2018||Apr 1, 2019|
|Z1||April 27, 2018||July 27, 2018||July 27, 2025|
|MX600||Feb 28, 2018||May 20, 2018||May 20, 2025|
|MX400||Feb 28, 2018||May 20, 2018||May 20, 2025|
|MS220-8||Jan 9, 2018||Jul 28, 2018||Jul 28, 2025|
|ANT-10||Sep 6, 2017||Sep 11, 2017||Sep 11, 2024|
|MR62||Aug 15, 2017||Nov 15, 2017||Nov 15, 2024|
|MR66||Jun 7, 2017||Jun 9, 2017||Jun 9, 2024|
|MS220 series||Mar 16, 2017||Jul 29, 2017||Jul 29, 2024|
|MR72||Mar 7, 2017||Apr 30, 2017||Apr 30, 2024|
|MR32||Jan 18, 2017||Apr 30, 2017||Jul 31, 2024|
|MS320 series||Dec 8, 2016||Mar 31, 2017||Mar 31, 2024|
|MR18||Dec 8, 2016||Feb 13, 2017||Mar 31, 2024|
|MS420||Aug 1, 2016||Oct 31, 2016||Oct 31, 2023|
|MR34||Aug 1, 2016||Oct 31, 2016||Oct 31, 2023|
|AC-MR-1-XX(AU, EU, UK, US)||Feb 9, 2016||May 9, 2016||May 9, 2023|
|MR26||Feb 9, 2016||May 9, 2016||May 9, 2023|
|MX80||Jan 26, 2016||Aug 30, 2016||Aug 30, 2023|
|MS320 & MS420 power supplies and fans||Nov 16, 2015||Nov 16, 2015||Nov 16, 2022|
|MR12||Jul 27, 2015||Oct 24, 2015||Oct 24, 2022|
|MX60W||Jul 10, 2015||Oct 24, 2015||Oct 24, 2022|
|MX60||Jul 10, 2015||Oct 24, 2015||Oct 24, 2022|
|ANT-13||Jan 12, 2015||Apr 24, 2015||Apr 24, 2022|
|ANT-11||Jan 12, 2015||Apr 24, 2015||Apr 24, 2022|
|Systems Manager Support License||Sep 22, 2014||Sep 22, 2014||End of customer’s license|
|802.3af PoE Injector||Feb 27, 2014||May 31, 2014||May 31, 2021|
|MR24||Feb 27, 2014||May 31, 2014||May 31, 2021|
|MR16||Feb 27, 2014||May 31, 2014||May 31, 2021|
|MS22/P and MS42/P licenses||Jan 6, 2014||Jan 25, 2014||N/A|
|SFP/SFP+ Accessories||Nov 5, 2013||Apr 26, 2014||Apr 26, 2021|
|MS42P||Nov 5, 2013||Apr 26, 2014||Apr 26, 2021|
|MS42||Nov 5, 2013||Apr 26, 2014||Apr 26, 2021|
|MS22P||Nov 5, 2013||Apr 26, 2014||Apr 26, 2021|
|MS22||Nov 5, 2013||Apr 26, 2014||Apr 26, 2021|
|MX90||Nov 5, 2013||Apr 26, 2014||Apr 26, 2021|
|MR58||Jul 26, 2012||Oct 30, 2012||Oct 30, 2017|
|OD2||Jul 26, 2012||Oct 30, 2012||Oct 30, 2017|
|MR14||May 29, 2012||Aug 30, 2012||Aug 30, 2017|
|MR11||May 29, 2012||Aug 30, 2012||Aug 30, 2017|
|MX70||Jan 18, 2012||Mar 31, 2012||Mar 31, 2017|
|MX50||Jul 15, 2011||Sep 1, 2011||Sep 1, 2016|
|Indoor||Mar 3, 2011||Jun 30, 2011||Jun 30, 2016|
|Mini||Sep 3, 2010||Dec 31, 2010||Sep 25, 2017|
|Wall Plug||Sep 3, 2010||Dec 31, 2010||Dec 31, 2015|
|Solar||Sep 3, 2010||Dec 31, 2010||Dec 31, 2015|
Painting Cisco Meraki Devices
It is sometimes necessary to place APs or cameras in publicly visible areas that require them to blend into their surroundings. With access points, Cisco Meraki typically recommends hiding the AP from view (e.g., above a drop ceiling). However, customers sometimes choose to paint their APs or cameras to match the area where they are mounted.
Points to consider when painting a device:
Because paint has the potential to damage the units, painting does void the Cisco Meraki warranty. There is an exception for indoor Meraki MV smart cameras, see below.*
- Avoid getting paint inside of the unit, especially if painting cameras or indoor APs. Tape over LEDs, antenna connectors, screw holes, the camera dome, etc. to prevent paint from getting inside the chassis.
- The default white color of the device reflects light. Darker colors will absorb more sunlight and may cause the device to overheat.
- Never use paint with metal flakes, lead, carbon, or any other conductive material, as this will greatly degrade the device's ability to operate. This is especially true if used on antennas.
If theft is a concern, APs and cameras can run in "dark mode" which will turn off the LED lights on the unit, making the unit less noticeable at night. Please reference our documentation for more info.
*Warranty for painting Cisco Meraki MV cameras:
If the cause of the failure of the MV camera is due to the painting, we will not honor the Warranty.
Under the condition that the below instructions are met, the product warranty is valid and will be honored for painted INDOOR MVs ONLY.
This does not apply to OUTDOOR MV cameras; painting outdoor MV cameras will void the warranty.
The camera lens or lens cover should not be painted.
Paint must not seep under the casing, chassis, or into the materials at any point.
Things to note when painting cameras:
Product performance may deteriorate due to the painting.
Darker colors absorb more sunlight, which can affect the thermals of the product. This can impact camera's video recording performance such as fluctuation in recording FPS or corrupted video as well as missed object detections.
Meraki Technical Support will not assist in the painting of these cameras. With painted cameras, RMA processing time may be longer than usual due to the further review required before approval.