Aruba Wireless Reviews

It gives us centralized management for all campuses and all wireless access points. Students have guest networks, so the centralized management help us to manage all of users.

Some of the diagnostic features I'd expect to help me troubleshoot parts of the network are missing. I'd like to have diagnostic tools to pinpoint where devices are not getting good signals and why.

We've been using it for about four to five years.

We've had no issues with deployment.

We've had only minimal outages over the past 5 years thanks to the High Availability solution for the controllers and the access points. If we do have an outage on one controller, the access points can free-associate to another controller on another campus and still function properly for the students and staff. So this is a very stable solution.

We've been able to scale sufficiently for our needs.

Customer service and technical support have always been great. We've never had an issue getting support from Aruba. We've always had quick responses and very helpful solutions when we contact them.

Before Aruba, we were on individual "fat" access points, so we had to manage each one individually.

It's pretty simple. Once the master controller and the local controllers are set up, it's just a matter of syncing the configurations, so you do the configuration once on the centralized controller, and everything gets replicated to all the local controllers at each campus. Adding, removing, changing, bringing on new controllers to replace old controllers is a pretty simple process.

I think originally we were in the $30-50,000 range, with yearly maintenance costs and support for licensing, which cost $10-$15,000.

We needed a more centrally-managed solution so that you didn't have to manage each individual AP. When we sought out quotes, we looked at Aruba, Meru, Cisco, and a couple of others. Based on the features and the scalability and all the deployment solutions and everything that we needed, Aruba was the best solution for us.

Make sure you get a proper configuration. Do a proper site survey of your location to know what you need to configure and how you need to customize it to your own environment so that when you deploy your wireless, you're not popping up with any surprises from a bad signal or bad interference in certain places. Just make sure you know your area and you customize your solution around what your area provides for you.

We use the solution for corporate users and guest users who come to the company. We use it for IoT devices, like factory devices and cameras.

We have a multi-site design with Aruba. For small locations, we use Aruba Remote Access Point. We can open a VPN tunnel to the controllers, and the users can connect their servers securely. For example, we used a captive portal solution from Aruba. The guest users could log in using web portals without any tools.

We manage all wireless devices from Aruba Central. Aruba AirWave is an on-premise solution. If we have our own servers, we can use AirWave and troubleshoot wireless networks. It's a good management system. It enables easy troubleshoots and management. The solution is secure. It has all the security options.

The support should be faster.

I have been using the solution for four or five years.

The tool is stable.

The tool is scalable. We have about 3000 users.

The support was better before. Now it is not good. It should be improved.

The setup is complex for new users. Cloud deployment is easier than on-premise deployment. The deployment can be done in one to two days.

The deployment can be done in-house. We can deploy devices from the cloud for remote locations. We need not go there. Aruba has a solution for zero-touch provisioning.

The product is expensive. We need to renew the license to use the tool.

I will recommend the solution to others. Overall, I rate the product a seven out of ten.

We use it to manage a substantial number of access points for our clients, ensuring reliable and secure wireless connectivity across their properties, including indoor and outdoor spaces. It helps streamline operations, and we are actively engaged in consulting and expanding our services in this regard.

It is highly stable and user-friendly. It provides excellent performance and security through the use of available features and policies, reducing the reliance on external firewall configurations while ensuring a secure and reliable network environment.

It would be helpful if they would release training materials and updates to enhance their offerings. When it comes to switching, there can be occasional variations, such as with the cooler switches. Also, there might be technical issues with the code that could lead to variations in performance. To enhance the system, more work on integration would be beneficial.

I have been working with it for four years now.

I am highly satisfied with its stability capabilities. I would rate it nine out of ten.

It provides good scalability abilities.

Its support services are satisfactory.

The initial setup was easy.

The deployment process can vary significantly based on the number of access points and the controller. When you're dealing with a large number of access points connected to a controller, it's important to monitor the synchronization process, which can take some time. Fortunately, there are features integrated into both the Access Point and the controller to help manage this process more effectively, help streamline the deployment process, and ensure it runs smoothly. It typically takes around two to three days for changes to become fully effective in the live customer environment.

It comes with a relatively higher price tag, but it's essential to assess the value it brings to the market because it actively competes with other players in the industry and dedicates efforts to offer competitive devices.

The product is known for its high quality and reliability, fulfilling its intended purpose effectively, which positions it as a practical and worthwhile option. Overall, I would rate it ten out of ten.

We're using Aruba Wireless as a wireless access point, particularly Aruba AP-505.

We're also using Aruba Wireless for guest management purposes.

For my organization, the most critical feature of Aruba Wireless is guest management.

An area for improvement in Aruba Wireless is creating a DMZ. Without Aruba ClearPass, you need to allow guess access directly via the internet, which means you need to implement the security in between, so this is what I'd like Aruba to improve in the product.

Another area for improvement in Aruba Wireless is delivery because right now, in the COVID-19 pandemic, the product doesn't have much availability. There's a limited supply of semiconductors, so I want Ariba to increase Aruba Wireless production. The product needs to be available and delivered to customers faster.

I've been working with Aruba Wireless since 2016.

I would rate the stability of Aruba Wireless as nine out of ten.

From a scalability point of view, I don't see any challenges with scaling Aruba Wireless. After all, my organization only has one office and only needs approximately fifty APs.

Aruba Wireless has good technical support.

We used Cisco, the older technology, before using Aruba Wireless. We were not getting guest management as a feature on Cisco, while Aruba Wireless came up with guest management via Aruba ClearPass, so we started using Aruba Wireless.

