Coming October 25: PeerSpot Awards will be announced! Learn more
Buyer's Guide
Wireless LAN
September 2022
Get our free report covering Ubiquiti Networks, Cisco, Aruba Networks, and other competitors of Aruba Instant. Updated: September 2022.
633,952 professionals have used our research since 2012.

Read reviews of Aruba Instant alternatives and competitors

Network and Security Consultant at a insurance company with 1,001-5,000 employees
Real User
Top 10
Overall a good product that provides role-based authentication native to the controller, but has code stability issues
Pros and Cons
  • "Aruba is an industry leader. The hardware is on par, and its performance is also on par with anybody else. The Aruba brand really only focuses on wireless, so they're not competing their R&D for switching data center products and cloud security. They're really focused on that and their underlying key pieces. They provide a role-based authentication that is native to the controller. A lot of other systems don't do that. They won't provide you the ability to basically have everybody join the network, regardless of whether or not they share the same network space, the SSID, or the wireless LAN. You can segment it down to a specific user role based on any kind of attributes that you like. That's their differentiator. If you need per user, per device, or per port segmentation, you can get that with Aruba. There isn't another vendor who does it."
  • "Currently, the stability of the code is the basic underlying problem for us. They had an 8.6 release that came out two weeks ago, but we had to migrate twice because the code wasn't stable. We can't get things to work the same way. Version 8 was a big change for them. They made a change so that it is forced to be a managed hierarchical system. It means that you make changes at the top, and it pushes them downstream. There are a lot of problems with the 8.6 version code. I ran into four bugs in one week and was informed that we should just move onto the next one because all of those fixes have taken place. The feedback loop for fixes is not always really relayed back to you. I don't have a lot of strong things to say about version 8.6. When we had version 6, the controller was pretty much rock solid. We had no problems. We made a heavy investment to migrate a lot of stuff to take advantage of things like WPA3, Wi-Fi 6, and all that kind of stuff, and we haven't been able to turn those features on because we are not confident that they are going to work just yet. So, right now, we're still very much stumbling through the version 8.6 code and just trying to make sure that it is safe before we turn on some of those features. In terms of the marketplace, they are one of the top three leaders. In some respects, one of the things that they focus on is wireless. Therefore, there are some things that should be beyond reproach, as far as I'm concerned. In terms of the stability of the code, there are always going to be bugs, but the core stability of the code needs to be there. When it is not stable, that's a real problem for me because you lose a lot of confidence in the products."

What is our primary use case?

We run a number of guest wireless networks with captive portals with layer 3 networks. We run .1x for corporate SSIDs or wireless networks for additional certificate-based and/or WPA2 security.

How has it helped my organization?

Aruba has a lot of features that work particularly well. One of the things that Aruba is trying to do in most of its product ranges to make sure that all of their products now have a fully functioning northbound set of APIs. That basically means that you can plug it into any kind of system that you have for some operational pieces. For example, if you want to have Tufin, but more in line with things like change management. We're a ServiceNow shop, so we use that for change management and orchestration.

The ability to use the APIs that are available in the Aruba Wi-Fi controller means that you can get information from the system very easily by using APIs, or you can push changes to it. So, if you want to lock administrators there and restrict the type of functions that people can do, you don't have to give them access to the systems anymore. 

This functionality has been useful for us because we have recently outsourced a lot of our lower operational tasks to an outside vendor. With that, obviously, other people need to access systems, but we don't always want to give them direct access to the system. So, we can provide them with APIs to be able to perform basic tasks without giving them access to our dashboard services.

What is most valuable?

Aruba is an industry leader. The hardware is on par, and its performance is also on par with anybody else. The Aruba brand really only focuses on wireless, so they're not competing their R&D for switching data center products and cloud security. They're really focused on that and their underlying key pieces. 

They provide a role-based authentication that is native to the controller. A lot of other systems don't do that. They won't provide you the ability to basically have everybody join the network, regardless of whether or not they share the same network space, the SSID, or the wireless LAN. You can segment it down to a specific user role based on any kind of attributes that you like. That's their differentiator. If you need per user, per device, or per port segmentation, you can get that with Aruba. There isn't another vendor who does it.

What needs improvement?

Currently, the stability of the code is the basic underlying problem for us. They had an 8.6 release that came out two weeks ago, but we had to migrate twice because the code wasn't stable. We can't get things to work the same way. Version 8 was a big change for them. They made a change so that it is forced to be a managed hierarchical system. It means that you make changes at the top, and it pushes them downstream. There are a lot of problems with the 8.6 version code. I ran into four bugs in one week and was informed that we should just move onto the next one because all of those fixes have taken place. The feedback loop for fixes is not always really relayed back to you.

