I've seen a couple of you out there with this same issue and it doesn't look like there's much help available. I thought I'd fish for a response anyway.
We have an infrastructure designed for RF redundancy, such that if one AP fails there is another within range. Unfortunately, it seems clients aren't real disciplined to handled this and like to switch APs on a whim, despite being connected to a stronger signal. In fact, we have clients who are physically stationaary, that routinely switch off the 80% to the 30% back to the 60% and anyone's guess after that. As the two links here show, this results in interruptions of traffic.
But so far, the only solutions from TAC are to reduce power on the APs (and thereby limit the # of APs the clients see) or reduce the allowed transmit speeds of the clietns on the APs (maximize the AP for throughput). Unfortunately, each of these solutions means lowering the number of APs available for redundant connectivity should one AP fail. TAC says this is completely client controlled beyond the measures above.
Anyone succesfully designed around this? I have a hard time swallowing that RF redundancy causes problems in an RF network : ).
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...