Looking for 802.11 rfc in regards to client roaming
Yes there are basic rules the vendors follow but those rules are still vendor specific.
Vendors usually depend on signal strength, delay, noise, packet loss...etc in order to decide when to roam. But each vendor takes different decision based on the equation they use to decide roaming.
For example, if there are two APs show good signal to a client while the clients is moving from one AP toward another, one client may decide to roam because there is a new signal that is stronger. Another client however may decide not to roam if the connection to the old AP is still OK although the new signal strength is higher.
If you want you need to look into vendors documents about how they decide roaming. some vendors allow you to modify roamign aggressiveness though:
Roaming Aggressiveness This setting allows you to define how aggressively your Wi-Fi client roams to improve connection to an access point. Click Use default value to balance between not roaming and performance.
Lowest: Your wireless client will not roam. Only significant link quality degradation causes it to roam to another access point.
Medium-Low/Medium-High: Allow Roaming.
Medium: Balanced setting between not roaming and performance.
Highest: Your Wi-Fi client continuously tracks the link quality. If any degradation occurs, it tries to find and roam to a better access point.
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...