I don't have a lot of strong things to say about version 8.6. When we had version 6, the controller was pretty much rock solid. We had no problems. We made a heavy investment to migrate a lot of stuff to take advantage of things like WPA3, Wi-Fi 6, and all that kind of stuff, and we haven't been able to turn those features on because we are not confident that they are going to work just yet. So, right now, we're still very much stumbling through the version 8.6 code and just trying to make sure that it is safe before we turn on some of those features. 

In terms of the marketplace, they are one of the top three leaders. In some respects, one of the things that they focus on is wireless. Therefore, there are some things that should be beyond reproach, as far as I'm concerned. In terms of the stability of the code, there are always going to be bugs, but the core stability of the code needs to be there. When it is not stable, that's a real problem for me because you lose a lot of confidence in the products.

For how long have I used the solution?

I have been working with Aruba Wireless for about four years now.

What do I think about the scalability of the solution?

It is pretty good. There are a lot fewer people in the office, obviously, because of COVID. Under normal situations, we were probably about 2,000 users a day. Between 40% to 50% of that would be corporate users with mobile devices, such as iPhones, as well as laptop users accessing corporate resources and the corporate LAN. We also have guest users.

They are really moving towards making it cloud-based and less attractive for you to use on-premises. There are still a number of limitations with the cloud. One of the reasons we don't use cloud controllers is that they're not able to support more than 250 access points per tenant instance. For example, you have two sites. One has 200 APs, and one has 300 APs. You could put one site in the cloud so that you wouldn't need to have on-premises wireless controllers. You could manage it all from the cloud instance, and you would have zero hardware and all that kind of stuff. 

However, you wouldn't be able to deploy the second site in the cloud because you can't put more than 250 APs. So, now you have got to go back to doing it the old-fashioned way, which is to have on-premises controllers or two management suites. You don't want to do that because the way this new code works is that it is hierarchical, meaning that you build your configuration centrally, and then you push it down to your access points or your local controllers. So, if you've got one management session in the cloud and one management session on-premises, you would have to manage them at two places.

I do understand that you can configure that local hardware. So, for the site that has 300 APs and a local controller, you could plug that controller into the cloud, but it is still for two different models. So, the companies that just want to have a very simplified setup or want to make it less complicated, they can just say that we're going to go cloud or just stay on-premises, but now you have to have a combination of both, or you just stay with on-premises. There are still some basic limitations preventing us from doing wireless deployments where controllers are based in the cloud.

How are customer service and technical support?

I use them a lot. Sometimes, I use them every day. They are pretty good. There is a problem in getting hold of people. That may be just because of COVID, but it is very much dependent on when you call and the type of issue that you have.

If it is a fairly standard issue, if you need assistance with a programming or configuration change, or if you need to know how to do something, you can normally get a very quick resolution. The meantime for resolution is pretty quick. It is within that call, half an hour, or one hour. You can generally speak to somebody. If it is some of the things that I have experienced or a bug, it can be very problematic. It could take days or weeks to get resolutions.

The basic stuff is really good. Anything past that, you probably need to have a dedicated support engineer on your camp if you're big enough, or you need to have resources that really know how to do the legwork beforehand.

Which solution did I use previously and why did I switch?

I worked for a company that had Cisco for many years. Actually, towards the end of that, I switched them from Cisco to Ruckus. I did a POC and a pilot between Ruckus and Aruba, and Ruckus came out on top because of its simplified approach to wireless networking. I have also used Meraki, which is Cisco's cloud-only based AP solution. 

Cisco is like the other de facto. A lot of shops are all Cisco. Their hardware is probably on par with Aruba in terms of processing and handling capabilities. Features are also probably the same. It is more like a Ford-GM question. If you were brought up in a Ford household, you are probably going to buy a Ford sort of thing. I don't think there is much to them, to be honest.

The differentiator for me is that Cisco has a product, which is its network access control system, called ISE or identity services engine. That's a terrible product. It really is an awful product. It is very cumbersome, and it makes adding network access control to your wireless and wired networks very problematic. Aruba's product is called ClearPass, and it is a very flexible tool and easy tool. It is a much more reliable tool. While it doesn't have all the features that you can use with Cisco, it is a standard network application system, which means it will work with any vendor for any system. So, you can do 90% to 95% of the stuff you want, and it is a much more stable and capable system. This difference and the price are differentiators for me. 

From a purely wireless perspective, I think that Aruba is number one. Cisco is a very close number two, and then Ruckus is actually a distant third. Ruckus doesn't have all of the advanced capabilities, but what it does, it does very well. If you want a very basic entry-level wireless that is cheap for K-12 schools or a lot of environments like that, you can use Ruckus. If you need some of the advanced stuff, then you're going to have to pick one of the other solutions.

