Can sleeping clients just be on anchor controller 7.6? Can the foreign controller not have sleeping clients configured and it still work as long as the anchor is configured for sleeping clients? The other question is.. Do all user use sleeping clients or only user who have actually web authed? We have a lot of people in webauth required state not sure if they count against the sleeping client count.

[Aaron Box]

Can sleeping clients just be on anchor controller 7.6? Can the foreign controller not have sleeping clients configured and it still work as long as the anchor is configured for sleeping clients? The other question is.. Do all user use sleeping clients or only user who have actually web authed? We have a lot of people in webauth required state not sure if they count against the sleeping client count.

[Saurav Lodh]

A sleeping client does not require reauthentication in the following scenarios:

• Suppose there are two controllers in a mobility group. A client that is associated with one controller goes to sleep and then wakes up and gets associated with the other controller.
• Suppose there are three controllers in a mobility group. A client that is associated with the second controller that is anchored to the first controller goes to sleep, wakes up, and gets associated with the third controller.
• A client sleeps, wakes up and gets associated with the same or different export foreign controller that is anchored to the export anchor.
• http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-5/config_guide/b_cg75/b_cg75_chapter_010111.html#concept_F70A46E44FFB41CA9C2A4FC60A81B0A2