Hi,
I will try to summarize the answers in the below points:
1. Yes, AP can be redirected to different controllers based upon the LMS settings.
2. As you need both the controllers to be active, you would configure them in master-local topology.
As you are interested in using HA, the LMS IP can't be the VRRP IP.
However, VRRP IP can be used for controller discovery. basically, you can point the DNS entry for aruba-master to VRRP IP address.
Eg:
10.1.1.1 - Master
10.1.1.2- Local
10.1.1.3- VRRP IP (create DNS entry for aruba-master pointing to this address).
In case you do not plan to use VRRP, you can map IP's of both master/local controller to aruba-master. The response for aruba-master will contain both the IP's. AP will try to reach the first IP in the response. If it is unable to communicate with the 1st IP, it will then try to contact the 2nd IP.
Basically, your HA profile will have both the controllers set in dual role as shown in following example:
ha group-profile "HA"
preemption
heartbeat
controller 10.1.1.1 role dual
controller 10.1.1.2 role dual
!
You will need couple of AP system profiles:
AP System profile 1: Will be used in the AP-group where AP's need to use master controller as primary controller.
LMS: 10.1.1.1
B.LMS: 10.1.1.2
AP system profile 2: Will be used in the AP-group where AP's need to use local controller as primary controller.
LMS: 10.1.1.2
B.LMS: 10.1.1.1
Then you can make both the controllers member of this HA profile. You can also enable state-snchronization in the HA profile (explanation provided in the user guide).
Note: The above configuration will allow the AP's to make use of HA failover mechanism.
Please refer to UG for more details information.