How was the initial setup?

I would say it is straightforward. It is just that it is a backward way of doing it. They had a fundamental shift in the way you deploy configurations in version 6 to version 8. So, basically, you would do one way in version 6, and then they completely reversed it in version 8. When you come into the product for the first time, it is easy and fairly straightforward. It is an easy adoption process. If you have got lots of experience with the previous version of code, such as version 6, and then you move to version 8, it is very confusing.

What's my experience with pricing, setup cost, and licensing?

Aruba is probably cheaper than Cisco, and yet you get all the things that you want.

What other advice do I have?

I would recommend Aruba Wireless, but it depends on the size and the scope. If you are a large-scale enterprise, you are going to need to deploy something large. If you are a big university or something, you are going to have to pick one of the big three, which, in this case, is going to be Cisco, Aruba, or Juniper. Juniper's Mist is a recent addition that is hugely popular right now because of a lot of the stuff it does in the cloud. They are all cloud-based controllers, and they integrate machine learning into all of your analytics to give you data. 

I think that Aruba Wireless is a good product overall. They have some code issues with this change as most vendors do when they go through a major change. The product hardware is really good, and they have additional capabilities that Cisco doesn't have, like being able to do per-port tunneling so that you can keep isolation on. They are building features, and you could only make use of these if you extend out and use all the Aruba products like Aruba switches, Aruba ClearPass, etc. 

I've had a couple of conversations with them about the next release, which is actually pending. I don't think it is happening this year. It will happen next year. Version 10 is their next step of code, and it is geared more towards automating a lot of the setup. There are still a lot of manual tasks that you have to do. The automation piece has been something that has really garnered a lot of interest from the wireless community in terms of being able to set networks up. You can just buy access points and just throw them up, and once they're powered on, they communicate with zero-touch provisioning and all that kind of stuff. A lot of the automated processes are coming along, such as the ability to tie in cloud-based analytics to look at your reports, training, or data, like Juniper Mist is doing.

There will also be a change in the user interface. They have now brought in things like COVID tracking. It is not like they are adding features that the market wants. They will add the ability for you to be able to write things that you want to see so that you can basically do your own SDK, if you like, and more easily be able to tie that into what you're doing. I'm not sure whether they'll offer that within the version 10 code.

I would rate Aruba Wireless a seven out of ten. The negatives are the instability with the specific versions of code. These could be specific versions of code, but the newer features, such as WPA, WiFi 6, require some of the newer code. The newer code isn't really very stable yet. The high point would be that it is still an industry leader with on par hardware and performance like anybody else.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Network Engineer at County of victoria
Real User
Top 20
Robust with a good level of performance and very helpful technical support
Pros and Cons
  • "It always runs, and it's very reliable in terms of performance."
  • "Their software's really clunky."

What is our primary use case?

We work at a courthouse, however, we manage the data for the entire county. We have them at the Sheriff's office. They use them in commissary purchases, which is a separate SSI and separate VLAN. That's to segregate wireless traffic for different groups of people per their needs. 

We have lawyers that maybe need to reach back into the network and access their documents when they take a laptop to the courtroom with them. And so through that, we've done some radius authentication. Therefore, it's not just an SSI ID. They actually have to log in with credentials as well. 

Then, we have a guest SSID just for general public access, and that's basically running wide open. We do have a simple password audit, however, everybody knows it, and that's separated by VLAN as well and run through Palo Alto. We also have a whole different SSID for patrol units for the Sheriff's office, where they upload car videos and update their car computers wirelessly. We use it broadly. 

How has it helped my organization?

The solution has let us get network access to more people in different locations where wires aren't feasible - like in a garage or for the Sheriff's office uploads in courtrooms. In some of these courtrooms, you can't run additional wire due to the fact that they're historical buildings. You have to have wireless. Also, you have lawyers walking around and you don't want them tripping over stuff. It's useful in every aspect of getting public access - even for when there are events in the square, across from the courthouse. It's basically helped us better serve everybody and provided them with network access.

What is most valuable?

It always runs, and it's very reliable in terms of performance. They are very, very robust, very rugged, and can handle indoor or outdoor coverage. We typically don't have too many problems with the hardware.

What needs improvement?

The wireless LAN controllers at the time when we started rolling out, we went with it simply due to the fact that everything else worked that was Cisco. We figured, if everything else works and we're satisfied with it, let's go that route. However, now people want more access points and more spots. And if you give everybody coverage, the cost is crazy high. You can either say, "No, we can't," or you can go with the cheaper product, even slightly cheaper, plus you get more APs out there for more coverage.

