Cisco Cisco 3365 Mobility Services Engine Release Notes

This unpack yields the following three files. These three files must be in the same directory when 
running the installer. The installation process uses the MSE_PUB.pem and signhash.bin to validate the 
integrity of the MSE image.

If the MSE image file was transfered directly to the MSE and not downloaded using PI, then the 
following command should be used to decompress and unpack the installer files: 
tar zxvf ../CISCO-MSE-L-K9-8-0-100-0.bin.tar.gz

Make sure that the CISCO-MSE-L-K9-8-0-100-0-64bit.bin file has execute permissions for 
the root user. If not, enter the following command: 

Manually stop the MSE service using the following command:

or service msed stop

To install the new Mobility Services Engine image, enter the following command:

The installation process takes a minimum of 30 minutes. The actual installation time depends on the 
amount of data present in your system. After the installation, you need to reboot the system before 
starting the MSE.

Start the new Mobility Services Engine software by entering the following command. If you attempt to 
start the MSE, it just returns an error saying that MSE needs to be rebooted.

The system must be rebooted after upgrading the MSE. After exiting the installer, enter the command 
reboot

 at the prompt to reboot the MSE.

To restore an old database, follow these steps: 

The regular Restore option on the Prime Infrastructure cannot be used to restore a backup from an older 
MSE releases such as 6.0, 7.0.105.0, or 7.0.110.0 onto 8.0.100.0.

Stop the MSE service: /etc/init.d/msed stop

Uninstall the software and select to delete the database.

To restore the backup data, you must first install the appropriate version of MSE software. Use the table 
below to determine the correct version of MSE to install.