cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
347
Views
2
Helpful
1
Replies

WLC -MSE NMSP status is inactive

Customer had some update done on Aeroscout and since then NMSP is inactive

Controllers: 2 5508 in HA mode running 8.5.140

MSE 3355 running 8.0 

Prime version 3.4

Verified the Auth list. readded the Hask Key shown in MSE. in the debug it shows handshake failure for the NMSP connection. There were 2 Hask Key in MSE. Sha1 and SHa2. Tried both and resync the services on the Prime. Still the error Key Hash Match

The product is EOL and End of Support. Just shouting out loud for any other workarounds

RShaikMahamood_0-1747075301807.png

 

1 Reply 1

Saikat Nandy
Cisco Employee
Cisco Employee

The snippet is pointing towards two issues - timezone and Hash mismatch.

For timezone - Please ensure that both controller and MSE are using the same NTP server. If you are not using NTP and relying on manual configuration, please ensure that WLC time is not behind the time that is set on the MSE.
For Hash Mismatch -
    ## First try adding the hash value using LBS-SSC & SHA256-LBS-SSC (lbs-ssc should work). 
    ## Secondly there could be a potential issue with TLS version. Try enabling TLSv1 for NMSP. Refer - https://www.cisco.com/c/en/us/td/docs/wireless/mse/release/notes/mse8_0_150.html#pgfId-1652296 (Section - Enabling TLS Version 1.0 for NMSP Connections)

Review Cisco Networking for a $25 gift card