Aruba Wireless Review
Allowed us to have one controller at our central location and still provide wireless to our outlying clinics.


Valuable Features

The main reason I chose to implement the HP WLC was due to the limitations of our previous Sonicwall WLC not being able to have layer three provisioning. I would say that feature is the most valuable.

Improvements to My Organization

With our old wireless network, we had to put controllers at every location to have wireless access. This product allowed us to have one controller at our central location and still provide wireless to our outlying clinics.

Room for Improvement

The user interface on the product isn’t terribly intuitive in some areas, especially when setting up VSC’s.

Use of Solution

I've been using HP MSM 720 Mobility Controller and 40 HP since April 2014, so approximately 10 months.

Deployment Issues

I experienced a few issues while deploying the controller. Getting the product to work correctly with a back end RADIUS server proved to be a bit of a task and the lack of documentation didn’t help either.

Stability Issues

Stability wise the product has been fairly rock solid. I can’t think of any time I have had to even reboot it since I implemented it.

Scalability Issues

The particular model (MSM 720) doesn’t provide much in terms of scalability. It only allows for 40 Access Points which my company has about that number.

Customer Service and Technical Support

Customer Service:

Customer service on the phone I would rate fairly poorly. On more than one occasion I could not understand the agent or would get disconnected, however, online customer service is much better.

Technical Support:

I have only used the HP forums for technical support and it has a pretty good following and a lot of knowledgeable users.

Previous Solutions

We previously used a Sonicwall NSA3500 for all our needs. We switched due to the lack of Layer three provisioning at the time plus I wasn’t a fan of one device controlling so many aspects of our network and security.

Initial Setup

I would say complex, mainly due to the lack of good documentation. All together, it took me about a week to fully get the product in a production state. Coming from a Cisco background it seemed much more cumbersome than their products.

Implementation Team

We used an in house team (me).

ROI

I am not sure of the ROI at the moment. It has not been implemented long enough for any significant ROI.

Pricing, Setup Cost and Licensing

Original setup cost for this implementation was around $30,000. Day-to-day the product costs nothing.

Other Solutions Considered

Any time we have a project we must have three viable options to choose from. We looked at HP, Cisco and Meru.

Other Advice

  • Have a strong knowledge of your internal network
  • Study the manual as much as possible
  • Focus on VSC’s and Vlan configuration
  • If you come from a Cisco background keep in mind you won’t use an access port on the switch port connected to the AP like you would in a Cisco WLC setup, but instead either a trunk or tagged port
Disclosure: I am a real user, and this review is based on my own experience and opinions.
1 visitor found this review helpful

Add a Comment

Guest
Why do you like it?

Sign Up with Email