The initial setup for Aruba Wireless was easy. It was so simple. My organization used it as a standalone solution.

Deploying the product took approximately six months.

We implemented Aruba Wireless through a consultant. Our experience with the consultant was good. He provided good support without the need for any intervention. The product was implemented well and working per our requirements.

The commercial department handles the Aruba Wireless license for my organization, so I cannot comment on the product's pricing.

I have experience with Aruba Wireless.

My organization is an Aruba Wireless customer.

My organization has three administrators of the product. Currently, there is no plan to increase Aruba Wireless usage.

I'd tell anyone looking to implement the product that Aruba Wireless works well in my environment. I have no complaints about it, so I can only say this.

Overall, I'd rate Aruba Wireless as eight out of ten.

The most valuable features of Aruba Wireless are the seamless feature and the concurrent user.

Aruba Wireless can improve the assigning of access points. We have times that the nearest access point is not assigned but one far away. The integration between access points could improve.

I have been using Aruba Wireless for approximately one year.

Aruba Wireless is very stable among all the other access points I have used.

The scalability of Aruba Wireless is good.

We have approximately 1,000 to 1,300 users using the solution. We plan to increase the usage of the solution. There are plans to install 150 access points in January.

We have a partner in Indonesia that we use for support that is called Agiva and they sometimes escalate issues to Aruba Wireless. I do not have direct experience with the support of Aruba Wireless.

I do not have any experience with other vendors other than Aruba Wireless.

The initial setup of Aruba Wireless is simple, including a wireless plan used. If we have instant access points and change them to computer access points, it is simple to do.

We have a license for the source mobility controller.

The price of Aruba Wireless is expensive.

I rate the price of Aruba Wireless a two out of five.

We have four people for the maintenance of the solution.

I rate Aruba Wireless a nine 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 currently have 500 access points deployed and operated by two controllers. Recently, all of the AP-125 models were replaced as part of a three year site wide upgrade, using AP-205H, AP-215, AP-225, and AP-325 models. 

Our wireless overhaul has reduced the number of wireless related help desk tickets by nearly 90%.

I work in a concrete fortress built 70 years ago. It obviously was not designed with wireless internet in mind. The software available allows me to make very specific changes to individual access points when throttling power/settings, which are critical to good working wireless signals. 

The ARM functionality does not always seem to perform how I would like. In some cases, I have had to manually assign channels to avoid channel confusion. Overall, it is a small task to worry about. 

HPE Aruba technical support is a nine out of 10. 

Quality of the product and the OS interface are a nine out 10.

The primary use we have for the product is for users' corporate mobile access.  

The most valuable feature is the fact that it can work with many devices. It supports everything that we need it to. Whatever features are required from an enterprise standard, it supports all of them. The main advantage is broad device support.  

The area that has the most room for improvement is upgrades. What we have seen many times now is that new releases tend to have bugs. Sometimes the bugs are a little bad and cause some undesirable issues. The new code in the upgrades or something leads to conflicts. I would say testing releases before making them available is one of the areas which Aruba needs to improve most with the wireless product. More comprehensive testing is required for a better, more reliable end-user experience.  

It is not necessarily testing more often, it is just for new releases. The testing they need to do is to work more closely with different environments and take notice of where issues tend to occur. They should have some idea of what environments are experiencing issues more often by now because of which companies are reporting the issues. They can make compensations for testing in those environments.  

I do not have any new features that the product requires off the top of my head. I think that more than improving the product, there are management portfolios and other peripheral things that could be better integrated. But just doing better testing is the main improvement that they need to make.  

We have been using Aruba Wireless for between seven and eight years now.  

Aruba Wireless has been a stable solution for us. Once it was set up correctly it was fine. We had some initial hiccups. We still have issues with upgrades sometimes. Except for mostly minor issues, it has been a good solution.  

Aruba Wireless is easily scaled between a lot of devices and a lot of endpoints. When we decided to use it as our solution we had planned to use it exactly for its ability to scale. We went through a massive scaling and did not have issues with devices and endpoints.  

Right now we have 30,000 users and around 45,000 devices between those users. It does not seem that there are many limitations for scaling the product's use.  

Technical support is good. The only issue we have had with them is that we often have to be referred to their engineering response team. That situation actually happens most of the time. On the other hand, we do not need to use support very often.  

So, yes, we get support for the product and we eventually get the solution we need, but most of the time it gets referred to their engineering team to get the complete solution. Overall, the support is pretty good.  

The initial setup was a little bit complex because our environment is complex. Because of that, I would say the initial setup was complex. It may not be as complex for other companies.  

It took almost a year for deployment. But there are two sides to the setup. One is the product is good and it can be configured to do what we need. But our environment was complex because it involves some legacy devices and some really advanced new devices and technologies as well. It is good that the product is able to support both of those needs.  

We have a couple of IT specialists, one architect, and a development operations engineer for deploying the updates and maintaining the solution. In total, it is around four or five people who maintain the product. Not everyone needs to be dedicated to it full-time.  

The advice that I would give to others who are looking into implementing Aruba starts with that it is a good product. It has some really good features. But the other reality is that you might need to be prepared to face some hiccups with any upgrades and with the setup.  

On a scale from one to ten where one is the worst and ten is the best, I would rate the Aruba Wireless solution as a seven-point-five out of ten. Because of the upgrade issues and the persistence of those, I would rate it a seven.