Showing results for 
Search instead for 
Did you mean: 

How does an Anchor WLC be marking the client for deletion once a client is disassociated / deauthenticated on Foreign WLC?

Do we have a flow of how an Anchor WLC will be marking the client for deletion once the client is de-authenticated/ disassociated from the Foreign WLC?

  • Under ideal scenario it is assumed that the foreign WLC will be ‘Sending Handoff Close’ for the mac entry to the Anchor WLC and accordingly its marked for deletion on Anchor WLC as well instantaneously.


How about the clients that have not been gracefully de-authenticated or when it moves away?

  • Anchor and Foreign WLC evaluates their configured ‘Client user idle timeout’ independently before marking the client for deletion or will there be a sync between Anchor-Foreign once the entry is deleted from Foreign after expiry of ‘Client user idle timeout’?
Hall of Fame Master

You answered your question... idle timer. As long as the sleeping timer is not used, the idle timer then the session timer will be used.
*** Please rate helpful posts ***

Thank you Scott for your response.

I mean will the Anchor and Foreign will  be evaluating the individually configured user idle timeout on the WLAN independently and accordingly deleting the entries


If the foreign is first to delete the entry after the lapse of user idle timeout, will the foreign be informing Anchor as well to get rid of that client entry as well?


In anchor/foreign, each controller has its own client tables. So there is no true sync when a client walks away from coverage. If the user disconnects from the ssid, then that is sent to the controller. This is nothing to really worry about to be honest. The idle timer will remove the MAC address of the device in its table. The foreign controller is responsible for the association and initial authentication so that controller determines what state the device should be in. If the device is in the table still, then the session continues, if not, then the device needs to go through the whole association l/AUTH the get on.
Why not just test it yourself to see if you get your answer? You need to test if a client shuts down, when a client walks away from coverage, when a client goes to sleep, so you can see if and when the device gets removed from both or not. With sleeping client enabled, the device is help on the anchor which sleeping client is enabled, thus the foreign will delete the device but the anchor will still have it. So depending on what you are trying to do will affect what you see.
*** Please rate helpful posts ***
Content for Community-Ad