Aruba Wireless Reviews

For me, its security features are the most valuable, helping us to reduce a lot of complications. For example, there are security code issues we have to address when enterprise users bring their own iPads, iPhones, notebooks, or any mobile device, and they want to access our network. They may need to access our network resources, but there can be complications because they are our enterprise users or guests with unique user names, passwords, etc. Aruba is able to address those complications by providing the security for that network access. 

I work as an IT infrastructure manager. WiFi is in our scope of responsibilities, so we prepare the implementation projects for the general areas and for our enterprise users. 

We asked for tenders from Aruba, Cisco, and Meru Networks. At the end of the day we decided, or rather I decided, on Aruba because of its security features. We performed a lot of tests to reduce the number of certificates needed, the access point requirements, IPS features, spectrum analyses, etc. After that, we decided that Aruba would be best for us. 

We have been using it for two years and we are very, very satisfied with the features because there are no security problems. We continued using Aruba, not just with that project, but for different projects in other companies.

For other projects, we ask for tenders, and if HP wins, Aruba will also win because we will not buy separate WiFi solutions. We will buy solutions under the local area network site. We combine the solutions because we believe that if you are using wired and wireless networks, the one utilizing UNIX systems should be the deciding factor. At the same time we want a program with NOC solutions, BYOD, MDM, and ATM location services. We want all that to work together in our program designs.

Sometimes there's some small problems, but this is the nature of technology.

We've not had any issues with deployment.

In our two years of use, there haven't been any big problems.

We've had some scalability issues because of the way we're scaling our hardware base. For example, we started with 64 access points although our controller supports only 6 core access points. We've scaled incrementally, though, as we then went to 128 and then to 200, whereas our competitors start high.

Out of the box, we had 1000 access points licensed, but that amount depends on your own license. If you buy 120, you can support 120. There's no change to the control site up to 1000 licenses. Compared to Cisco in this regard, Arube is not as flexible.

The initial setup was not complex. There's a CLI, much like Cisco. Aruba's certification is also very similar to Cisco's, which is not very difficult.

I implemented it myself.

The solution's most valuable features are authentication and third-party vendor integration.

The solution's GUI for configuration could be better.

We have been using the solution for two years.

The solution is stable. I rate its stability a nine out of ten.

We have enterprise businesses as our customers for the solution. I rate its scalability an eight out of ten.

The solution's technical support is excellent.

Positive

Compared with the solution, Cisco Wireless has a more user-friendly GUI for configuration.

The solution's GUI for configuration is complicated. Thus, it is easier to implement if you have experience using it. There should be drag-and-drop features to make it more easier. I rate the process a four out of ten. It takes a month to complete.

The solution's cost is affordable. I rate its pricing a five out of ten.

The solution is stable, integrates with different platforms, and is reasonably priced. I rate it an eight out of ten.

The product can be used in all verticals. There are different kinds of use cases. Mostly, it is used in corporate settings, however, we also use solutions for distribution centers, et cetera.

We sell the solution and we do due to the fact that we think it's the best solution overall. We usually are researching other solutions also, as you have to know what you're competing against. That said, we've never been disappointed by its capabilities.

Overall, it's a very strong solution.

The solution is stable.

The scalability is great. 

The pricing could always be better.

Technical support needs work. It's hard to reach the right people you need to help you when you come face to face with issues. 

I can't say that they are missing any features at this time. There's nothing I can think of needing in the next release. 

We have been Aruba's partner for the last 16 years.

The stability is good. There are no bugs or glitches. It doesn't crash or freeze. It's very reliable. 

We've found the solution to be scalable. If a company needs to expand it, it can do so easily.

Technical support needs to be more responsive. It takes time to get to the proper person when you need help. The solution itself is better than the support on offer.

For us, it's easy to set up. I don't know if this is the case for everyone, but for us, it's easy. We have people that are certified in solutions, including Aruba. We know how to handle implementations quite effectively.

The time it takes for the deployment depends on the size, however, usually, the process is one to two weeks.

As integrators, we can implement this product for our clients. 

We'd like Aruba to lower the cost of using the solution. 

While we really like Aruba, we usually are researching other solutions also, as you have to know what you're competing against.

We sell wireless solutions. We are integrators. We also use the solution. We deal with multiple deployment versions.

If a company would like to add Aruba to their organization, they should first get a knowledgeable system integrator that knows the solution. If they do, the deployment will go well and they will be okay.

I'd rate the solution at a nine out of ten overall.

We're primarily using it for wireless users. It's actually to monitor use; we're using stand-alone wireless controllers in all our sites.

Before we used Aruba Wireless we had individual access points connected to our switches. We didn't actually have a centralized switch that could control all of our access points. Now, bringing the Aruba Wireless Controller into production, it's really giving us good visibility. All our access points are connected to one controller. Through that controller, we can actually handle each access point; we can disconnect or connect that access point, and then we can tell, or see, or allow how many users are, or should be, connected through that access point. These are the developments, or the functionalities, that wireless controllers provide for us.

The most important feature is all about the two wavelengths, the 2.4GHz and the 5GHz, and the access points which are connected to this wireless controller.

The perfect thing is that if we really want to know where a specific user is connected, it gives us the ability to see that and how that user is actually receiving. We can know the speed and their IP, their MAC address and, most of the time, how much bandwidth they're using per day. The wireless controller actually gives that functionality as well.

The other good thing is the dashboard. It tells us who is using most of the bandwidth, and how many APs are not in good range, or that do not actually have good security. It shows us which users are trying to hack or how many users are trying to use BitTorrent. So it gives us very good visibility into the user, so we know who we have or who we are providing internet or bandwidth for.