At least with the WLC 2500 that we've been using, you can't take just the stock AP from them. You have to use lightweight firmware. You turn it into a lightweight AP and then you can join it to, or provision it to, the wireless controller, which should be automatic. In most cases, it works pretty well, however, it's still not there yet, as far as plugging it into this network that's going to tunnel back to the controller. I would say it works 7 out of 10 times. For the price, it should be a 10 out of 10. Especially with Cisco running an entire Cisco network with CDP all over the place, there should be no reason it doesn't tunnel back every single time. And yet, there are a few times where it doesn't.

It got to the point where, when I prevent in APs, I just take them directly to the switch that the controller is plugged into and provision them there instead of just plugging them in like you should be able to. 

The software on offer is not great. Cisco lacks in software updates, surprisingly. They don't update their firmware too much for the controller. This is not something you want to be done constantly as it does make downtime, however, I would like to see them more than once a year. Unless there's a critical flaw, or you're running an early release. They're their main releases, I want to say year after year, it's been maybe once a year, and then you have to push it out to all your APs. 

Their software's really clunky. It's not very user-friendly, which you can see that as a good thing and a bad thing. We should learn this stuff, but at the same time, it shouldn't be overly difficult. You shouldn't have your options hidden in menus. You shouldn't have to go 25 minutes deep to get to some security options for a specific SSID. 

Also the way the group their security settings is a little bit backward to me. It's not done by SSID. There's just a security tab. Then, you have to link back and forth through that. However, that's something that you're going to fight with through every controller, every different type of device. We all wish they were organized differently. 

For how long have I used the solution?

We originally started using the solution in 2014.

We had one before then as well. Since we've gone wireless, or implemented wireless throughout the buildings here, we've always used Cisco. This is just a Cisco shop. 

What do I think about the stability of the solution?

The solution is extremely stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

The one issue we did have was with their mesh radios. I'm not sure that it was with the radio itself, the software in the radio. They run two different firmware. One is autonomous firmware, which they use with their AP line and then lightweight APs. With the autonomous one, there's no consistency there. For the indoor APs, you'll have lightweight firmware that you need on them. And then for the outdoor mesh radios, they're not fully autonomous, yet you have to have the autonomous software on them for the mesh feature to function. That's a little bit convoluted and I kind of wished that would just have it one way or the other.

What do I think about the scalability of the solution?

The solution scales easily.

The number of users varies. Some days we have court cases and then you have jurors, lawyers, the media people. It varies widely. I would say on average, we have possibly 200 people a day on a slow day using it. And then on an extremely busy day, it could double that.

We use the solution quite extensively.

We do plan to increase usage, however, it won't necessarily be with this product. We'll probably like to go with a different product based on price and licensing.

How are customer service and technical support?

Technical support is 10 out of 10. Cisco tech support is one of the best supports I've ever dealt with.

How was the initial setup?

The initial setup was very straightforward. As we have added SSIDs, when we have had a hardware failure, the re-setup, for instance, is a bit more involved. When the controller itself was acting kind of finicky, we did an overnight request and got one in. Re-uploading that configuration was not as easy if that makes sense. If you're setting up a brand new device, it's very easy, very straightforward. If you're trying to restore from a backup configuration, it's not as easy. We ended up actually just resetting it up from scratch.

The deployment itself likely took three hours.

We had some bugs to work out after that, however, the majority of it was up and running within three hours.

For maintenance, you only need one person (a network admin) and then a backup person, just in case that person is on vacation or something.

What about the implementation team?

We handled the setup all in-house. We do have their tech support. At one point, we did get tech on the phone and were working with them. It basically came down to firmware. The one they shipped us could not downgrade its firmware to the firmware we were running on. There was no good way to make it upload the config from an older firmware. They wanted the same firmware restorations. That was kind of a pain, however, we just ended up manually going through and resetting everything, which was not too terrible.

What's my experience with pricing, setup cost, and licensing?

Cisco's APs are licensed and you need to buy them. Basically, for every AP, you have to have a license. Some of the other devices do it so that they support X amount and you can buy the licenses for zero to 20, 20 to 40, et cetera, and it's a little bit more affordable. That's kind of why I was trending towards Ruckus. They handle their licensing a little bit differently. 

Every time somebody asks "How much is a wireless access point? We need wireless in this room." Well, then you tell them the cost and mention "Oh yeah, and there's a license." It's expensive.

Users purchase each AP, and that's until the end of that product's life. If you break it down over a year, it's fairly affordable. However, nobody replaces one AP, we replace them all typically at the same time. Unless one dies or they need one expanded, as far as specific costs go, it's different for indoor and outdoor ones. It might be around $100 for a license. The internal ones are far cheaper than that. 

Which other solutions did I evaluate?

