i´m facing exactly the same problem after upgrading from 7.5 to 8.0. Since the MSE is only accessible via VSAT, i have to be sure what i´m doing next... If you say "run setup again", do you mean the Setup.sh or installing the MSE with the bin-File?
Hi Neville, after rm all Folders naturally the setup.sh was also removed, so i had to reinstall the MSE Application. The Good news is, that after all the MSE works properly and after adding the MSE to the WLCs auth-list the NMSP runs perfectly.
I followed the same procedure and it worked, but I don't think you have to delete this folders.
After the first try I managed to get the MSE working when I executed the setup.sh, but the MSE was unreachable in PI. The only thing I did at the setup.sh was:
1. Menu Mode
6) Prime Infrastructure password
<Set password and reboot>
The last step for me was to change the username and password in prime 3 (Services > Mobility Services Engines > <Choose your MSE in the right pane> > Edit configuration top right drop down menu > Enter user: admin password: <password entered in setup.sh>.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...