I have two 4402 WLC's running 22.214.171.124 and a number of 1131AG ap's.
I have the two wlc's configured in a mobility group which is working fine.
Both interfaces, on both wlc's are connected to different pairs of switches with differing vlan loads. WLC1 has its management, AP-Mgr1 and AP-Mgr2 interfaces in vlan 'A' and WLC2 has its interfaces in vlan 'B'.
I have been testing this design out for a little while now and the inter-subnet roaming seems to be working fine.
The question I have is to do with AP failover behaviour.
If i pull the plug on port 2 of WLC1 for example, all the AP's which were using port 2 for their AP Manager interface jump to controller 2. Whilst this works, I would have thought it would simply move to port 1 on WLC1 ?
Without the mobility group, the AP would just move to port 1 on WLC1 which is faster than waiting for the AP to move controllers.
In my lab, I have stack switches, so LAG would mean connecting the WLC to a single switch. I was trying to avoid that if possible.
However, in deployment, these will be connected to a pair of cat6k's via single sup720-vss (no vss deployed but this sup has 3xSFP and the other blades are 10gig). So rather than trying to connect the wlcs between the 6ks'or even connecting them to an edge stack, I would be better off connecting one wlc to each 6k with LAG and use the mobility to provide the redundancy.
Losing a link in the bundle will not cause the the AP's to jump wlc's and if i lose the entire bundle then i have probably lost the sup anyway.
I think I was getting to caught up in my lab and LAG does look like the way forward.