What is our primary use case?
Aruba Networks Wireless WAN is used for wireless network conductivity.
What is most valuable?
The most valuable feature of Aruba Networks Wireless WAN is that it is easy to configure. Additionally, with the same configuration with Cisco and Ruckus, we can receive 55 to 60 percent more out of Aruba Networks Wireless WAN.
If you're unwilling to purchase or spend money on a controller, you can opt for a virtual console base solution that offers up to 120 access points. This approach is highly cost-effective, as you won't have to raise your budget, and it's easy to set up.
What needs improvement?
When it comes to configuring rules for file security tests, any issues that arise can be referred to as "glitches". Despite the extensive configurations required, the process itself is not overly complicated.
For how long have I used the solution?
I have been using Aruba Networks Wireless WAN for approximately three years.
How are customer service and support?
When I open a support ticket with Aruba, it goes to their team in Bangalore, India. While I cannot say they are the worst, I am not perfectly happy with their support. Recently, I closed a ticket with them that took over seven days to resolve a simple issue of adding a MAC address to the control. This slow support process can be a problem, especially if the customer has a live network. However, I have noticed that their CCAs are now more professional than they were three years ago. Sometimes, Aruba avoids alerting by opening tickets after their official time, which goes to the European team. Similarly, we do the same for Cisco to reach their European team for faster and more knowledgeable support. Currently, Aruba's support is not as scalable as Cisco or Roper, although Roper's team is also in Bangalore.
As an on-site engineer, I sometimes open support tickets when I suspect a configuration mistake, but it can be confusing when the supporting engineer has less knowledge than me. It is also challenging to escalate the ticket in front of the customer I am installing for, so we have to maneuver a little to reach another engineer. Overall, Aruba's support is not as frustrating as before, although sometimes I feel the need to change the engineer.
Which solution did I use previously and why did I switch?
I have used many other network solutions, such as Cisco and Ruckus.
Ruckus stands out in its ability to provide connectivity to users through its access points even when the controller is unavailable or cannot be reached. In contrast, if the controller goes down with Aruba or Cisco, the entire infrastructure will be affected, unless you switch to Mobility-based or virtual-based software.
One disadvantage of Aruba is their access point bracket, which is not standardized across all their devices, such as Cisco's brackets. This makes it difficult to identify and mount access points in different locations, as they may require different types of brackets based on the mounting method and physical location. Additionally, Aruba's console cable is not standardized across all models, unlike Cisco's console cable which can be used for switches, access points, and RJ4 devices. Furthermore, Aruba's console cable is not included in the box, which can make it challenging to access and control an access point through the serial port without having to find and purchase the specific cable required. In contrast, Cisco has a standardized console cable that can be used for all their devices.
How was the initial setup?
The initial setup of Aruba Networks Wireless WAN is simple.
To deploy Aruba Networks Wireless WAN, we use various tools for server setup and generating heat maps, typically employing models 505 and 515. The 505 model is cost-effective yet powerful, supporting fixed Wi-Fi and over 100 concurrent users as well as handling 100 voice clients. Once we generate the heat maps and present the external version, we include customer pricing and other details for approval. Upon approval, we proceed with the deployment.
I create heat maps, which are becoming increasingly in demand these days. I use multiple models of devices from Cisco, Ruckus, and Aruba depending on the physical location. For example, if it's a warehouse with high ceilings, I use the Aruba 515, while for office areas, I use the 505. For outdoor locations, I use the 565 or 575. However, I haven't utilized Nest connectivity with any Cisco, Aruba, or Ruckus routers yet.
What's my experience with pricing, setup cost, and licensing?
The price of Aruba Networks Wireless WAN is less expensive than Ruckus and Cisco.
What other advice do I have?
The maintenance of the solution is not difficult, I have been doing it for a long time.
Aruba's controller is an integrated system, whereas Cisco has separate devices and services that are not too integrated. Ruckus also has separate devices and services. When customers buy Cisco or Ruckus devices, they are buying all the devices together to get the best service. However, after the sale, nobody calls for support or assistance.
In the case of Aruba, if the controller goes down, the access points can be converted to a version of the software that allows them to work with a virtual controller. However, there are physical issues with Aruba, such as confusion with the access point bracket and console cable. Even if there are multiple console types, it would be fine as long as they are provided in the box.
I prefer Ruckus solutions, but it is expensive for customers.
I rate Aruba Networks Wireless WAN a seven out of ten.