Guest

Preview Tool

Cisco Bug: CSCum57439 - client clean up not proper on anchor after roaming

Last Modified

Dec 11, 2015

Products (1)

  • Cisco 5700 Series Wireless LAN Controllers

Known Affected Releases

10.1(0.9)

Description (partial)

Symptom:
Katana1 -> Katana2
3.6.3 pi03

Enable native profiling with http on both the controller on the wlan. Now connect a client to    katana1
do http gleaning for the client on katana1
Now the roam the client to katana2
When the client is in Foreign state on katana2, disconnect or disable the client
the client entry on the Foreign is cleaned up
But the anchor still  has that entry. it does not get removed unless force deauth  command is used. or in some cases the controler has to reloaded.
the client cannot also move back to the anchor in this state

Conditions:
Katana1 -> Katana2
3.6.3 pi03

Enable native profiling with http on both the controller on the wlan. Now connect a client to    katana1
do http gleaning for the client on katana1
Now the roam the client to katana2
When the client is in Foreign state on katana2, disconnect or disable the client
the client entry on the Foreign is cleaned up
But the anchor still  has that entry. it does not get removed unless force deauth  command is used. or in some cases the controler has to reloaded.
the client cannot also move back to the anchor in this state
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.