In addition to that, most Aruba controller deployments are layer-2, which means the controller doesn't have an IP address in the vlans used for your wireless clients. If you need access to the management IP of the controller, you will need to setup routing and if a firewall is in between access rules that your client can access the controller management IP.
Most times customers specifically try to limit the access to the controller from the wireless SSIDs; this can be the case.
Probably the first step is to find the management IP (or any IP on the controller), the second step is to make sure your client can access the controller from the subnet where it is in.