Aruba Wireless Reviews

I was able to provide Aruba Wireless to financial, Telco, and hospitality industries.

If you're looking into a wireless solution, more and more people now are using Aruba Wireless. There are two key reasons why: in a developing country, many of the companies look at the cost and quality of a solution. Cost-wise, Aruba Wireless is very attractive here in the Sri Lankan market. The other key reason is Aruba Wireless provides their key product portal and a limited lifetime warranty. Other providers do not provide that level of warranty. These are the reasons why a customer would choose to purchase Aruba products than Cisco, or any other access point or wireless solution.

The key feature of this solution is the value for money. If customers can get a good quality product at a very competitive price, plus a limited lifetime warranty, then this gives very high value to the customer, which is what you can get from Aruba Wireless.

Aruba Wireless is able to provide value addition, apart from their product features.

This solution is user-friendly and their technical support team provides very good support.

An area for improvement I found in this solution is the configuration. Though it's currently an improved version, it could still be made easier, so technical people could benefit from being able to configure Aruba Wireless within a quicker amount of time.

I'm a specialist and I've been in this industry for 22 years, and I've been dealing with Aruba Wireless for over 10 years. I've worked with it within the last 12 months.

Aruba Wireless is a stable product.

Aruba Wireless is scalable. We have different product segments and we educate different customer requirements and industries. Because of COVID, all industries are facing a lot of challenges, but we find this product scalable.

We have our pre-sales team with us in-house, but we do have two technical support people distributed here locally. We always communicate with them. They share their product knowledge, experiences, and user case studies, to help us improve. We also share our experiences with them to also help them improve. On a scale of one to five, I'm giving the technical support team a four. They provide very good product support.

The initial setup of Aruba Wireless is not complicated. In the past, it was complicated, e.g. We needed experienced technical people to do the configuration and the initial setup. Nowadays, even basic technical people can do it.

It has improved, but what we are expecting is that when new technologies arise, along with the new technologies, the configuration should be simplified.

The cost for Aruba Wireless is good. It's attractive.

I evaluated Cisco Wireless.

Our company's role is system integrator. We are involved with products and solutions which we provide to the end customers. The products we provide vary, because it would depend on the requirement and customer requirement levels. It would also depend on the current pricing of the products, e.g. this is because we provide different vendor products, not just Aruba. We also provide Cisco, Maracas, and the entire product spectrum that we provide to the customers.

We provide the latest version of this product to our customers, because with the latest version, the benefit to the customers is that they can get the maximum usage of the product lifetime.

Other than the product features, our customers value our onsite support, onsite feedback, clarifications, and installations. We are able to quickly sort out the issues experienced by our customers.

For people who are not currently using Aruba Wireless, I would tell them to look into the Aruba product range and try it out for themselves. They'll find out that these are Amazing products with very good product support.

I'm rating Aruba Wireless an eight out ten, because no products could reach the perfect score of ten. Technology is fast-changing, so today's technology won't be tomorrow's technology. There's no technological vendor who could be ranked a ten, so my rating for this product is an eight.

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.

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.

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.

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

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.

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.

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.

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.

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

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.

Aruba Wireless is a little bit complex to use and operate. So, it can be an area for improvement.

I have been using Aruba Wireless for three to four years. Also, I don't remember the version of the solution I am using. I am a customer of the solution.

The product has been pretty stable.

The product is scalable. Around 150 people in my company are using the solution. We need only one administrator for the solution.

I haven't faced any problems with customer support.

Regarding the deployment process, it keeps showing updates.

A third party did the implementation. I'm not familiar with the setting. So, I got help from a consultant.

We have some licenses for the solution, and we need not renew licenses. But we need to pay a hundred thousand if you want to renew our subscription and renew the hardware. But if we switched to another solution like Ruckus, I think maybe it is just a similar amount even if we don't have the license. So we are considering this, but have not reached a decision yet. Also, we need to make additional payments for support.

Based on our evaluations, we are considering Ruckus and Ubiquiti over Aruba since Ruckus' and Ubiquiti's functions and settings are okay, making them easy to use.

Aruba Wireless will phase out. We are actually phasing out and looking at other solutions. We are switching because it's a bit expensive, so we are looking for a cheaper solution.

Because of the price and ease of use, I rate the overall solution a seven out of ten.

We primarily use the solution for access points. 

The solution is very complete. 

The portal has been very helpful for us. 

It's easy to set up the solution. 

We have found the product to be stable. 

It's scalable. 

They need to increase the number of routers on the controller. The VSSIP needs to have at least 25 access points. I just need them to increase the access points without the controller.

Other than that, it has everything we need, and we do not need any new features. 

The downside is right now there is a shortage of hardware. It's hard to acquire switches and access points. 

