03-29-2022 09:55 AM - edited 03-29-2022 09:59 AM
Good afternoon.
I have a problem assigning a wIPS profile to a WLCs.
The environment consist of MSE 8.0.150 , PI 3.7.0, Primary and Secondary WLCs 5520 8.10.151, APs 4800 in wIPS submode. We have all required licenses for MSE wIPS (ELM and MM both) , for PI and APs on WLCs.
It was working well, but some tome ago it broke and we can't make in work again.
The problem happens when we try to apply a wIPS profile to the WLCs from the PI.
It fails for both WLCs associated with wIPS service. At the moment of the attempt, ome WLC is primary and holds all APs, another one is secondary and has 0 APs. Both WLCs have active NMSP connection with the MSE.
The third WLC on the screenshot is Anchor WLC which is not important, don't be confused. BTW it has the same error if we try to associate it with the wIPS profile.
We found several errors on the MSE:
But we do not understand if it address our issue.
Here is one more weird thing we noticed - wIPS service does not find any WLC:
So, the MSE has an active NMSP connection with the WLCs but the wIPS service running on this MSE can't see the WLCs. We double-checked licensing limits, and it was fine, but usage was "0".
We have tried disabling and enabling wIPS service, MSE restart, and also cleared the history logs, since it caused a bit perfomance problems. But nothing helped, the wIPS service doesn't see WLCs.
It looks like a cause for the error we can see in the PI when we try appliyng wIPS profile, but we need some guidance how to troubleshoot it further.
Thank you!
03-29-2022 05:07 PM
the WLC version 8.10 has limited support, see table 13 for limitations, only selected signatures are supported so one thing to verify is your profile does not contain unsupported signatures.
secondly try this debug on wlc and see if you are seeing any communication from MSE, may be it will give some hint.
debug nmsp all
04-15-2022 04:33 AM
Hello @ammahend , thank you for the reply.
We tried to bind a new profile with only one signature ("AirDrop Session detected" which is supported, by the "Software Compatibility Matrix"). That didn't work "...Error: Can not find controller(s)".
NMSP communication works, a lot of logs from *apfLbsTask:, *apfRogueTask_0:, *spectrumNMSPTask:, *nmspTxServerTask:.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide