Basically, MikroTik Routers fulfill the main functions required by small and medium-sized companies (Routing, OSPF, BGP, Firewall, DHCP, DNS, PPP, among many others). However, the choice of another product is motivated by the limited number of SFP ports that MikroTik products …
I'd say the thing is I don't think there's any environment where it's less suited unless it has to be maybe in a rugged environment where it would be susceptible to environmental issues. But yeah, I think it performs really well in every scenario we placed it.
MikroTik is suited for large companies that require advanced distributions in terms of contracted bandwidth, and in the same way, allows a single device to specify filtering and firewall rules without acquiring an additional device. There is a range for small companies which is more economical and less robust, but in case it's not necessary, such a strict control over the data consumption of the company is not a feasible solution.
Dashboard - Up/Down ease of checking up/down devices status
The template config, easy to copy and bulk deploy config to multiple switches. This can be used to fix a bunch of MS switches simultaneously too which is very helpful.
The integrated features such as Cisco Umbrella and guest WiFi. The customer really appreciated the rapid possibility of getting a site up and running without tinkering through complex configurations.
Multicast configuration in the L3 settings was very easy to setup and get running. (Snooping Querier)
I think the biggest improvement is actually being able to see the hardware status, like the actual CPU status, memory status. Is there something, if there's an issue, one of the biggest issues that we've had is we could see whether some port information, we can see some ups and downs, but we don't, unlike the Cisco Catalyst series which we use also, we are able to dig in and confidently look at like, Hey, why is this device having an issue? We can't really do that with Cisco Meraki. We just kind of have, see if it's up or down and we like, well, we don't know exactly why it's down or we don't know why it could be having an issue.
Some of the wiki articles have not been updated or are not accurate enough. We spent a couple of days trying to find an example of implementing a mobile IPSec client solution. But once this has been implemented, it has been solid (always worked). A bigger community would help, and I am finding it hard to find the time to contribute to these articles.
Being on the cloud its very easy to manage. We have layer 7 visibility and Cisco has introduced stackable MX switches which is even better! The Meraki portal can be accessed via SSO which is important to my organization (although it was a bit difficult to get that implemented initially!)
Meraki support is excellent. They are also highly proactive. They literally replaced all of a particular model of our MS switches when it was discovered that they were not sure about the longevity of a particular chassis fan inside those switches. Without us having to do anything other than ask, they shipped us all new replacements (with a better fan in them) for the 10 or so of the switches that were in the affected model group, and we shipped the defective ones back to them int he same packaging, prepaid. None of the recalled switches had ever experienced a fan failure, but they were not willing to let them run in a production environment. I like that. Meraki MS support staff are also quick to get back to you and very knowledgeable about their product. I actually contact our Meraki rep to instigate a support case (although i could call support directly), and he gets the details from me first, then opens the ticket for us and explains it to support. This means that I only even need to talk to one person, and I like that, too. Meraki MS switches are designed to be essentially "plug and play", so support is generally not needed unless the end user is not following the deployment and operation guides
There is no SOC, NOC, where you can contact to try to resolve any difficulties. The problems that these devices have are solved largely through the community, with workaround alternatives, or if the support team responds to a request, the response times are too high for the current needs of technological communications.
Well, we've been using it for quite a number of years, so I guess I have evaluated, this is on the wireless side, the Ruckus platform, and it did not compare to the Cisco Meraki dashboard as far as the way it is utilized.
Cisco Routers are one of the best in the market, however they are also very expensive and not suitable for a small deployment or any deployment which requires just a couple of routers. MikroTik on the other hand are less expensive and provides many features that you require for a small scale deployment. they fit in with the budget and do what you need them to.
I would say probably eight. I think there's a lot of, the scalability is very nice and I've definitely deployed a lot of sites quickly. I think for us right now that we have to pivot away from manual configurations and using automated configurations. And so just being sure we prevent things like drift between sites is kind of important right now for us. And so I think that's the next steps for us in that product. And so I think if there was better documentation or better best practices about how to automate and deploy standardized, I think that would help.
