Cisco Cisco 3310 Mobility Services Engine Release Notes
9
Release Notes for Cisco Mobility Services Engine, Release 8.0.120.0
Upgrading Cisco MSE
Step 5
To migrate data to 7.x.x.x, follow the steps provided in the
.
Compressed Software Image
If you download the Cisco MSE image *.gz file using the Cisco PI, the Cisco MSE automatically
decompresses (unzips) it, and you can proceed with the installation as described in the
decompresses (unzips) it, and you can proceed with the installation as described in the
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 tar zxvf command. For more information, see the Manually Downloading
Software section in the Cisco Connected Mobile Experiences Configuration Guide, Release 8.0.
running the installer. These files are compressed under the Linux operating system and must be
decompressed using the tar zxvf command. For more information, see the Manually Downloading
Software section in the Cisco Connected Mobile Experiences Configuration Guide, Release 8.0.
To make the .bin file executable, use the chmod +x <filename.bin> command.
The Cisco MSE virtual appliance is distributed as follows:
•
Open Virtualization Format (OVF) for VMware
For more information on deploying the Cisco MSE virtual appliance, see the Cisco MSE Virtual
Appliance Configuration Guide, Release 8.0.
Appliance Configuration Guide, Release 8.0.
Updated Software Version Shown in the Cisco PI After Polling
After a software update, the new Cisco MSE software version does not immediately appear in Cisco
MSE queries on the Cisco PI. Up to 5 minutes are required for the new version to appear. By default,
Cisco PI queries the Cisco MSE for status every 5 minutes.
MSE queries on the Cisco PI. Up to 5 minutes are required for the new version to appear. By default,
Cisco PI queries the Cisco MSE for status every 5 minutes.
Upgrading Cisco MSE High Availability
To upgrade for Cisco MSE high availability, follow these steps:
Step 1
Ensure that the HA pair that needs to be upgraded is in normal mode and not in Failover mode. In normal
mode, the Primary MSE is active and the Secondary is in standby mode. The output of the gethainfo
command on primary MSE will show PRIMARY_ACTIVE and the secondary MSE will show
SECONDARY_ACTIVE.
mode, the Primary MSE is active and the Secondary is in standby mode. The output of the gethainfo
command on primary MSE will show PRIMARY_ACTIVE and the secondary MSE will show
SECONDARY_ACTIVE.
Step 2
Log in to Cisco Prime Infrastructure and delete the MSE HA pair.
Step 3
Perform a full backup of the primary MSE.
Step 4
Stop the primary MSE and the secondary MSE using the service msed stop command.
Step 5
Perform the upgrade on the Primary and Secondary Cisco MSE servers by following the instructions
described in
described in
.
Step 6
Start both the primary and secondary MSE instances using the service msed start command.
Step 7
Recreate the MSE HA pair using Cisco Prime Infrastructure.