We had looked at Meraki before, however, the cost is just astronomical. We're a local government, so there's no money. The cost of Cisco wireless controllers has always been kind of clunky. I had heard a lot of good things about Aruba, and then I heard they were bought out by HP, however, it seems like it's still good. I was leaning more towards Ruckus based on just how it handles traffic and handles the guest VLANs and that it can do SSI de-scheduling. I still need to go back and do an in-depth read on the Ruckus option. I am leaning towards that one, even though it seems like it's a close tie.

I also looked at Ubiquity, however, from what I've read, their hardware is not really up to par when you hit saturation, and on certain days of the week here, we definitely have saturated APs due to the fact that we have court cases. You can go from the usual 10 people on an AP to possibly 40 plus people, all trying to check their internet over the wireless. It gets kind of crazy on those days.

What other advice do I have?

We're just a customer and an end-user.

We use the 2500 wireless controller and all the APs that go with it. 

We have Cisco switches and routers as well. We were using Cisco firewalls up until about three years ago. And then we switched to Palo Alto. As far as switching goes, still happy with their switches. They're extremely pricey, however, they last forever, and they meet a lot of government requirements that we have.

I'd recommend the solution I wouldn't hesitate to do install it if the company can afford it.

I would rate the solution at an eight out of ten for its ease of setup, ease of scalability, and robustness.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Tim Brumbaugh - PeerSpot reviewer
Solutions Architect at Golden West Technologies
Real User
Top 5
Great performance, easy to set up and simple to configure
Pros and Cons
  • "The product has some very awesome patents on their radios and their antennas and antenna patterns and how their signaling works. That's why nobody can touch them. If they go head to head with anybody."
  • "The cost could be slightly improved. It's not on the low end, and it's not in the high end. It's in that middle area, which can be a deciding factor between someone going with this solution versus another one."

What is our primary use case?

We primarily use the solution for its performance, compatibility, and general capabilities. We do a lot of schools, colleges, large civic centers, large arenas, etc. That kind of stuff. We know how to deploy this so that the clients get great client connectivity.

How has it helped my organization?

In terms of COVID, we've deployed external access points to the outside of a lot of the buildings. These are very weather-resistant, all-metal enclosures. The students have been able to do assignments and schoolwork and that kind of stuff from the parking lots of the schools. They can drive up in their car, get their assignments, or do work that they need to while they're connected to the school. It made social distancing in this way pretty seamless as everything was already set up on their laptops. Most of the schools are what they call the one-to-one initiative, where every student gets a laptop and they've been able to work through COVID from their cars in parking lots when they needed to be at the school for something. It's really benefited a lot of the schools to be able to do that.

What is most valuable?

The performance of the product is amazing.

The ease of configuration that's on offer is very good.

The product is very compatible with other solutions.

The guest onboarding is so simple. We can onboard guests really easily. Each guest that connects has a pre-shared key that they get which are all unique. We have some great control over the guest and corporate traffic. We can control how much bandwidth a guest user gets versus a corporate user, and who gets priority on there. 

Ruckus is way ahead of the game on a lot of stuff like Wi-Fi 6. They're already rolling out the second version of Wi-Fi 6, which is a huge improvement over even Wi-Fi 5. The way wireless started is you had 802.11b, 802.11a, then 802.11g and 802.11n, then 802.11ac, then AC wave to 802.11ax which is the first version of Wi-Fi 6. The next version of Wi-Fi 6 is rolling out already.

The product has some very awesome patents on their radios and their antennas and antenna patterns and how their signaling works. That's why nobody can touch them. If they go head to head with anybody. They blow Cisco and Aruba out of the water and even Mist for radio plant connectivity. On top of that, they have very good engineering. If I ever need help with engineering stuff, I can call on them. The company does a really good job, which is why we've stayed with them.

What needs improvement?

They're leaders in what they're doing. I don't know what they can do to improve what they're doing currently. 

The cost could be slightly improved. It's not on the low end, and it's not in the high end. It's in that middle area, which can be a deciding factor between someone going with this solution versus another one.

They've got a rotation or a life expectancy of about four years for the radio. Not that radio is going to die right hten. I've got some that are way older than that, that the customers are still using. However, they take them and they end the life of them at four years. Any of their wireless products are end of life by year four. Most of it's because technology has changed so much that those old videos can't do stuff that is now available for PCs to connect or phones to connect to that kind of stuff. 

What they do is they force you into a Cloud controller. We've got a couple of them. If I've got a Cloud controller there and it's on version 5.1, and I want to go to version 5.2, bdue to the fact that I need to support the new radios coming out, I can't if I have some older radios on that controller. I can't upgrade that controller to the latest software to support the new radios as I've got some end of life radios on there that go into life when I upgrade the software. They need to be able to allow us to keep some of the older products on the Cloud controllers or any of their controllers longer, and just start supporting the new controllers. They force you into an upgrade unnecessarily.

