While evaluating a post-installation WLAN deployment, problems are occurring when a client roams from one AP to another. The client bounces back and forth between APs. Which two items can be checked…

Question

Options

• ACheck if the roaming settings in the AP are set properly for non-CCX clients
• BCheck the RF levels of the first AP as the client moves toward the second AP
• CCheck the client RSSI and SNR levels for both APs at the roaming point
• DSimplify 802.1X/EAP by moving from external RADIUS to local authentication
• ECheck that the client roaming parameters are set properly

• A
  12% (5)
• B
  79% (33)
• D
  2% (1)
• E
  7% (3)

Explanation

Client 'bouncing' between APs (also called the sticky client problem) occurs when the roaming thresholds are not properly balanced between two APs. Checking the RF signal levels of the first AP as the client moves toward the second AP (B) reveals whether the first AP is holding on to the client too long with a still-adequate signal. Checking the client RSSI and SNR levels for both APs at the roaming point (C) identifies the overlap zone where the client switches associations, allowing you to tune the transition threshold. Option A (CCX roaming settings) and E (client roaming parameters) are configuration items that might help but are not primary diagnostic checks. Option D (switching to local authentication) addresses authentication latency, not the bouncing/oscillation behavior.

No community discussion yet for this question.