Clients connecting to "G" radio are not able to pass traffic / not able to get ip address when using AP LACP
Consider the scenario were there are two local controllers A and B with HA pair configured.
There are two AP groups ,one with LMS pointing to Controller A and other pointing to Controller B.
ap system-profile "LocalA"
ap system-profile "LocalB"
ha group-profile "bc-boston-HA-group"
controller 10.1.1.2 role dual
controller 10.1.1.3 role dual
Below is the ap lacp configuration on both the controllers
AP LACP LMS map information
AP LACP Striping IP Enabled
GRE Striping IP 10.1.1.10 LMS 10.1.1.2
GRE Striping IP 10.1.1.50 LMS 10.1.1.3
Now consider the APs with LMS as LocalA. They will use 10.1.1.10 as striping ip address for 2.4/G radio traffic.
Since 10.1.1.10 is also configured on LocalB as striping address , it can also respond to the ARP request.
In this case if the intermediate/uplink switch updates the ARP for 10.1.1.10 as controller B ,then the traffic will be routed to wrong controller
This results in clients connecting to "g" band not able to pass traffic .
We need to make sure that the LACP striping ip address is unique on each controller
The correct configuration should be as below
Local controller A :
striping-ip 10.1.1.10 lms 10.1.1.2
striping-ip 10.1.1.50 lms 10.1.1.3
Local controller B:
striping-ip 10.1.1.11 lms 10.1.1.2
striping-ip 10.1.1.51 lms 10.1.1.3
The APs with LMS ip as 10.1.1.2 in system profile will terminate on controller A and use striping ip as 10.1.1.10.
When they fail-over to controller B (10.1.1.3 ) they will use the striping ip as 10.1.1.11
Similarly APs with LMS ip as 10.1.1.3 in system profile will terminate on controller B and use striping ip as 10.1.1.51 ,
When they fail-over to controller A (10.1.1.2 ) they will use the striping ip as 10.1.1.50.