We have some customers that have just a few APs. There are some small businesses that don't want to, or don't need to upgrade their controllers and they're crushing their access points. For us to be able to work with the latest access points, we've got to upgrade our controller, however, we can't. That bites us every year. We'll have customers that have APs that are going end of life that still work fine, but we can't manage them anymore.

I know the reasoning behind it is it could be security features or it's something that the access points don't support that newer devices do. They'll support this new Wi-Fi 6 coming out, however, I can't run the same types of radios on this particular controller software anymore. That kind of puts me off a little bit, however, that's the only thing that the company has done that's made me mad.

For how long have I used the solution?

I've been using the solution for the past six years.

What do I think about the stability of the solution?

The stability of the product is rock solid. We haven't had any issues at all.

What do I think about the scalability of the solution?

The solution is extremely scalable. I can have up to three controllers with each one housing 10,000 APS. I can have a cluster of controllers controlling 30,000 different APS. I don't have anything that big. One is close to a thousand and that's the biggest I have. Still, it's nice to be able to build in more redundancy. 

How are customer service and technical support?

As a Ruckus partner, I've got access to Ruckus. I've got access to tech support, and it makes things a lot easier for the end-users and businesses I work with. If they have an issue, they can come directly to me or they can go directly to Ruckus, it doesn't matter. I'll be happy to help them. If I can't answer the question or get them fixed, then we'll get with tech support. I don't call tech support very often. Maybe once a year, if that. They make a good product and offer good training. Once you learn it, it's pretty easy to manage. 

Which solution did I use previously and why did I switch?

We used to have Cisco's products for one or two years. I don't know the last time I had to turn in an RMA for a Ruckus radio. They're a solid product.

How was the initial setup?

I've been doing implementations for a long time. If it's brand new to the system, like any system, it can be fairly complex. However, they have great documentation on their website on how to set it up. If a client needs complexity, however, they need help. That's where I come in.

I can go in and configure things securely for guest access and BYOB devices and corporate laptops with 802.1X. I have a stand-alone AP, I just got one office with one AP. I don't need it to be controlled by anything. If I've got one or two SSID, it can still be configured. It's just that you're doing it on the AP or, alternatively, they have what's called Unleashed, which is controller-less. The AP is the controller that can do up to 50 APs all controlled by one AP. If that AP was to die, it doesn't matter, that configuration is saved on all of them. 

There are several different interfaces you may run into, to be able to configure everything. However, they're all very similar in how they work and react. The full controller has much more capability than Unleashed and at least has more capability on the stand-alone. In any case, it's all well documented, and all straightforward.

In terms of deployment times, we figure for AP it's an hour and a half, so you can just figure in that as the base amount of time you need for each AP and that includes configuration and installation. Therefore, if you have 20 APs, it's about 30 hours for 25 APs and that's setting up the controller virtual, or Cloud-based, setting up the AP, the SSIDs, passwords, 802.1X., and then physically mounting them.

What was our ROI?

The solution definitely offers my clients a good ROI after they implement it.

What's my experience with pricing, setup cost, and licensing?

They don't really need to be cheaper. They're not the most expensive, and they're not the least expensive. They're right there in the middle.

What other advice do I have?

We're a reseller as well as a customer.

We're running the latest software. We deploy through a controller and we use 802.1X. There're multiple ways to deploy to customers. There's a cloud controller, for example. We typically do a virtual controller on their systems.

If a company is new to Ruckus, it's best to work with a partner. You need somebody that knows what they're doing, and knows what questions to ask so that you're getting the right information. When I go to do an implementation, I've got a list of 50 different questions. I'll ask somebody, what about this? What about this? What about this? It will help with the implementation process if someone has a complete view of what to ask for and what to do.

You get what you pay for. People will throw in Linksys, and this other stuff. If you're a business, say you're a coffee shop and you have 50 customers sitting there. You want all of them to get the same performance all the time. I want to make sure everybody gets an equal amount of time without anybody getting any interruptions.

With Linksys and Ubiquiti and all these other brands, you don't get that. When it comes to the head-to-head competition, the Ruckus far out-shines them. Ten to one, you just can't compete. When they say it's going to do something, it does it. They don't put documentation out that is misleading. If it says it'll do 1,024 clients it'll do 1,024 clients. If it says it'll do 4.3 gigabytes, it'll do 4.3 gigabytes. It's great.

