Cisco Bug: CSCun82296 - Communication between MSE and Amur NGWC/WLC is in Inactive state
Feb 27, 2018
- Cisco Prime Infrastructure
Known Affected Releases
2.0(0.0.274) 2.1(0.0.19) 2.1(0.0.57) 2.1(0.0.78) 2.1(0.0.79) 2.1(0.0.83) 2.1(0.0.85) 2.2
Symptom: Communication between MSE and NGWC in inactive state. MSE not able to establish SSL handshake with NGWC. "certificate_unknown" or "java.net.ConnectException: Connection refused" exception is seen in the MSE Location Server log file. Conditions: The "Connection refused" exception happens if NMSP is not enabled on the Amur NGWC. The "certificate_unknown" exception can happen under one of the three scenarios below : 1. An Amur NGWC is added to PI, and then synchronize to MSE 8.0. 2. A NGWC (running image earlier than Amur) was added to PI, and synchronized to MSE 8.0. After that, upgrade NGWC image to Amur. 3. An Amur NGWC was added to PI, and synchronized to MSE 8.0 (with the workaround described in this release-note). Later upgrade 8.0 to newer build.
Related Community Discussions
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