In
part 1 of this series, we looked at SharePoint and compared an On Premise installation with a cloud-based one. In this article, we do a similar comparison with WIFI gear, comparing the controller-based Aruba with the cloud-based Meraki.
Every time we need to decide between two competing products, a series of tradeoffs arises. It is usually the case that there is no perfect answer, only indications as to which way might go better in most circumstances.
I recently faced this conundrum in comparing the enterprise WIFI offerings of Aruba and Meraki. These offerings take a completely different approach.
Aruba - The Controller Approach
Aruba makes wireless gear and associated network components, and nothing else. Their access points are extremely well built and engineered, and the price reflects this. While they do have a primitive cloud-based solution as well as an "Instant" embedded systems that autoconfigures access points for you, the flagship product requires the use of a controller and several sets of software.
In order to make your first access point operational in this environment, there is a long list of activities:
- Order everything you need. And that turns out to be harder than you would think. They have a broad range of access points, antennas, controllers, and mounting brackets. To order the gear, you really need a knowledgeable rep or reseller
- Buy the licensing you need. This may include the controller as well as Airwave and Clearpass software.
- Install the controller, and get it licensed. The controller has an interface that only an engineer could love. There are so many tabs, menus, sub tabs, sub menus and expanding areas to even get to a page that has 100 different settings on it.
- Configure the controller. So, you use this complex interface to setup your SSIDS, VLANS, radio settings and many other areas. At a minimum for this first AP, you'll need an SSID and a VLAN, possibly firewall settings and a DHCP server
- Rack the controller, power it, connect it to your network switches and routers
- Connect an Access Point to a POE+ port (or injector) into your network
- If the controller was setup correctly, it will find that AP and present it under the configuration tab, AP installation menu. You select it, then click the provision button. This takes you to a page full of text boxes, radio buttons, and not much in the way of explanation. It's here that you name the AP, tell it about the controller, set its radios and IP address
- Will you want to report on wireless usage? If so, you'll need to buy, then download and install their Airwave software. To do that, you'll need to build a server to host it (the server can be virtual)
- Will you want to see things from outside your network? Then you'll need to setup a VPN connection to your controller and to Airwave.
All in all, and assuming you have solid networking skills and VMWare skills going in, you're looking at probably something on the order of 100 hours worth of work. I guess the good news is subsequent installs can get down to an hour or two.
Cisco Meraki - The Cloud Approach
Meraki, in contrast, is astonishingly simple:
- Order the gear. They only have a few models of access points and antennas. Basic mounting kits are included. They'll also send you eval units so you can see for yourself how simple this is. While Aruba will also give you an eval, they're not going to give you 100 hours worth of install.
- Order the cloud license.
- Install the AP. Once it arrives at your office, connect the AP to a POE port on your network. See this article for a useful tip on installing your AP and deciding locations prior to making a commitment.
- Go to the Meraki site and setup your account. They have a wizard to walk you though setting up SSIDS and everything else you'll need. Next enter the serial number of your AP.
- Um, that's it. The AP comes up. You position it on a map. The reporting interface immediately starts recording user activity. You can reboot the AP, flash its lights, and override a limited and understandable set of features.
All in all, even if you're pretty new to this stuff, you're looking at an hour or two of work.
Cost Comparison
I am nothing if not a keen negotiator, and I work at a non-profit where pricing tends to be great. So YMMV, but I got the 5 year cost of a Meraki outdoor AP down to about $800 and the 5 year cost of Aruba at $950. In fairness to Aruba, that per AP cost will go down the more I add (but I am licensed to 128 APs. Go over that, and the next tranche would kick me over $1000).
So Why on Earth Did I Choose Aruba??
So it costs more and is hugely more complex. Why did I go with Aruba?? A big reason was certainly that Aruba started a relationship with me with a sizable donation. Then they followed up with a discount that I imagine is deeper than most could get. But even so, I wanted to make the right decision, and Meraki was a definite contender all the way along.
Truth be told, there wasn't a bad decision to be made here. But my reasoning was as follows:
My Trade-Off Analysis
- Relationship. Aruba became very personally involved with my account. I know engineers by name, and have their cell phone numbers. My experience with Meraki certainly wasn't a bad one, but if you're going to go with a cloud-managed provider, then by its very nature it will be more cookie cutter and less personal.
- Technology. The outdoor Aruba AP-275 is an AC model. The Meraki MR66 is only N, and so far Meraki doesn't have an outdoor AC unit. I wanted to future-proof my installation as best as possible.
- Performance. In my own testing, both Meraki and Aruba performed well, but my testing wasn't really under any kind of load. Then I read Tom's Hardware "Cage Match" and developed great concerns over Meraki, both under load and in its "air fairness" practices. I did not however do my own testing to this level, and if I were to take everything Tom's article said to heart, I would have ended up buying Ruckus!
- Tweakability. This is a tough one. I think Meraki is this >< close to making this unnecessary. And Aruba quickly loses me with complexity; I don't really want to be an RF engineer. I just want WiFi to service a few thousand people flawlessly. But I have found that a call to Aruba support will get an engineer who remotes into my PC and I get to watch while they make changes.
- I already paid the heaviest price in setup. I spent more than 100 hours setting up controllers and software. But now, adding an AP is a simple matter, and takes 10 minutes. Installing it outside is another matter (Atlanta heat, angry yellow jackets, and poison ivy all awaited me), but that would be true no matter what gear I used.
- Warranty. The Aruba outdoor AP has a lifetime warranty. Meraki's outdoor units are only 1 year.
But that's me and my tradeoff analysis. You have your own set of unique circumstances. Cloud managed WIFI is very compelling. The Meraki interface is a thing of design beauty. You don't need to know dBI from SNR. You can order some eval units and see for yourself, without any commitment (not even return shipping). You can't really do the same thing with controller-based solutions like Aruba or Ruckus.
