10-13-2015 09:41 PM - edited 07-05-2021 04:05 AM
Hi all, I've just recently upgraded to Prime 3.0 and think I may have either introduced an issue or am seeing an issue come to light because of it. I'm running a HA pair of virtual MSE (7.6.120.0) and have found that about every hour, the MSE drops the NMSP connection to my wireless controllers (all 25 at the same time). I've found that I can go into Synchronization Services, check a controller to synchronize it, remove the CAS check, sync, add the CAS check, sync, and all is good. I've tried lowering the Mobility Synchronization (was 60, now 30) and that hasn't helped either. Has anyone else seen this or am I a lucky one running into a 3.0 bug?
Thanks In Advance!
10-15-2015 09:03 PM
CMX 10.2.x is out there, so suggest to upgrade your MSE platform to this and then there is no dependency on Prime for location analytic.
http://www.cisco.com/c/en/us/td/docs/wireless/mse/release/notes/cmx_10_2_rn.html
If you want to stick with MSE 7.6.x then best to reach TAC & see if this is a known issue.
HTH
Rasika
03-08-2016 12:39 PM
I forgot to update this, but we found the issue was tied to a previous version of Prime that was used to transition to 3.0 still running. It appears that the server was essentially polling the controllers and causing the black out. Once we turned off that server all was calm again.
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