Aruba Wireless Reviews

Integrated firewall, integrated WIDS/WIPS on the controllers and the ability to tunnel LAN traffic from the switches through the controllers to set consistent 802.1x and access controls that are consistent across both wired and wireless LANs.

It improves security by helping us to centralize access controls and dot1x and set common policy across both wired and wireless LANs without having to install additional components.

The controllers used to include heat map functionality. This was removed in a recent release. To get this functionality now, you need to be using Airwave (AWMS), which adds additional cost. On the other hand, Airwave can be used to manage a multi-vendor environment, so there may be some other benefits to having it deployed, but it would be nice to have the heat map back in the controller.

I've been using it for five years.

No issues encountered.

No issues encountered.

No issues encountered.

It's excellent.

It's excellent.

Default settings are sufficient to get a functioning wireless network up and running fairly easily. Complexity increases add vLANs, security policy, dot1x, redundancy, etc.

At my previous employer we had a relatively large wireless installation so we worked with a vendor team. The network at my current employer is small enough that I could handle it myself.

Licensing has improved. In the past all redundant controllers required licenses for all the access points. They've not implemented a centralized licensing model so that you only need to license your access points once.

We evaluated Cisco. Cisco's solution, at the time, required additional components to provide the same functionality. For example you'd need external firewalls, IDS/IPS, and authentication servers. Aruba controllers had all this built in. I haven't looked at Cisco's current offerings, so this may not still be the case.

I'd recommend you do the training.

I have a small office with about five APs. It has a good central management system to help manage my wireless devices, just to ensure that everything is working correctly.

It makes things easier because it's SD-WAN. With the central management system, I'm able to access each device. I can configure one device and then it provisions all the other devices with the same configuration, rather than my having to configure them one by one.

The central management system. It's called Aruba Central, which allows you to manage the APs, the switch, and the controllers, etc.

The management system would be better if it were more polished, if it had a better interface like, for example, Meraki.

Scalability is pretty good. I believe they recommend having up to 50 APs per cluster, but it can scale even more than that. I don't really need that in particular, although it's an enterprise-standard product. The throughput is pretty good.

I haven't used technical support as of yet.

I used to use Meraki but with Meraki, if you stop paying for the licenses, you basically don't own the device. Once you stop paying for the licensing, the device is pretty much dead.

The initial setup was pretty much straightforward to be honest. You only configure one AP and when you plug the other ones into the network, it recognizes that that AP is the master and gets the configuration off that.

I did look at Ubiquiti because the price point was cheap. But after looking further into it, the main reason I chose Aruba was because they have a lifetime warranty on their APs.

My advice would depend on the needs. It depends on what size of business you have and what you are looking to accomplish. In general, I'd recommend Aruba Wireless. 

The only other thing I would let you know is that, if you want a centralized management system that is able to manage all your networking devices such as the wireless, the switch, the routers, and the firewall, then Aruba may not be the one, because Aruba doesn't do firewalls. For example, with Meraki, you can have a full Meraki network with the switches, routers, firewall, APs, all managed on one central network. With Aruba, if you have a firewall, you'd have to use a separate management system to manage that.

The most important criteria when selecting a vendor would be

• support
• durability of the device
• brand reputation
• ease of use.

I would rate Aruba Wireless at about eight out of 10. I haven't had any issues with it to date, and it's a pretty robust product. The reason I won't give it higher than that is because of the GUI. They need to make it more polished like Meraki's. But other than that, I've been pretty happy with it and I like all the additional features there.

We use Aruba wireless APs to provide wireless services for a private high school campus which is located on a 60-acre campus in Rockford, IL, with an enrollment of nearly 900 students.

Increased productivity with mobile devices has improved by expanding wireless coverage throughout the building. While our building has been covered by the Aruba APs throughout the years, we are now replacing older APs to increase bandwidth to support an increase in the number of users with dedicated devices. Nowadays, the end-user devices require faster bandwidth from APs, and the newest APs obviously support faster standards and improved bandwidth connectivity.

We appreciate that the Instant models do not require a dedicated "controller" to manage the APs. This cost saving allowed us to purchase more APs in our initial order. We started out small and slowly added more APs as each annual budget allowed. We still have the possibility of adding a dedicated controller which affords us more options, but at this time we haven't needed it.

The web interface to manage the APs is intuitive and makes managing the system easy. 

Firmware updates are quick and do not require much downtime.

Customer service really needs to be improved. If the customer support was better, I would recommend it to others more than I do now. I say that even though we are upgrading to newer units this summer.

Stability of wireless services provided by the Aruba APs hasn't been an issue. If there have been any issues, they've been minor and have been resolved by firmware updates.

No issues with scalability. Scalability has been one of the easiest aspects of the Aruba Instant product line. As long as the models are compatible, you can simply connect it to your network and it will learn the settings from the other APs on the network and join the AP network. This is one of the best features of the Aruba Wireless Instant product line, besides the fact that you do not need a dedicated "controller."

The first level of technical support is frustrating, and I stated that technical support was the one area where Aruba Wireless needs improvement. Higher levels of support are better. Considering that you have to pay yearly for support, I expect a higher level of support. On a scale of one to 10, I'd give their first level of support a four. They have to improve.

We did for a very brief time, it was a consumer "off-the-shelf" product to get us by in strategic locations in our building. It was not intended to be a long-term deployment.

Initial setup was straightforward. We followed the very basic instructions (connect to the new WiFi network, then go to a website, make some simple changes, save, reboot, done); updated the firmware, and we were on our way.

Pricing is competitive. Licensing is needed to maintain access to the latest firmware, which wasn't made clear originally when we started with Arbua (or things changed, I'm not sure which). I would just say, make sure you budget for it. In addition to the licensing, you do get "support," for what its worth.

No, we received guidance from others in our community and stuck with Aruba.

We currently utilize the Aruba Instant 205 and older Instant 105 models. I would give both models a rating of an eight out of 10. We will be upgrading this summer to move our Instant 105 models out of circulation and will be implementing three new Aruba product lines.

Make sure you get the maintenance licensing, don't skimp on the models. If you can buy a more powerful unit, get the more powerful unit, it will be supported longer and offer a longer ROI.

I sold both the Aruba hardware and software, primarily the IAP 100, 200 and 300 series, along with AirWave as well as ClearPass to SMB clients primarily with less than 500 employees. At the time, I worked for PGH Networks, a local MSP and Aruba certified partner.

I used this solution for four years from 2013 to 2017.

Aruba provided a great product offer for clients of all sizes and scopes. Everyone needs WiFi. Aruba allowed for the detailed control and management of an entire WiFi network from a single screen backed by a support team with local SEs who work with business partners to ensure the product's success.

• Instant access points and ClearPass
• IAPs could be deployed without a controller, solving sticky clients by peeling away users crowding one AP and can have settings pushed from a master AP.
• ClearPass and AirWave gave highly accurate detailed reports of who used which applications when and the ability to throttle users if they were bogging down the network with superfluous activity.

Larger network for Aruba users and partners. I would have liked to see more manufacturer driven events and outings to drive brand recognition and familiarity.

I use Aruba Wireless to manage and monitor mobile users.

It has helped in making deployments easier despite the configuration's complexity.

I have found the Access Point (AP) group profile feature extremely useful. It makes deployments look easy.

• They should simplify the configuration flow. 
• Additional detailed reporting for client traffic would be a great addition.

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 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.