Cisco Bug: CSCvv13214 - Anchor deliberately closing DTLS with New Mobility member after session is re-established
Sep 17, 2020
- Cisco 5500 Series Wireless Controllers
Known Affected Releases
Symptom: - 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. Conditions: - 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 Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases