Preview Tool

Cisco Bug: CSCvv13214 - Anchor deliberately closing DTLS with New Mobility member after session is re-established

Last Modified

Sep 17, 2020

Products (1)

  • Cisco 5500 Series Wireless Controllers

Known Affected Releases


Description (partial)

- Mobility path does not re-establish properly after a connectivity issue in the path takes the control or data path down between New Mobility members (NGWC Foreign and AireOS Anchor).
- Connectivity is back between the controllers, but their tunnel does not come back as expected; it does not recover until mobility member entry is removed and re-added on the Anchor WLC.
- Anchor WLC is killing the DTLS session that is just re-established with the mobility peer. Immediately after the initial DTLS handshake is successfully finished, the Anchor sends a Close Notify Alert and kills the session, so they try to re-establish it again, but the same cycle repeats.

- AireOS Anchor WLC 5520 running 8.5.161.x
- NGWC Foreign WLC 3650 running 16.3.8
- New Mobility between them with Control/Data paths up, but that goes down at some point for any reason (like connectivity issue in the path); when trying to recover the DTLS tunnel, they cant.
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.