I started using the solution one year ago.

The stability has been good. There are no bugs or glitches. It doesn't crash or freeze. 

The solution is scalable. 

We have ten people using the solution right now. 

I've never called technical support. I haven't needed any assistance so far. 

I've also used Juniper.

The product has been very easy to set up. It's straightforward to implement. It did not become overly complex. Under ten access points only takes about five minutes to set up. 

We only need one person to manage the solution. 

It is free to use. It is open source. We do not have to pay for a license. 

We're an Aruba partner. 

We are using version 11. In 2022, it might be now version 12. 

I'd rate the solution eight out of ten. 

Aruba Wireless could improve the interface, it does not have a smart web interface. Other solutions have smart web interfaces, such as Cisco Meraki.

I have been using Aruba Wireless for approximately six years.

Aruba Wireless is stable.

Aruba Wireless is scalable for the needs of my customers. Some of my customers have approximately 1,500 users using the solution and it works well.

The price of Aruba Wireless is reasonable.

I rate Aruba Wireless a seven out of ten.

I've been a consultant for six years.

Aruba is easier than Juniper.

The stability and management could be improved.

I have been working with Aruba Wireless for five years.

We are currently working with Aruba Wireless but will be changing to Juniper later this year.

When it comes to stability, Cisco is number one. Aruba and Juniper are similar.

Aruba Wireless is a scalable solution.

Technical support is good.

I have been working with Juniper WLC Series for one year. We plan to implement Juniper next month.

The initial setup is very easy.

The pricing is fine.

Cisco is more expensive than Aruba or Juniper.

Aruba has pricing for a Virtual license with a VLAN package.

We decided to change to Juniper because it looked right, and because of the easy management.

I would rate Aruba Wireless a nine out of ten.

We are part of a conglomerate on the island. We provide this solution to all our different divisions, including the shopping malls. We are the technology division of the group. So, we've been assisting the group in their implementation across sectors.

I like the analytics feature.

The price could be better. In the next release, I would like to have more analytics features.

We have been using Aruba Wireless for the past five years.

Aruba Wireless is a stable solution.

Scalability depends on the model.

Our in-house team did the implementation.

The price could be better. Competitors offer more features for a similar cost.

On a scale from one to ten, I would give Aruba Wireless a six.

I rated Aruba Wireless six because the analytics part seems to depend on third-party software applications and because of their pricing.

The feature I found most valuable to customers in Aruba Wireless is not a technical feature. It's more of its image, trademark, or brand as the product is very well-known in the market, and that's a good point to offer to customers.

My customers just ask about the basic features of the product, and usually, when asking about Aruba products, customers don't pay too much attention to any specific feature as long as the product is solid and sure, and that you can change or modify it, as what you can get from Aruba Wireless.

One area for improvement in Aruba Wireless is its dashboard or interface because in some cases, it's not as easy to use as it should be, but overall, it's okay.

Pricing for the product is also on the higher side.

Another area for improvement in Aruba Wireless is technical support because it's hard to reach when issues arise and the speed of answer could be faster.

Other areas for improvement in the product include integration and configuration.

We've used Aruba Wireless within the last twelve months for some of our customers. We act as sellers and integrators of Aruba Wireless. We don't use the product, but our customers use it if needed and if it is a requisite for our customers. We've been dealing with Aruba Wireless for two years now.

Aruba Wireless is a stable product. I didn't notice any problems with its stability.

Aruba Wireless, in terms of scalability, is okay.

The technical support for Aruba Wireless needs improvement in terms of providing better support and being more reachable when problems appear. Support also needs to improve its speed in answering customer issues.

In terms of setting up Aruba Wireless, if everything goes well, usually there's no problem, but sometimes if you need something specific, it becomes very tricky, particularly in terms of finding the right support for your setup issue. It's not easy. As for how long the deployment of Aruba Wireless takes, it didn't take too much time, though I can't give an exact timeframe.

In terms of pricing, the pricing for Aruba Wireless is not bad for large-sized companies, but for medium-sized companies, it's on the higher end, but because Aruba has a good company image, medium-sized companies still go with Aruba Wireless.

My advice to others looking into using Aruba Wireless for business is that Aruba is a well-known brand. When you buy the product, you should know what you're purchasing. As long as you have all the information you need before the purchase, you have complete knowledge of Aruba Wireless, and you know what to expect from the product and what to do with the product, then go for it.

I would rate Aruba Wireless eight out of ten, overall. I only give a rating of ten when everything goes okay, and that's almost impossible. There could be room for improvement in the pricing, and in any business relationship, there's always an issue that could arise, so it's very rare for me to give a ten out of ten to any product or company.

My company has a business relationship with Aruba Wireless as an integrator.