Overall, I would rate the solution at a nine out of ten.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Zachary Wheeler - PeerSpot reviewer
President / CEO at Secure Solutions Center LLC
Real User
Top 10
Impressive manufacturing quality, highly durable, and very easy to deploy
Pros and Cons
  • "For me, the ease of setup and the rugged nature in harsh environments are most valuable. So, durability and ease of use have been its best features."
  • "They need to do more with their marketing. That's what's wrong with them. Nobody knows they do all this other stuff. I love the product. For an enterprise-level system, you never have to explain why you're recommending Fortinet, whereas you might have to do that if you want to use the Ubiquiti Professional or the new Netgear line, but you don't have to explain Fortinet. It has been remarkable to work with."

What is our primary use case?

We're putting together one of our more complex Fortinet environments. It involves switch-to-switch fiber connections, and it also includes the deployment of outdoor access points to power cameras, in addition to providing WiFi. There is also the deployment of a firewall, and I believe they are going to convert all level two or level one switches to level three. 

It is deployed on-prem.

How has it helped my organization?

It is enabling us to have an internet connection to remote locations on the client's property to drive security cameras with complete coverage. It is an incredibly harsh outdoor environment subject to lightning, sun, and heat. It is pretty much the worst tech environment you could ever imagine. When we opened up some of the access points in front of the client to show them, he was absolutely floored or impressed by the manufacturing quality and the durability. It had an instant customer buy and acceptance. They're a Cisco house, so the introduction of this Fortinet was our doing, and so far, it has been doing very well for someone who's new to the Fortinet family.

What is most valuable?

For me, the ease of setup and the rugged nature in harsh environments are most valuable. So, durability and ease of use have been its best features. 

What needs improvement?

They need to do more with their marketing. That's what's wrong with them. Nobody knows they do all this other stuff. I love the product. For an enterprise-level system, you never have to explain why you're recommending Fortinet, whereas you might have to do that if you want to use the Ubiquiti Professional or the new Netgear line, but you don't have to explain Fortinet. It has been remarkable to work with.

It would be nice if they had some smaller switches or hubs. They should offer two-port, three-port, or four-port devices so that you don't have to buy an eight-port switch, and you don't have to use an unmanaged element, but their product line is very complete, and I can't say enough about it.

For how long have I used the solution?

We have been working with this solution for about a year and a half, and our level of experience is growing day by day.

What do I think about the stability of the solution?

I would rate it a 10 out of 10 in terms of stability.

What do I think about the scalability of the solution?

I would rate it a 10 out of 10 in terms of scalability. We've got it in some retail establishments, such as car dealerships. We use this product a lot with a company called Verkada, which is a cloud-based camera and access control system. It just fits everywhere because of its ease of use, ease of deployment, stability, and performance.

How are customer service and support?

We always opt for 24/7/365 support, and as a result, the phones are answered quickly. We're getting the level two and level three people immediately, and their follow-up is outstanding. Fortinet has been a very good experience.

Which solution did I use previously and why did I switch?

Fortinet is our lead product, with Aruba being a close second. Both of them have been outstanding to use, and whenever they release a new product, I would like to use it. For example, I'm going to buy a FortiVoice phone system, just because I've had such great success. I'm so pleased with what we've done up to now that I want to see how much more they can do.

Everybody touts Ubiquiti and how great Ubiquiti is, but my number one thing with Ubiquiti is that I don't feel like it's a real enterprise solution. I'm sure a lot would disagree with me, but I find the interface very difficult to use. We are highly impressed with the ease of use of Fortinet. I was using some of the Ubiquiti products, and the reasons for switching were:

  • Ease of deployment
  • Physical quality in terms of what it feels like in your hand
  • 24/7/365 support with hardware replacement plans

As a reseller, we provide support for the systems that we sell, but our objective, as crazy as it sounds, is to build systems that don't fail. If and when they do, the objective is that the replacement device is on-site, a lot of times even before the client realizes that there was an issue. That's kind of impressive.

How was the initial setup?

It was super easy. I would rate it a five out of five in terms of the setup. 

The deployment for this very large Florida location is probably a day or a day and a half job, but that's only because of the number of switches and APs that we have to physically install. Getting it online takes a couple of hours.

What about the implementation team?

I'm the president of a tech company, and I'm not a tech guy. It's so simple and so intuitive that I can deploy the systems, but I've got my guys doing it. We have one or two people for its deployment and maintenance. 

There is very little on the side of maintenance. The biggest challenge is just ensuring the ISP is getting their signal to us. One of the founding principles of a company is architecture. So, whether it's the cable, the method of installation, or the location of the installation, all of these variables contribute to either a successful or a challenging environment post-deployment.

What was our ROI?

It would be in the realm that if they don't call us, it works. So, not failing in itself is ROI to us. There are a lot of MSPs who want to be engaged with the client. I don't. We consider ourselves a technology hardware reseller. I do not, by any means, position us as an MSP. Although we support the systems we sell, I don't have a room filled with guys answering the phone, and that's by design.

