Guest

Preview Tool

Cisco Bug: CSCvu69426 - ewlc-Auto-contain doesn't resume after rogue-client gets removed and connects back later

Last Modified

Aug 21, 2020

Products (1)

  • Cisco Aironet 1850 Series Access Points

Known Affected Releases

ap-17.4.0.2

Description (partial)

Symptom:
Rogue  client containment does not resume after rogue client is removed

Conditions:
Autocontain configured for "using our own ssid" initiates containment on AP after detecting same ssid. 

Containment get stopped after rogue client gets removed from AP and controller.

Clients associate back to rogue AP after a day. Rogue contain payload is not pushd from controller
to AP in this case
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.