Upgrading Cisco MSE
For instructions on automatically downloading the Cisco MSE software using Cisco Prime Infrastructure or for manually downloading the software using a local or remote connection, see the “Updating Mobility Services Engine Software” section in Chapter 2 of the Cisco Mobility Services Engine Getting Started Guide : https://www.cisco.com/c/en/us/support/wireless/mobility-services-engine/products-installation-guides-list.html
Only users with Cisco MSE Release 7.4 or later will be able to upgrade to Cisco MSE Release 8.0.140.x. The following scenarios are available to upgrade from Cisco MSE Release 7.4x to Cisco MSE Release 8.0.140.x.
Note Do not uninstall the releases 7.4, 7.5, 7.6, or 8.x, instead stop the Cisco MSE and run the installer.
– Downgrading from Cisco CMX Release 10.x to Cisco MSE Release 8.x
Compressed Software Image
If you download the Cisco MSE image *.gz file using the Cisco Prime Infrastructure, the Cisco MSE automatically decompresses (unzips) it, and you can proceed with the installation as described in the “Upgrading from Cisco MSE Release 7.4.x to Cisco MSE to 8.0.140.x” section.
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.
To make the.bin file executable, use the chmod +x <filename.bin> command.
The Cisco MSE virtual appliance is distributed as 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.
Upgrading from Cisco MSE Release 7.4.x to Cisco MSE to 8.0.140.x
Ensure that you have copies of your Cisco MSE license files before performing the upgrade. If you do not have copies of the Cisco MSE license files, copy the *.lic files under the /opt/mse/licensing folder of the Cisco MSE to your local machine.
Note We recommend that you back up the Cisco MSE using Cisco Prime Infrastructure.
Note If you already have Cisco MSE Release 22.214.171.124 installed (either with or without the CSCuv55645.zip patch), you can upgrade to Cisco MSE Release 8.0.140.x using the upgrade procedure described in this section.
Step 1 Untar the Cisco MSE software image before placing it in the /opt/installers directory.
Step 2 Upgrade the Cisco MSE from Cisco MSE Release 7.4 to Cisco MSE Release 126.96.36.199.
Step 3 Download the applicable 8.0.140.x software image from Cisco.com. For example, the image name for Cisco MSE Release 188.8.131.52 is CISCO-MSE-L-K9-8-0-140-0-64bit.bin.tar.gz.
Note If you are downloading the Cisco MSE image file on a Windows system, remember that some browsers modify the downloaded filename. If the downloaded filename is not correct, you must update it to the correct filename before using Cisco Prime Infrastructure to transfer the file, or directly copying the file to Cisco MSE.
Step 4 From the Cisco Prime Infrastructure UI, select Services > Mobility Services Engine to download the software to a Cisco MSE.
Step 5 Click the name of the Cisco MSE to which you want to download the software.
Step 6 Select System > Maintenance > Download Software from the left menu. The Upload Software Image screen displays.
Step 7 Click Select File, and navigate to the local folder that contains the upgrade file.
Step 8 Select the file and click Open. When the filename appears in the Upload Software Image field, click Import to send the software to the /opt/installers folder on the Cisco MSE.
Step 9 When using Cisco Prime Infrastructure to transfer the image to Cisco MSE, the file will be decompressed, and the.gz will be removed from the filename. Verify that the Cisco MSE image file is in the Cisco MSE /opt/installers directory. For example, the image name for Cisco MSE Release 184.108.40.206 is CISCO-MSE-L-K9-8-0-140-0-64bit.bin.tar.gz.
Note When copying the Cisco MSE image file directly to the Cisco MSE without using Cisco Prime Infrastructure, the filename of Cisco MSE image will remain unchanged.
Step 10 Use the cd /opt/installers command to navigate to the /opt/installers directory.
Step 11 Use the tar xvf <.tar.image-name > command to unpack the installation files. For example, for Cisco MSE Release 220.127.116.11:
tar xvf CISCO-MSE-L-K9-8-0-140-0-64bit.bin.tar
This unpack action yields the following files. These files must be in the same directory when running the installer. The installation process uses the MSE_PUB.pem and signhash.bin files to validate the integrity of the Cisco MSE image.
- CISCO-MSE-L-K9-8-0-140-0-64bit.bin (for Cisco MSE Release 18.104.22.168)
CISCO-MSE-L-K9-8-0-140-9-64bit.bin (for Cisco MSE Release 22.214.171.124)
Note If the Cisco MSE image file was transfered directly to the Cisco MSE and not downloaded using Cisco Prime Infrastructure, use the tar xvf <.gz-image-name> command to decompress and unpack the installer files.
Note Do not untar or unzip the database package.
Step 12 Use the chown nobody:nobody./ < image-names > command to change the permissions of the files. For example, for Cisco MSE Release 126.96.36.199:
chown nobody:nobody./CISCO-MSE-L-K9-8-0-130-0-64bit.bin signhash.bin Database_Installer.188.8.131.52.tar.gz
Note A space must be provided between the filenames in the chown command above.
Step 13 Make sure that the Cisco MSE bin file (for example, CISCO-MSE-L-K9-8-0-140-0-64bit.bin) has execute permissions for the root user.
If it does not, use the chown +x <.bin-image-name > command. For example, for Cisco MSE Release 184.108.40.206:
chmod +x CISCO-MSE-L-K9-8-0-140-0-64bit.bin
Step 14 Manually stop the Cisco MSE service by entering this command:
/etc/init.d/msed stop or service msed stop
Step 15 Use the /opt/installers/ <.bin-image-name > command to install the new Cisco MSE image. For example, for Cisco MSE Release 220.127.116.11:
Note 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, reboot the system before starting Cisco MSE.
Step 16 Start the new Cisco MSE software by entering the following command. If you attempt to start the Cisco MSE, a message is displayed that Cisco MSE should be rebooted.
Step 17 After exiting the installer, enter the reboot command to reboot Cisco MSE.
See “Upgrading Cisco MSE High Availability” section for details on upgrading Cisco MSE high availability.
Restoring an Old Cisco MSE Backup to Cisco MSE Release 8.0.140.x
Note Before you begin: If high availability is configured, delete the secondary Cisco MSE before restoring the historical data on the primary Cisco MSE. You can add the deleted Cisco MSE after restoration on the primary Cisco MSE successfully completes.
To restore an old database, follow these steps:
Note The regular restore option on the Cisco Prime Infrastructure cannot be used to restore a backup from an earlier Cisco MSE Releases such as 6.0, 18.104.22.168, or 22.214.171.124 to Cisco MSE Release 8.0.140.x.
Step 1 Stop the Cisco MSE service: /etc/init.d/msed stop
Step 2 Uninstall the software and select the option to delete the database.
Step 3 To restore backup data, you must first install the appropriate version of Cisco MSE software. Use the table below to determine the correct version of Cisco MSE to install.
Table 1 Release Matrix
Version of Database to be Restored
New Version to be Installed
Step 4 After you have installed the software, restore the desired database backup to the new Cisco MSE using the regular procedure from Cisco Prime Infrastructure.
Step 5 To migrate data to 7.x.x.x, follow the steps provided in the “Upgrading from Cisco MSE Release 7.4.x to Cisco MSE to 8.0.140.x” section.
Updated Software Version Shown in the Cisco Prime Infrastructure After Polling
After a software update, the new Cisco MSE software version does not immediately appear in Cisco MSE queries on the Cisco Prime Infrastructure. Up to 5 minutes are required for the new version to appear. By default, Cisco Prime Infrastructure 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 Cisco 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 Cisco MSE HA pair.
Step 3 Perform a full backup of the primary Cisco MSE.
Step 4 Stop the primary Cisco MSE and the secondary Cisco 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 Upgrading from Cisco MSE Release 7.4.x to Cisco MSE to 8.0.140.x.
Step 6 Start both the primary and secondary Cisco MSE instances using the service msed start command.
Step 7 Recreate the Cisco MSE HA pair using Cisco Prime Infrastructure.
Configuring History Pruning Parameters
The History Pruning parameters are configured from the Cisco Prime Infrastructure or Cisco MSE user interface. This interface is used to:
- Enable/Disable History tracking for clients/tags/rogue APs/rogue clients/interferers.
- History Retention period—How long (in days) to retain history data.
- Time at which to prune history records.
Starting in Cisco MSE Release 126.96.36.199, the Cisco Prime Infrastructure and Cisco MSE user interface is used to enable/disable History tracking for clients/tags/rogue APs/rogue clients/interferers. The pruning of History data takes place every hour automatically. This hourly pruning task computes the number of history records that must be deleted to bring the record count to the platform limit. After the computation, the pruning task deletes the oldest history records so that the record count matches the platform limit. The history pruning task does not perform anything if the history record count is below the platform limit. The Cisco MSE Administrator cannot change the pruning interval or the history retention duration.
The history record count for various Cisco MSE platforms is as follows:
- MSE-3355—7.5 million records
- MSE-3365—25 million records
Virtual MSE—15 million records
This section describes the operational notes and navigation changes for Connected Mobile Experiences, wIPS, and the Cisco MSE for Release 188.8.131.52 and later releases.
Features and operational notes are summarized separately for the Cisco MSE, Connected Mobile Experiences, and wIPS.
This section contains the following topics:
Operational Notes for Cisco MSE High Availability
VIP and Prime Infrastructure Configuration
(CSCvb61125) When configuring High Availability on the Cisco MSE, make sure that the virtual IP address (VIP) is assigned first, and then set the Prime Infrastructure password through the setup.sh file.
If you change the VIP after setting the Prime Infrastructure password, you will need to reset the password through the setup.sh file. Otherwise, HA configuration cannot be completed.
Swapping HA Roles
(CSCvb59484) We do not recommend swapping HA roles. If the role or the VIP needs to be changed, follow these steps:
Step 1 Run the setup script.
Step 2 Change the HA role.
Step 3 If the new role is Primary, assign the VIP.
Step 4 Select the Verify and apply option to apply the changes.
Step 5 Restart the Cisco MSE services.
Step 6 Reboot the Cisco MSE, if needed.
Step 7 Run the setup script again.
Step 8 Change the Prime Infrastructure password of the Cisco MSE.
Step 9 Select the Verify and apply option to apply the changes.
Step 10 Restart the Cisco MSE services.
Step 11 From Prime Infrastructure, edit the Cisco MSE configuration so that the primary Cisco MSE uses the new Prime Infrastructure password.
Step 12 Verify that the reachability status for the primary Cisco MSE shows as Reachable.
Step 13 Continue with HA configuration from Prime Infrastructure.
Deleting HA Mode MSE from Prime Infrastructure
To delete the Cisco MSE in HA mode from Prime Infrastructure, follow these steps.
Step 1 From Prime Infrastructure, go to the HA configuration of the primary Cisco MSE and click Delete to break the HA pair.
Step 2 After the secondary Cisco MSE is deleted from Prime Infrastructure, delete the primary Cisco MSE from Prime Infrastructure.
Operational Notes for Cisco MSE
This section lists the operational notes for the Cisco MSE and contains the following topics:
Resolution to NMSP/SHA2 Keyhash Mismatch Issue
By default, Cisco MSE Release 8.0 supports SHA-2 keyhash algorithm for peer authentication with Cisco WLC Release 8.0 during the SSL handshake. Cisco Prime Infrastructure 1.4.2 and 2.1 supports only SHA-1 AP (or Cisco MSE) Authorization template when synchronizing Cisco WLC with the Cisco MSE. This causes keyhash mismatch issue because the Cisco Prime Infrastructure and Cisco MSE use different keyhash algorithm on Cisco WLC Release 8.0. An option is added to the Advanced Parameters page in the Cisco MSE user interface (UI) to allow the user to force Cisco MSE Release 8.0 to use SHA-1 keyhash algorithm.
Follow these instructions to configure SHA-1 Cipher:
Step 1 Launch the Cisco MSE admin UI by typing https://mseip/ mseui in a web browser.
Step 2 Click Configuration.
Step 3 Choose System > Advanced Parameters from the left menu.
Step 4 Check the Enable Use of SHA-1 Ciphers check box (see Figure 1).
Step 5 Click Save.
Figure 1 Advanced Parameters
Step 6 Unsynchronize Cisco WLC from Cisco MSE, and then resynchronize Cisco WLC with Cisco MSE from Cisco Prime Infrastructure.
Step 7 The NMSP status should change to active state.
Note If the FIPS mode (also known as Root Access Control) is enabled on the Cisco MSE, then this option will not be available to the users as FIPS mode requires all operations in SHS-2.
Use a valid DNS sever as CAS and Analytics service to use nslookups.
Rebooting Cisco MSE After Fresh Installation or Upgrade
After a new installation or upgrade of the Cisco MSE software, you must reboot the Cisco MSE using the reboot command.
Mapping Controller and Associated Cisco MSE Must be Mapped to the NTP and Cisco Prime Infrastructure Server
Communication between the Cisco MSE, the Cisco Prime Infrastructure, and the Cisco WLC are in Coordinated Universal Time (UTC). Configuring the Network Time Protocol (NTP) on each system provides devices with the UTC time. An NTP server is required to automatically synchronize time between the Cisco WLC, Cisco Prime Infrastructure, and the Cisco MSE.
The Cisco MSE and its associated controllers must be mapped to the same NTP server and the same Cisco Prime Infrastructure server.
Local time zones can be configured on a Cisco MSE to assist the network operations center personnel in locate events within logs.
Note You can configure NTP server settings while running the automatic installation script. See the Cisco Mobility Services Engine Getting Started Guide Started Guide for details on the automatic installation script at https://www.cisco.com/c/en/us/support/wireless/mobility-services-engine/products-installation-guides-list.html
Default Root Password
You must change the default root password of the Cisco MSE while running the automatic installation script to ensure optimum network security.
You can also change the password using the Linux passwd command.
Note During the initial login, even if you choose Skip (S), you will be prompted to enter the password. This is because it is mandatory to change the root password at the initial login.
Configuring the Cisco Prime Infrastructure Communication Username and Password Using Cisco MSE setup.sh
You can configure the Cisco Prime Infrastructure communication password using the Cisco MSE setup.sh script file.
The scenarios which you might encounter while configuring the Cisco Prime Infrastructure password are as follows:
- By default, the username used by Cisco Prime Infrastructure to communicate with Cisco MSE is “admin”.
- The username/password used by Cisco Prime Infrastructure to communicate with Cisco MSE can be updated from the Prime user interface only. The setup.sh script only allows changes to the Cisco Prime Infrastructure communication password associated with the username “admin”. If you change the username that is used by Cisco Prime Infrastructure to a username other than “admin” then the password changes made via setup.sh are not effective.
- If you configure a new Cisco Prime Infrastructure password, the password provided is applicable for the Cisco Prime Infrastructure username: admin.
Note The Cisco Prime Infrastructure communication users are API users, and they do not have corresponding operating system users on the Cisco MSE appliance.
Configuration Changes for Greater Location Accuracy
In some RF environments, where location accuracy is around 60 to 70 percentage or where incorrect client or tag floor location map placements occur, you might have to modify the moment RSSI thresholds in the Context Aware Service > Advanced > Location Parameters page on the Cisco Prime Infrastructure.
The following RSSI parameters might require modification:
Contact Cisco TAC for assistance in modifying these parameters.
Wireless Security Module with Cisco Aironet 3600 and 3700 Series Access Points
If you are attempting to deploy Wireless Security Module (WSM) with Cisco Aironet 3600 and 3700 Series APs, then APs should be placed in monitor mode with both submode wIPS and advanced wIPS engine enabled on the Cisco Prime Infrastructure.
AeroScout Engine Module Changes
Starting Release 7.5, the AeroScout engine module is removed from both the Cisco CMX setup and location code. During installation, if you are upgrading from Release 7.2 and later to Release 7.5, then you will be prompted to remove the AeroScout engine. If you agree to remove, the AeroScout engine is removed and by default, the Cisco Tag Engine is started as part of Cisco CMX. If you do not agree to remove the AeroScout engine, the installation will exit.
Ports to be Opened for High Availability Between Cisco MSEs
The following is the list of ports to be opened for High Availability between Cisco MSEs:
- tcp 22
- tcp 80
- tcp 443
- tcp 1411
- tcp 1521
- tcp 1522
- tcp 1523
- tcp 1524
- tcp 1525
- tcp 1621
- tcp 1622
- tcp 1623
- tcp 1624
- tcp 1625
- tcp 8001
- tcp 8080
- tcp 8081
- tcp 9006
- tcp 15080
- tcp 59000
- tcp 61617
- udp 12091
Synchronizing Floor Maps in Location Service
While synchronizing floor maps in location service, we recommend that you synchronize floor maps in batches of 1000 APs at a time.
Health Monitor IP Address Issue
- (CSCvc52891) Incorrect IP addresses are displayed on the Cisco MSE Health Monitor window:
– When you configure the IP address for the Cisco MSE Eth0 port, the default IP address (184.108.40.206) is displayed from the Health Monitor window.
– When you configure the virtual IP address for a standalone Cisco MSE device, the IP address that you configured for the Cisco MSE Eth0 port is displayed from the Health Monitor window.
Northbound Notification Name Issue
- (CSCvd80611) When adding a Northbound Notification, do not include a period in the notification name (for example, Northbound.Msg or notification.aeroscout.1). Notification names with a period cannot be deleted.
Operational Notes for Context-Aware Service
This section lists the operational notes for a Cisco MSE and contains the following topics:
Synchronization Required When Upgrading to Release 220.127.116.11 or Later, or When Importing CAD Floor Images
When upgrading to Release 18.104.22.168 or later from Release 7.x, you must synchronize after the software upgrade and when CAD-generated floor images are imported into the Cisco Prime Infrastructure.
Floor Change or Minimum Distance for Location Transitions to Post to History Log
When history logging is enabled for any or all elements (client stations, asset tags, rogue clients, and access points), a location transition for an element is posted only if it changes floors, or the new location of the element is at least 30 feet (10 meters) from its original location.
Note The other conditions for history logging are as follows:
- Clients–Association, authentication, re-association, re-authentication, or disassociation.
- Tags–Tag Emergency button.
- Interferers–Interferer severity change, cluster center change, or merge.
See Services > Mobility Services > Device Name > Context Aware Service > Administration > History Parameters.
Logs can be viewed at Services > Mobility Services > Device Name > Systems > Log.
Non-Cisco Compatible Extensions Tags
The Cisco MSE does not support non-Cisco CX Wi-Fi tags. Additionally, these non-compliant tags are not used in location calculations or shown on the Cisco Prime Infrastructure maps.
Cisco Compatible Extensions Version
Only Cisco CX Version 1 or later tags can be used in location calculations and mapped in the Cisco Prime Infrastructure.
In the Monitor > Clients page (when Location Debug field is enabled), you can view information on the last heard access point and its corresponding RSSI reading.
Calibration Models and Data
Calibration models always apply to wireless clients, interferers, rogue APs, and rogue clients.
See Chapter 7, “Context-Aware Planning and Verification” in the Cisco Connected Mobile Experiences Configuration Guide, Release 8.0 for more information about client calibration.
Advanced Location Parameters
Settings for advanced location parameters related to RSSI, chokepoint usage, location smoothing, and assignment of outside walls on floors, are not applicable to tags.
See the “Editing Advanced Location Parameters” section in Chapter 7 of the Cisco Connected Mobile Experiences Configuration Guide, Release 8.0.
See Services > Mobility Services > D evice Name > Context Aware Service > Advanced > Location Parameters.
Location History Time Stamps
The Cisco Prime Infrastructure time stamp is based on the browser location and not on the Cisco MSE settings. Changing the time zone on the Cisco Prime Infrastructure or on the Cisco MSE does not change the time stamp for the location history.
Tablets and Smartphones with Limited Probe Requests
Many tablets, smartphones, and other Wi-Fi devices with power save mode do not continuously send out probe requests after an initial association to the CUWN. Therefore, calculating the location accuracy of such devices using RSSI readings is not always optimal.
Repeat Use of FloorIDs
In the relevant CAS API, the use of the parameter FLOORID is not guaranteed to return the same value on consecutive calls. It may get changed by such activities as resynchronizing the Cisco MSE. Instead, the parameter FLOORAESUID should be used. The API call getStationHistoryListByArgs can use both parameters in Cisco MSE Release 8.0.
Operational Notes for wIPS
wIPS profile cannot be pushed to Cisco Wireless Controller (WLC) 7.5 or earlier using the Cisco Prime Infrastructure 1.4.x or 2.x with Cisco MSE Release 7.6.
Operational Notes for Cisco CMX Analytics
While using the newer version of Firefox browser to connect to the Cisco MSE user interface or Cisco CMX Analytics user interface, an error message appears saying “Peer’s certificate has an invalid signature”. For more information on how to fix this, see https://support.mozilla.org/en-US/questions/776144.
To fix this, follow these steps:
Step 1 Open Firefox browser.
Step 2 Enter about:config in the address bar.
Step 3 Enter browser.xul in the Filter field.
Step 4 Verify if the browser.xul.error_pages.expert_bad_cert property exists with a value of false.
Step 5 Right-click browser.xul.error_pages.expert_bad_cert and select Toggle. The value will change to true.
Step 6 Exit from Firefox.
Step 7 Launch Firefox again and try the Cisco CMX Analytics user interface. You will be asked to add the exception.
The Cisco CMX Analytics in Release 8.0 the provides ability to view the analytic results in both 2D (Open Street Maps) and 3D Web Graphics Library (WebGL) environments. This provides improved understanding of results on multiple floor paths or when dwell times are calculated throughout a multistory building. The 3D environment presents the same information as the 2D environment.
WebGL is an advanced feature that provides graphic capabilities. All browsers do not support WebGL on a particular hardware. Verify your browser compatibility in the Get WebGL website. If your browser supports WebGL, then you must see a spinning cube.
Note If your system does not support 3D, then the analytic results are displayed only in 2D Open Street Maps view.
If your browser does not support WebGL, perform the following actions:
Step 1 Update your latest drivers for video card.
Step 2 For Google Chrome, follow the instructions given for WebGL and 3D Graphics in the Google Chrome support website.
Step 3 Enable WebGL:
- For Firefox, follow these steps:
1. Download the latest build of Firefox browser and launch Firefox on your computer.
2. In the browser address bar, enter about:config.
3. In the Search text field, enter webgl to filter the settings.
4. Double-click webgl.enabled_for_all_sites.
5. Set webgl.enabled_for_all_sites=true.
- For Safari, follow these steps:
1. Choose Safari > Preferences.
2. Click the Advanced tab.
3. Check the Show Develop menu in menu bar check box.
4. Choose Enable WebGL from the Develop menu.
Sometimes, the Cisco CMX Analytics service does not start up because of a stray JBoss process that runs as a root user. If Analytics engine does not start, and if you notice a stray JBoss process with root permissions running, perform the following actions:
Step 1 Stop Cisco CMX Analytics service from the Cisco Prime Infrastructure.
Step 2 Kill the Jboss process.
Step 3 Run the chown -R nobody:nobody /opt/mse/analytics command.
Step 4 Start Cisco CMX Analytics service from the Cisco Prime Infrastructure.
Operational Notes for Facebook Wi-Fi
When you try to pair a location with the Facebook page, it may fail with no notification in Connect and Engage user interface. One of the reasons could be due to Facebook site outage. You can check Facebook API health at: https://developers.facebook.com/status/
Operational Notes for Cisco CMX Connect and Engage
- (CSCve73287) The default setting of Cisco CMX Connect allows for a maximum of approximately two clients per second continuously, a higher number can be achieved at peak (for example 4,000 HTTP connections can be made during a 5-minute window). In additional, special configuration changes can be made to increase this rate. Contact Cisco Technical Support for these recommendations. The information in the https://www.cisco.com/c/en/us/products/collateral/wireless/mobility-services-engine/data_sheet_c07-473865.html incorrectly states that Cisco CMX supports 45 logins per second.
- While upgrading the Cisco Prime Infrastructure server, the map IDs and the information also get updated. This results in new identifiers for maps. The new identifiers are not automatically synchronized with the Cisco CMX Connect and Engage. This causes the location updates to use the new identifiers, but the Cisco CMX Connect and Engage will not be aware of the new identifiers and cause the location updates to get ignored. To resolve this issue, you must update maps in the Cisco CMX Connect and Engage user interface. To update maps, log in to the Cisco CMX Connect and Engage user interface and choose Maps from the left sidebar menu and click Update Maps from Cisco Prime Infrastructure.
Operational Notes for Mobile SDK
Two different venues with the same Cisco MSEs receiving location updates result in the device location bouncing from one venue to another venue. The Mobile Application Server (MAS) receives updates and changes the location to the most recent update received. The client location then changes from the most recent location update, which can be from either venue.
Enabling Root Access Control in HA Mode
To enable Root Access Control (RAC) in HA mode, you need to enable RAC on both the primary and secondary Cisco MSEs. The RAC configuration is not synchronized across the primary and secondary servers. Therefore, you should enable it on both servers. This will enable the RAC configuration to work on the active server in case of a failover or failback.
Resynchronizing Cisco WLC to Cisco MSE After an Upgrade
After upgrading Cisco Prime Infrastructure or Cisco MSE, in some cases, the NMSP sync between the controllers and Cisco MSE may not work properly. Without performing the unsync and resync of the controllers to Cisco MSE, you may not able to push the wIPS profiles to Cisco WLC. We recommend that after you upgrade Cisco Prime Infrastructure or Cisco MSE, perform an unsync operation and then resync all the controllers with Cisco MSE.
DoD Mode Is Enabled by Default
(CSCuy95991) By default, the DoD mode is enabled on a newly installed or upgraded Cisco MSE.
When the DoD mode is enabled, the future restart date of the Cisco MSE cannot be later than 6 months.
You can disable the DoD mode, so that the future restart date of the Cisco MSE can be set up to 1 year later.
To disable the DoD mode:
1. Enter echo “false” > /var/mse/certs/enabledod command.
2. Restart the Cisco MSE.
Access to Cisco MSE UI
The Cisco MSE UI can only be accessed by the users who are in the user group granted with Full Access permission. Users with only Read Access permission can use the REST APIs to pull data but cannot access the Cisco MSE UI.
Deleting Archive Logs
Do not manually delete the archive logs. Instead, use the /opt/mse/framework/bin/manualDeleteArchiveLogs.sh script to delete the archive logs.
Troubleshooting Errors While Installing Device Certificate on Cisco MSE
If you encounter the
Import Server Certificate failed.: Invalid input file error while installing device certificate on Cisco MSE, perform the following steps:
Step 1 Combine all certificates in CA chain into single file by concatenating them (for example, ca-chain.pem).
Step 2 Combine the signed server certificate and server private key into single file by concatenating them (for example, server-cert-key.pem).
Step 3 Import the ca-chain.pem as the CA certificate.
Step 4 Import server-cert-key.pem as server certificate.