If you are using them together as an HA pair, then you only need 1 license. If you are using them separately, then you will need a license per appliance. If you are using them in an HA pair, then like @MarcP said, they have to be the same model. 2xMX84, 2xMX100, 2xMX67W, etc.. In your case, since you are purchasing two MX84s, you'll be okay.   https://documentation.meraki.com/MX/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair   Hope this helps ... View more

Welcome @FJOM! Once you start moving toward Meraki, you don't want to go back 🙂 ... View more

Glad it is working! ... View more

Hi @Chris_Durham, I was just working with the MS Switch Stacks recently so I think I know what the issue is. You stated the stack was created before the switches where connected. That is your issue. If you look at the switch stack config documentation, there is kind of a process with the stack setup. https://documentation.meraki.com/MS/Stacking/Switch_Stacks   The steps below explain how to prepare a group of switches for physical stacking, how to stack them together, and how to configure the stack in Dashboard. Add the switches into a Dashboard network. This can be a new Dashboard network for these switches, or an existing network with other switches. Do not configure the stack in Dashboard yet. Connect each switch with individual uplinks to bring them both online and ensure they can check in with the Meraki Dashboard. Download the latest firmware build using the Firmware Upgrade Manager under Organization > Monitor > Firmware Upgrades, if they are not already set for this. This helps ensure each switch is running the same firmware build. With all switches powered off and links disconnected, connect the switches together via stacking cables in a ring topology (as shown in the following image). To create a full ring, start by connecting switch 1/stack port 1 to switch 2/stack port 2, then switch 2/stack port 1 to switch 3/stack port 2 and so forth, with the bottom switch connecting to the top switch to complete the ring.   Step 4 includes the image @DarrenOC provided and continues through the steps on how to setup the stack.   I tried the same thing you did my first time setting up the stack and I had all kinds of issues. If you follow the documentation it should come up for you and then you'll be able to use 1 uplink for the stack (multiple is better as others have pointed out).    Hope this helps.  ... View more

That would work too @BlakeRichardson! ... View more

This may help. https://snehpatel.com/index.php/2019/09/11/configuring-syslog-in-meraki-device/ ... View more

Like @Bruce @Inderdeep stated, the short answer for new hardware is no. Additionally the licensing for Systems Manager is different from the hardware licensing so I can see where that may not exchange well when converting from SM to MX,MS,MR or etc. equipment. If you really wanted to go the route of purchasing equipment without licensing, the only way would be to purchase the hardware on eBay. With that comes a huge risk though because the equipment needs to be unclaimed and they are not covered by warranty. To me and probably the rest of the community, it's just not worth the savings you'd get from transferring the SM license. I would just work through your account manager and equipment vendor and I am just they can get you great deals. Possible? Yes, but only used and at what I think would be more costly in the long run. Advisable? Definitely not. But now you know. ... View more

That's what I figured out as well. There must be a good amount of bugs because all of my networks on 12.28, changed there status from "Good" to "Warning by April 30. " ... View more

I would just contact support or your account manager and have them issue an RMA. That should be covered. New camera and you don't have to deal with fixing cables. ... View more

Awesome job everyone and thanks again @MeredithW  for another successful points contest! Those are some great numbers! Congrats @sambo on winning the camera! ... View more

That's a good point as well @PilipDAth. Huawei will also work, unless you are in the following countries: Sweden, United States, Australia, the U.K., and France. These countries have banned Huawei. ... View more

I've used it on the MX65(W), Z1 and Z3 appliance and they all have worked within the last year. If you are looking for cellular failover specifically, then down the road, I'd budget for the "C" options (if you are looking at the Z3, MX67, or MX68 appliances). Not ideal, but good to note so that the 4G is built-in rather than the USB. I'd say if you can, buy a few different USB 4G dongles and try them out. Skyus, Verizon, Sprint, or whatever provider you have. They might work. All-in-all I still agree the list needs to be updated. ... View more

