If you were talking to someone whose organization is considering Aruba Switches, what would you say?
How would you rate it and why? Any other tips or advice?
We use both the cloud and on-premises deployment models. I would recommend the solution, especially if you are on a tight budget and are looking for a no-nonsense product. I'd rate the solution seven out of ten.
We are system integrators and we propose solutions for our clients. From what I read in Gartner Magic Quadrant, Aruba Switches rank highly. It's a good solution. I would rate this solution an eight out of ten.
For small businesses, it is the best on the market right now. The recognition is still new. Aruba is easy to expand and easy to configure. I would recommend Aruba Switches. I would rate this solution a nine out of ten.
I will rate this solution an eight out of ten at least. I would like to see some additional features to be included in the next release, and I would like more data center functionality for our data center people.
We used and configured Tricom Switches. HP merged with Tricom and the company after that Aruba merged with HP. The switch became very different, it is good and has a different configuration. We have had a few problems in our company, we have had some conflicts in the configuration. Aruba was the first company to introduce access points, as far back as ten years ago. It's a good product, but it's not equal to Cisco. It's better. I compare it with Cisco and Aruba is a better switch. With Cisco, you buy the name, history, and global branding. If an engineer or any company ask me about network solutions, I recommend Aruba. I have some concerns because not many engineers write on the command line in Aruba. Not many engineers know the solution, unlike Cisco, which is well known in the education industry and on the market. If you can configure the Aruba Switch for the very first time without any issues, then you are a very good engineer, you know the solution. Aruba Access points, controller, and performance are the best! I would rate this solution a ten out of ten.
I received training on this solution from HP, here in Egypt. I strongly recommend Aruba Switches with Aruba products for compatibility. If you use Cisco or other solutions, it may cause some issues with the stability of the environment. I would rate this solution an eight out of ten.
We've been implementing, with the help of Aruba, with zero-touch provisioning in a newly opened hospital. Roughly 450 switches have been put into operation using zero-touch provisioning (ZTP). It was challenging; even Aruba probably hadn't done such a large scale project before using ZTP. In terms of advice, I'd say if you are entering the next stage of switch hardware, of network hardware, just have a look at Aruba. It's really, really helpful having an open API to use Python or other script languages to modify configurations and to automate exchange of state changes with neighbouring structures. We try to keep as close as possible to standards. There are some areas where standards aren't available, for instance stacking of network Access switches, whre no vendor-independent standards is existing yet. So look at the whole package including the switch hardware, the licenses, the license for management and bear in mind the transceivers. When using Aruba switches, stick with the automation tools, don't let yourself be seduced into going back to manual configuration. I'd rate the solution nine out of ten. They would be perfect, but there's a noise once they are on under heavy load in a warm environment. It might be the case that they are not usable for installations where the loudness damping between the installation room and office is not sufficient.
I would recommend this product. I would rate this product a seven out of ten.
We prefer Ruckus solutions over Aruba, whether they are wired or wireless. I would rate this solution a seven out of ten.
My advice to someone considering this solution is to play it out before and choose whoever has the better solution. I would rate it an eight out of ten. Not a ten out of ten because there were some major issues like configuration conflicts and by the time we got to solve them, it was a bit of a nightmare until we got it up and running. But there will always be some teething problems. There were problems while implementing until we sorted things out and until it started stabilizing itself. It was either a question of the switch temporarily disconnecting from the internet so it couldn't connect to Aruba Central for the configuration. You can do a configuration but it is accepted as a configuration and it doesn't tell you, for example, what a particular error or something like that is.