I reported this - or a very similar issue - on 7/24/14. Basically I think the sync is just enough different that the SM locks onto the weaker beacon of the opposite side AP and while it's decoding that it ignores the stronger beacon of the closer AP.
On Sun, Nov 22, 2015 at 9:08 AM, Ken Hohhof <[email protected]> wrote: > Has anyone else seen this? > > I have an ABAB site where some SMs couldn't register to the AP or see it > in AP Eval Data, but could see the opposite AP (same frequency, very low > signal level, different color code). I checked and the opposite AP was > stuck on iGPS despite having power port sync available. I power cycled the > opposite AP, which then came up on power port sync, and the SM registered > to the correct AP. > > I still have these on 13.2.1 and maybe 14.1.1 will fix the "stuck on iGPS > sync" problem. > > But how was the one AP masking the other? The only thing I can think of > is the sync was slightly different and somehow that prevented the SM from > seeing the beacons, despite the signal being much higher. The only other > unique thing about the config is these APs are on 5845 (10 MHz channel), so > they are on the highest available frequency. The power port sync is coming > from a CTM2 over 300 ft cables. > > Changing out the SM didn't make a difference. > >