@MarcAEC, are you using both ethernet internet uplinks and the cellular failover? While I agree that they should increase their list of 3rd party USB devices, I would say these are the "official devices." There are a couple options I have found to assist in the 4G backup space. I have used Verizon's 730L on my Meraki MXs/Z3s. https://www.verizon.com/internet-devices/verizon-global-modem-usb730l/ If you aren't using the secondary ethernet connection, on the MX appliances, we purchased the Skyus 140/160 modems. They provide a direct ethernet connection to 4G cellular and is, what I believe a better solution to cellular backup. It has immediate failover and a lot more features than the cellular back up setup. https://inseego.com/products/enterprise/skyus-160/. Honestly, Meraki has been digging deeper in the cellular connection space with the integrations of SIM cards in their MX and Z3 lines (MX67C and Z3C devices). Additionally they recently introduced the MG21 cellular gateway that is just like the Skyus 140/160, but much more ideal since it integrates with the dashboard. https://meraki.cisco.com/product/security-sd-wan/teleworker/z3c/ https://meraki.cisco.com/product/cellular/integrated-antenna/mg21/ This doesn't make up for Meraki's lack of updating their list of devices, but they do offer a number of solutions. ... View more

Definitely @EJN! The way I understand it is roughly. 1 Year = cost of 1 year - $145 3 year = cost of 2 year - $285 5 year = cost of 3 year - $430 Again, this is all MSRP pricing. I am sure that if you work with your supply vendor (CDW for example), they can find more savings as well. If you go to humming bird network sales, they sell the 1 year at $84.74 US Dollars. https://www.hummingbirdnetworks.com/cisco-meraki-license-renewal-lic-ms120-24p-1yr/ Hope this answers your question @Felix_Mugambi. ... View more

Hi @Felix_Mugambi, In the US, you are looking at about $145 MSRP. This price can vary when working with your purchase vendor. If you ever need MSRP costs for Meraki equipment, you can use the Meraki Cost Calculator. https://meraki.cisco.com/buy/cost-calculator It has helped me a lot during budget times! ... View more

Updating everyone who is here on this issue. We seem to have found the problem. This is an issue affecting the MS120 series switches and it deals with Access Policies causing CPU spikes in the switch. I worked with support and we were able to reproduce the issue in the test environment. If you would like to see the same issue, you'll need an MS120, a RADIUS server for 802.1x authentication, and about 10 devices for good measure. Setup the Access policy and assign it to the switchports connected to the end devices. In my test environment, I had to disable and enable about 20 ports to get the error, but when I disabled the ports, this is what would happen: Config would start and my continuous ping would go from about 10ms to 1000+ms. After about 2 pings, the switch would stop responding and my PoE phones would say "Network Disconnected" but the power would remain. It took about 20 pings for the configuration to go through and disabled the ports. At that point the switch would resume. Removing the access policy would stop the switch from loosing pings, but would still cause brief 1000+ms during the config update. After a while, the changes would cause so much CPU utilization that the switch would soft reboot. This issues is present in firmware versions 11.31, 12.28, 12.33, and 14.16. Support has instructed me this is specific to the MS120 and a CPU issue, which the development team is aware about, escalation priority needs to be higher. So if you are using MS120s or have customers that utilize the MS120s with Access Policies configured, I would suggest reaching out to your account rep or support to have them escalate this issue and get it fixed as soon as possible. Thanks for all of your suggestions everyone! ... View more

Hi @BGFFernandes, It will not. Based on the spec sheet, the MX64 will allow 250Mbps of firewall throughput and 100Mbps of VPN throughput. Hope this answers your question. https://meraki.cisco.com/product/security-sd-wan/small-branch/mx64/ ... View more

If you have an Account Rep, reach out to them and I am sure they can push this through for you. ... View more

Hello @Antonio_Ruiz! Welcome to the Meraki Community! It is a great community to be a part of and we are glad to have you here. Krebs on Security is a great blog to follow. Also if you like security, check out the podcast darknet diaries. ... View more

Hello @BeniMaurer! Welcome to the Meraki Community! It is a great community to be a part of and we are glad to have you here. ... View more

Hello @MikeHoule! Welcome to the Meraki Community! It is a great community to be a part of and we are glad to have you here. ... View more

Hello @ddv_ua! Welcome to the Meraki Community! It is a great community to be a part of and we are glad to have you here. ... View more

Hello @DarrenLucht! Welcome to the Meraki Community! It is a great community to be a part of and we are glad to have you here. I was able to get my Acura TL up to 250,000 when I sold it. I still saw it driving around town years later still kicking! ... View more