Hi Rasika,
Thank you for your answer. I read your blog and I have few more questions :
1/ If I go in the Prime to "Services -> Synchronize Services -> Controllers”, select the controller & click “Change MSE Assignment”, I could then assign the same controller to two different MSEs as shown in the enclosed picture. If I return to the WLC in CLI and run the command "swho nmsp status" it would return two lines with the information for both MSEs, am I right ?
2/ I understood that I should have two MSEs if I want to run both CAS and wIPS from Cisco documentation : "From release 7.5 onward, wIPS service requires a dedicated MSE because it does not support CAS and wIPS on the same MSE". But in your blog you checked both options on the same MSE. Did I miss a point ? Or is it a recommendation for scalability or resource issue ?
3/ For troobleshooting NMSP communication, you set up the level of log at trace with the CLI command "set trace nmsp connection level debug". In the Prime Interface, one can set up the policy of logging in the "Advanced Parameters" tab, setting "Logging Level" at Trace and checking the Advanced Debug checkbox. Is there a problem letting the MSE running with such policy of logging ?
Regards,