The speed could be better. I heard that Aruba is trying to shape the speed inside the wireless controller, but that has not been adopted yet. If they put some kind of mechanism inside the wireless controller for the speed such that, "Okay, this many users will have 20 by 20, 20 in the upload, 20 in the download. Just this many users. And this many users will have this type of speed or that type of speed." I think it would be very good if they actually bring that functionality inside the wireless controller.

I would also like to see stable firmware.

Every month Aruba has new firmware. I don't know if it's good or bad but it's not good in terms of production. We can't upgrade our firmware every month, especially an enterprise company, because if we upgrade our firmware based on the latest firmware that Aruba has, that firmware is not stable. They're not 100 percent sure about it.

My suggestion is, take your time, or invest in your knowledge. Bring on more engineers. Don't produce or broadcast firmware every month. Just have two or three firmware updates each year, and make them stable. Perfect. The way that Cisco does.

The amount of work that the controllers are handling is perfect. It's very good.

Tech support is pretty easy to work with, pretty fast. But when it comes to sending your logs to the Aruba guys, then it takes time. I had some crash logs the other day. I sent them and it took about three weeks for them to analyze the logs and then, in the end, they told me they really didn't know what was going on.

So the help desk, the first level of support is very good. But when it's going to the engineers to analyze logs, then it takes time.

The setup was a little bit complicated. It really depends on the person. If you really don't know and it's your first time that you are touching an Aruba device, then it takes a lot of time. You're not going to get it, if you have never actually touched an Aruba Wireless Controller. You have to have an experienced engineer with you to show you what to do: how to add an AP, how to proceed with all the other configurations. Once you have had your hands on it a couple of times, then it becomes easier.

It's not expensive. That is the reason we switched to Aruba.

Take the training at first and then implement it. Be sure to have full knowledge of your network, know how your network has been set up. And have a senior engineer or have one of the Aruba engineers so they can help you with the project that you have. Ask them how to actually implement Aruba into your network and they can advise you.

I give this solution a 10 out of 10. It's a new product, Aruba is somewhat new to the market but I think they are doing an excellent job. For a newbie type of product, it's not very easy to compete with the market, especially with the Cisco controller manager. But I think Aruba is on top, nowadays, in the market.

• Branch and campus access
• Guest and employee access
• Device onboarding and device access
• Guests are divided into groups. 

• Providing WiFi access to employees and guests.
• Traffic segregation
• WiFi roaming
• Digital branch 

• Superior WiFi access and RF management
• WiFi security via WiFi Firewall 
• Access control
• Integrations with other systems

• Needs integrated wired, which is not traditional HPE.
• The new 8400 failed at Lab, plus its integration with Aruba Central. 
• Needs a good enterprise story, including branches and campuses.

We are using Aruba Instant in four remote branch offices. We chose this solution at the time because of its controllerless feature and easy setup.

It provided an easy WiFi solution for our branch offices to deploy. We could usually have them up and running from out-of-the-box in about 10 minutes.

The controllerless feature. It will randomly pick one of the APs to be the designated master. If that access point fails, the role is moved to another AP. This saves a lot on management and infrastructure costs.

There is plenty of room for improvement. Reliability of a flawless upgrade after the 4.x releases is rare. There is a lot of manual intervention required lately due to random bugs. If you have a mix of APs using different firmware, it takes nothing short but an act of god to upgrade successfully. 

The product’s performance got worse with newer releases as well. It seems like they are adding more frivolous features and sacrificing stability and speed. The latest design of their APs removes the console port and requires purchasing an expensive proprietary cable just to access the console.

Occasionally, it needed to be rebooted. I used to have issues with DHCP. It is extremely buggy and difficult to upgrade with different firmware versions/models.

I do not know what the maximum number of APs in a cluster can be (for the Instant series), but I never seemed to hit a limit. At one site, we had 12 clustered together.

It seemed to be good when we needed it. This was before HPE purchased them. I have not had a need to contact support since then.

The other way around, we have switched away from Aruba to Ruckus. Aruba’s poor performance and random upgrade issues caused too much time consuming maintenance and troubleshooting. Ruckus Unleashed has been flawless; performance almost doubled, and it is far easier to configure.

The initial setup was very simple. There were some settings which were confusing and unlabeled when trying to use the online help with the newer firmware.

Trial different solutions and compare pricing to how well they perform, their stability, how easy it is to maintain, etc.

At the time when we first started using them, we did not evaluate other options. They seemed to be only ones back then who could cluster APs without requiring a separate controller.

Perform a site survey and get a model that supports the latest AC technology.

At first, the product was a solid 10. As time went on, and newer firmware was released, the product has dropped significantly to maybe a four or five rating out of 10 due to various bugs and design issues. We no longer use Aruba for any new sites and are slowly phasing them out from our locations with a different controllerless product that has drastically increased reliability and performance.

I have found the most valuable features are the new Wi-Fi six technology and it also integrates with triple-A solutions. It has good bandwidth and virtual control.

I would like to see the management improve.

I have been using Aruba Wireless for the past two to three years.

The stability is excellent and ranks a nine on a scale of one to ten.

The scalability is very high with Aruba Wireless.

Technical support is very helpful and response time is good.

Positive

I have used all three solutions Aruba Wireless, Cisco, and Ruckus.

The initial setup is straightforward and easy to set up. Simply plug and play and it will automatically block calls. You can change it every Friday or by favorites.

The setup is generally in-house and we support it.

When you look at the price it is a higher price than Cisco.

I have used all three and Cisco is more complicated than Aruba Wireless.

I would rate Aruba Wireless an eight on a scale of one to ten.