Cisco Meraki is announcing the end-of-sale for the following products, in accordance with their End-of-Sale (EOS) Policy for Meraki cloud managed networking products. The [MS250, MS350, MS355] have been replaced with the following products, which are functionally equivalent:
End-of-Sale Model | Replacement Model |
MS250 | C9300L-M |
MS350 | C9300-M |
MS355 | C9300X-M |
Cisco is expect to be accepting final orders for this product through August 8, 2025. However, the final date will depend on the availability of stock and, at Cisco Meraki's discretion, the actual end-of-sale date may be earlier than August 8, 2025. End-of-Support date for this product will be August 8, 2030.
End-of-Sale Model | Replacement Model |
MS410 | C9300-24S/48S-M |
MS425 | C9300X-12Y/24Y-M |
End-of-Sale Model | Replacement Model |
MS120/MS125 | MS130 |
End-of-Sale Model | Replacement Model |
MS390 | C9300-M |
End-of-Sale Model | Replacement Model |
MG21-HW-WW MG21-HW-NA |
MG41-HW |
MG21E-HW-NA MG21E-HW-WW |
MG41E-HW |
End-of-Sale Model | Replacement Model |
Z3-HW | Z4-HW |
Z3C-HW-NA | Z4C-HW |
They expect to be accepting final orders for this product through September 4, 2024. However, the final date will depend on the availability of stock and, at Cisco Meraki's discretion, the actual end-of-sale date may be earlier than September 4, 2024. End-of-Support date for this product will be September 4, 2029.
Cisco Meraki has a unique distribution model worldwide due to the fact the hardware and licenses are assigned to the particular end user that acquires the product. Here's the key takeaways from our Cisco Meraki Buying Guide.
There is no stock held by any Reseller in the USA - all new Meraki orders ship directly from their California, USA warehouse direct to the customer via Fedex. This is of course unless it's second hand, grey market or refurbished stock.
It typically takes up to 24-48 hours for Meraki to process an order and ship it - even if expedited. All hardware products ship via Fedex ground by default to you at no extra cost because the freight is built into the price we pay as a reseller.
We'd encourage you to choose your Reseller first (hopefully us!) and let us go to work for you to get the best price. We offer all inclusive pricing with free freight and the USA power cord included. We see a lot of our competitors advertise a cheap price on a device and then charging you extra for a power cord and even more for a freight/processing fee.
We are other Reseller and Consultant friendly! If you are NOT a Cisco Meraki partner and need to supply your customer, we are happy to work with you. We work mainly with IT Managers that need a fast, consistent and expert service. No order is too small or too large for us to accomodate.
We will work with you to provide the information you need to properly quote and supply your customer's requirements within the parameters of our Reseller Agreement with Cisco. We will get the best pricing possible by working with the Cisco Meraki team and be mindful that you need to share in the margin too when quoting!
Remember the team at Cloudmanagedwifi are Meraki experts and this is the only networking hardware vendor we work with. We process orders the same day we receive them (within minutes) and always have terms available with the vendor so there is never a delay with shipment due to credit issues.
End-of-Sale Model | Replacement Model |
MR70-HW
MA-MNT-MR-1
MA-MNT-MR-2 MA-MNT-MR-3 MA-MNT-MR-4 MA-MNT-MR-5 MA-MNT-MR-6 MA-MNT-MR-7 MA-MNT-MR-8 MA-MNT-MR-9 MA-MNT-MR-10 MA-MNT-MR-11 |
MR78-HW
N/A
|
There is much to be said about optimizing the Maximum Transmission Unit (MTU) size on your Meraki MX. The MTU is the maximum size of the packet transmitted over the LAN / WAN.
Too big an MTU means the packets sent are fragmented when they hit a router that only supports an MTU smaller than that which is set by default or otherwise. The default MTU of a Meraki MX is 1500 bytes (seen as a safe setting.)
You can test whether a smaller MTU size would be advantageous by following the article below:
When I test our MX with the value in the terminal line set to 1472 (MTU 1500 - which is 1472 +28 for the headers), it fragments. Then when I test it with a value of 1464 it returns correctly with no fragmentation. (MTU 1492 - which is 1464 + 28 for the headers).
If you do the troubleshooting as per the article and find you need to take action to reduce the size of the MTU, then there are a few ways to do this. You might want to check with your ISP what their recommended MTU settings are first.
Here are some steps you can take when dealing with an MTU issue.