Preview Tool

Cisco Bug: CSCur78697 - 1st Hop MAP CAPWAP Restart Due to race condition when seeking RAP2

Last Modified

Sep 07, 2016

Products (1)

  • Cisco Aironet 3700 Series

Known Affected Releases


Description (partial)

1st Hop MAP takes almost 1 Min to rejoin to RAP2 after the CAPWAP Restart

Association request sent by 1st Hop MAP's to Controller using RAP2 as Proxy Node 
The controller Sends Association response & EAPOL ID  request to the 1ST Hop Map's via RAP asking it to start the EAPOL Security 4 way handshake process. 
After receiving the EAPOL ID the port is in Blocked state allowing only 4 Way handshake  messages to pass through. 
Typically Assoc response should have sent first to 1st hop MAP and then the EAPOL ID by RAP. 
This results in 1st Hop MAP never receiving the Assoc response causing the MAP1 to start the association process all over again resulting in CAPWAP Restart
Bug details contain sensitive information and therefore require a 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.