Cisco Cisco 3365 Mobility Services Engine

Uninstall the software. Delete the database.

Based on backed up data that you want to restore, follow the matrix in 

 to install a relevant version 

of MSE.

Once you have installed the software, restore the desired database backup onto this using the regular 
procedure from the Prime Infrastructure.

To migrate data to 7.x.x.x, follow the steps in the 

If you download the mobility services engine image *.gz file using the Prime Infrastructure, the mobility 
services engine automatically decompresses (unzips) it, and you can proceed with the installation as 
before. 

If you manually download the compressed *.gz file using FTP, you must decompress the files before 
running the installer. These files are compressed under the LINUX operating system and must be 
decompressed using the gunzip utility program. The unzip method you use is defined by the filename 
you are trying to unzip. 

To make the bin file executable, use the chmod +x filename.bin command.

The MSE virtual appliance software is distributed as an Open Virtualization Archive (OVA) file. You can 
install the MSE virtual appliance using any of the methods for deploying an OVF. For more information 
on deploying the MSE virtual appliance, see Chapter 5: “MSE Delivery Modes” in the Cisco Connected 
Mobile Experiences Configuration Guide, Release 7.4, and Cisco Wireless Intrusion Prevention System, 
Release 7.4, respectively.

After a software update, the new mobility services engine software version does not immediately appear 
in mobility services engine queries on the Prime Infrastructure. Up to 5 minutes is required for the new 
version to appear. Prime Infrastructure, by default, queries the mobility services engine for status every 
5 minutes.

5.2.0

5.2, 6.0, 7.0

6.0

6.0, 7.0