What's my experience with pricing, setup cost, and licensing?

Licensing costs are reasonable. There are so many different types of licenses with Fortinet, but the licensing and the 24/7/365 support are so reasonable that I automatically include it with every transaction. I never line item it without it. There are no additional costs.

What other advice do I have?

I would rate it a 10 out of 10.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Senior Manager Infrastructure at a tech services company with 1,001-5,000 employees
Real User
Competitive pricing with an easy initial setup but needs better technical support
Pros and Cons
  • "The pricing is very competitive and the feature sets are very good. It compares well against more expensive options."
  • "The support needs improvement. The official support is kind of complex. It's not that straightforward compared to Cisco and Aruba."

What is most valuable?

The configuration is straightforward.

The initial set up is easy. All solutions at this point, at a basic level, are very similar in terms of features and items of that nature.

The pricing is very competitive and the feature sets are very good. It compares well against more expensive options.

What needs improvement?

The support needs improvement. The official support is kind of complex. It's not that straightforward compared to Cisco and Aruba. Their support is probably so much better. That's one of the reasons I'm looking for an alternative solution.

You may find a lack of features compared to Cisco, or other options. For example, on Cisco or Aruba you've been able to find the Wi-Fi 6 access point for a long time now. If you have set up a new solution, you probably will look for something with Wi-Fi 6 coverage. Ubiquiti at that point didn't have it. Now they have it. I checked their website and they do have Wi-Fi 6 support. However, it's clear that they are behind on some pretty standard aspects.

If you're talking about enterprise-level coverage, you likely have many locations. Ubiquiti can handle this, however, it's a bit complicated. To compare another solution, Meraki cloud has a cloud controller. Ubiquiti has a cloud controller, however, it requires some other stuff and probably an appliance that you need to have in order to have this centralized solution control. Cisco is more straightforward and easier to manage at this point. 

If you were to compare solutions in general, Cisco is a step forward. Again, there are no big differences. It's just these minor details. However, overall, it makes a difference, depending on your requirements.

When I started to compare other solutions it was due to the fact that I do have technical issues with this product. There seems to be interference between the channels of the solutions. What I was told is that Ubiquiti can set up the channels automatically in order to avoid interference between channels, especially on 2.4 large coverage. That's fine, however, I heard that Cisco, for example, does have the option to do it automatically for APs. If there's a conflict between channels, and interferences become a big issue on your network, they will automatically adjust. That feature is not available on Ubiquiti. That is probably one of the reasons why I do have some technical issues regarding the overall experience.

What do I think about the stability of the solution?

The solution has okay stability.

How are customer service and technical support?

I've had issues with technical support.

When it came to dealing with interference, they weren't upfront about the issues caused by too many APs being set up. I didn't really get a timely response from Ubiquiti. It took too long to get into contact with them. Their worldwide support just isn't as good as, for example, Cisco.  

I'm in South America. That means, if I have an issue, I can call Cisco and have expert help in 24 hours or less. Ubiquiti doesn't have that kind of turnaround. They can't help you solve things very quickly. 

How was the initial setup?

The initial setup is not complex. It's pretty straightforward and very similar to any solution of this nature. A company shouldn't have issues implementing it.

What's my experience with pricing, setup cost, and licensing?

The relationship between the cost versus performance is probably the reason this is the best solution from a pricing perspective. It's pretty cheap and has the best features if you were to compare it to others. 

Which other solutions did I evaluate?

We haven't switched yet, however, we are looking for new options.

I have issues with interference and I'm looking for products that offer solutions to help me avoid this. I've looked at Cisco, and they seem to be able to adjust automatically if interference is detected. 

I've also looked at Aruba, and I've found that comparing the three, Cisco and Aruba are much more mature solutions.

What other advice do I have?

We are a customer and an end-user. We don't have a business relationship with the company.

I've run an internal audit about the company's Wi-Fi solution properties, all the main metrics about the solution. I was told that there was interference between the channels due to the fact that we have many floors and the floors are where the conflict comes in. Even though the channels were set up automatically by the solution, there were too many APs on the same floor, and that caused the interference to become an issue. It was not caused by the specific solution, however, the fact that their solution was not capable of fixing that automatically or doing something to let me know that that problem was being caused by too many APs density was not the best response.

I'd rate the solution seven out of ten. We've had problems with interference, however, that issue aside, the value you get in terms of features and pricing is quite good. It's not the most mature solution, however, it does offer a pretty good set of features overall.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Wireless LAN
September 2022
Get our free report covering Ubiquiti Networks, Cisco, Aruba Networks, and other competitors of Aruba Instant. Updated: September 2022.
633,952 professionals have used our research since 2012.