Reset Search
 

 

Article

Client cannot connect and is constantly rejected from the Controller in a Mobility Domain

« Go Back

Information

 
TitleClient cannot connect and is constantly rejected from the Controller in a Mobility Domain
Symptoms
  • Client is DEAUTH'ed repeatedly from the Access Point
  • Cannot connect no matter what controller or AP it connects too
  • Only happens on certain clients, most users are ok. 
  • Message in Controller station events regarding the DEAUTH is:    
    Cause[Request from Other Controller]
Environment
  • ExtremeWireless
  • Version 9.21.11 and older
  • Version 10.01.05 and older
  • Multiple Controller Availability Pairs
  • Mobility Domain
  • Mobility Matrix
Cause
This is caused by an issue with Bulk Association communication between Mobility Controllers. When the time stamp is not the same for controller updates then some clients can be impacted.  (Note: The time stamp can be off even if network time is correct for all controllers) 
Resolution
  • Upgrade to Version 9.21.12 or 10.01.06 and newer. 
  • Workaround is to disable the Mobility Manager function, and then re-enable.  This will cause clients in the Mobility Matrix to drop, and then re-associate to their local AP/Controller. This will only take about 15-20 seconds to complete, but we recommend doing this off-hours or scheduling it.  
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255