What is our primary use case?
The Aruba switch is supporting a doctor's office, so it's an on-premise switch. These particular switches provide the fundamental network for the entire office, including power over ethernet for the security cameras and wireless access points. The solution also provides network switching between databases and clients. I manage the switches using the Aruba Central public cloud.
How has it helped my organization?
Aruba gives me greater network visibility compared to an unmanaged solution. I mostly use unmanaged switches at other locations and offices.
What is most valuable?
I like the Aruba Central platform. It makes a lot of sense. The switches have a lot of great capabilities. Central can lockdown VLANs and control the apps and protocols.
There are several built-in security features that I'm not utilizing. However, those capabilities are part of the reason I'm using enterprise switches in a small office. I like knowing that I can do these things when necessary.
What needs improvement?
There are some growing pains with Aruba Central. When you first launch the wireless access points or switches, a lot of updates are needed to get Aruba Central ready, especially on the access points, so the initial deployment time could improve.
I would hope that I could just turn it on and leave the updates until later on. The switches themselves probably did okay. I'm primarily referring to the wireless access points. There was a lot of back and forth before everything was in sync. It took hours.
I can't think of any missing features, but it would be nice if there were a free version of Aruba Central for my small business clients that doesn't have as many features.
For how long have I used the solution?
I got one switch a while back and was using it in a lab situation to play around with it a little bit. I wasn't utilizing it a whole lot. It was more like, "Hey, how do you configure this? How does it work?" In the last couple of weeks, I added a second 6200 S switch and threw it into an actual production environment where it's being utilized.
What do I think about the scalability of the solution?
The scalability is fine. I've got two 6200 24-port switches, so 48 ports total. I Aruba switches are capable of putting trunk groups in between. It's a chiropractic office, so we've got 32 network tables all plugged in between servers and all of the devices, and then there are all the computers hanging on the walls and stuff like that.
However, in reality, it's typically only four people working at the office at any given time, but they run around from room to room using x-rays, computers, and all that other stuff, so there are a lot of different devices. In total, there are 32 ethernet cables plugged into these two switches.
Some people define a user as a person typing on the keyboard, but In a chiropractic office, you have customers who walk into the adjusting room and scan their little cards. Meanwhile, the doctor kind of walks from room to room. It's really only one doctor.
We'll be bringing additional computers online over the next couple of years as they ramp up that office, so there will be increased utilization of the switches even inside that office. I will also be adding switches for each of my clients. I mean as I'm going in and taking over managed service provider relationships with these clients, I'll be looking at putting those same switches, so I have complete visibility.
How are customer service and support?
I rate Aruba support six out of 10. Like many vendors, Aruba is dealing with staffing shortages or other things. Once you get somebody on the line, they're usually pretty good. It's just a matter of getting to the correct person and the time it takes to respond.
I'm not trying to bash Aruba because they're not the only ones having this problem with tiered support. It's crucial to learn the equipment, so you can hopefully do most of the maintenance and troubleshooting yourself.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
My other clients have unmanaged Netgear switches, but it's apples to oranges. They may be switches, but they're not in the same class. It's a home network switch versus an enterprise network switch.
How was the initial setup?
Deploying the switches itself wasn't that complex. You can make it complex depending on what you want to do. You can implement VLANs and do all sorts of wonderful things, but for this particular implementation, I didn't really need that level of complexity.
It took about an hour to take the switches out of the box and onboard the devices on Aruba Central. They work out of the box even without Aruba Central. You can take them out, turn them on, plug them in, and they will function as a basic unmanaged switch. There's not a whole lot that you have to do for it.
What about the implementation team?
I do all of my own stuff. I'm a solo managed service provider.
What was our ROI?
The return on investment for me in these switches will come when we start facing network challenges. Some of the applications at this doctor's office rely on old file-based databases. When they start having problems with the application, and the vendor starts saying that's a network problem, that's when I'll get my real return on investment.
I can pull up the Aruba Central platform and say, "Nope, it's not a network problem, and here's why. You're getting no gig speed. There are no errors on any of the ports or failed packets." Having all that visibility is where the true return on investment is going to come. It's preparing for those types of debates. I'm tired of people blaming the networks. It may be. It could be a configuration or something else, but it's something else most of the time.
What's my experience with pricing, setup cost, and licensing?
I am paying for the hardware and Aruba Central licenses, but I would like a version of Aruba Central to come out with a light version with a few features turned off. Ubiquiti and other vendors have free tools.
I believe they're looking at that, but it's not out yet. I hope they will release that to make it competitive because I'm using an enterprise-class switch for small businesses. We're looking for some of those capabilities, but not all of them.
Aruba has its Soho class switches, which are instant-on platforms. However, with the instant-on platform, you need to manage everything with individual clouds instead of bringing all of them under one console.
There's an annual license fee for the Aruba Central cloud management platform for each Aruba device. You don't need licenses for the hardware and other support, but if you don't pay for the Aruba Central license, you will not get firmware updates or technical support. You have to have those at least for probably several years.
When you reach a point where you're managing 100-150 devices in a small business, you suddenly need multiple layers of switches, and then you have to get into campus networks, trunk groups, VLANs, etc. Then, you need segmentation between different levels.
You have to utilize those additional capabilities and features more than you would for a dozen or so computers. You typically aren't going to create a bunch of VLANs, trunk groups, and multiple switches for a dozen computers. It doesn't make sense.
I think under 250 people would technically be classified as a small business. However, when I say "small business," I mean 10-20 people physically working at a building. Still, the price is reasonable. I'd rate Aruba eight out of 10 for affordability.
As a managed service provider, I also have access to discounts that help me manage costs better. As I own all the switches, so I keep adding people to the switches I own. Aruba has been good about providing a managed service provider discount to make it competitive. If they didn't, it would be kind of hard to justify spending $4,000 on these switches for a tiny business like a doctor's office.
Which other solutions did I evaluate?
I looked at Ubiquiti, Cisco, and some other solutions, but I have a friend who works for Aruba. I opted to go with Aruba after chatting with him about where it's positioned in the market. Aruba seems to be a leader, especially in wireless access points and some of the newer capabilities and features.
I was looking for network switches that could be managed with the same wireless access points in one console, so that gave it to me with Aruba. Some people are fine with having one console for switches and another for wireless access points. As a solo managed service provider, I'm all about simplicity, so I was really looking for one solution that would handle both.
What other advice do I have?
I rate Aruba Switches nine out of 10. If you're deploying these types of switches, I encourage people to utilize some type of cloud-based management console. If you don't use Aruba, make sure whatever you use has cloud management to give you visibility into what's going on in terms of configuration, errors, etc.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner