Release Notes for Cisco CMX Release 10.5.x
Introduction to Cisco CMX Release 10.5.x
Resolved Caveats in Cisco CMX Release 10.5.1
Resolved Caveats in Cisco CMX Release 10.5.0
Communications, Services, and Additional Information
First Published: July 9, 2018
Last Modified: June 16, 2020
This document describes what is new and important in Cisco Connected Mobile Experiences (Cisco CMX) Release 10.5.0 and later, and provides the system requirements and caveats. Unless otherwise noted, Cisco Connected Mobile Experiences is referred to as Cisco CMX in this document.
Explore the Content Hub, the all new portal that offers an enhanced product documentation experience.
Get started with the Content Hub at content.cisco.com to craft a personalized documentation experience. Do provide feedback about your experience with the Content Hub.
Cisco CMX Release 10.5.x is a high-performing scalable software solution that addresses the mobility services requirements of high-density Wi-Fi deployments.
This release is suitable for deployments where the following features are required:
This release is not suitable for deployments where the following are required:
This release provides critical bug fixes. No features were added. We recommend this release to all Cisco CMX users. |
Cisco CMX Release 10.5.x can be installed on the Cisco 3375 Appliance for Cisco Connected Mobile Experiences and the Cisco MSE 3365 platform.
Note Cisco CMX Release 10.4.x or later does not support the Cisco MSE 3355 platform.
The Cisco 3375 Appliance requires Cisco CMX Release 10.5.1 or later. For hardware and software installation information, see the Cisco 3375 Appliance for Cisco Connected Mobile Experiences Installation Guide at: https://www.cisco.com/c/en/us/support/wireless/connected-mobile-experiences/products-installation-guides-list.html.
Cisco CMX Release 10.5.x can be installed as a Virtual Cisco MSE appliance, which requires VMware ESXi 5.1 to ESXi 6.5 versions. For information about installing a Cisco MSE Virtual Appliance, see the Cisco MSE Virtual Appliance Installation Guide at: https://www.cisco.com/c/en/us/support/wireless/mobility-services-engine/products-installation-guides-list.html
Note Cisco CMX does not support VMWare tools.
Table 3 lists the Cisco CMX Release 10.5.x hardware guidelines for a virtual Cisco MSE appliance, such as VMWare. For complete requirements, see the Cisco Connected Mobile Experiences Data Sheet at: https://www.cisco.com/c/en/us/solutions/enterprise-networks/connected-mobile-experiences/white-paper-listing.html
Note Before you deploy Cisco CMX, we strongly recommend that you refer to the following:
– Cisco Connected Mobile Experiences Data Sheet at: https://www.cisco.com/c/en/us/solutions/enterprise-networks/connected-mobile-experiences/white-paper-listing.html
– Cisco Connected Mobile Experiences (CMX) 10 Ordering and Licensing Guide at: https://www.cisco.com/c/en/us/solutions/collateral/enterprise-networks/connected-mobile-experiences/guide-c07-734430.html
Note Do not use Internet Explorer 8.0 to edit the Cisco Wireless Controller's (WLC) SNMPv3 credentials. Use Google Chrome 50 or later.
Note By default, Cisco Prime Infrastructure maps—including client location and client counts—refresh every 2 minutes. To manually refresh, click Refresh on the user interface.
RFID tags1, wireless-connected clients, rogue APs, rogue clients, and interferers |
||
Cisco Prime Infrastructure performs the Cisco CMX API query when the Cisco Prime Infrastructure Map page is displayed. |
Two weeks before the evaluation license expires, you will receive a daily alert to obtain a permanent license. If the evaluation license expires, you will not be able to access the Cisco CMX GUI or APIs. Cisco CMX will continue to run in the background and collect data until you add a permanent license and regain access to it.
Note ● You cannot upgrade to Cisco CMX Release 10.5.x from Cisco CMX Release 10.4.x and earlier. You must install and deploy the Cisco CMX Release 10.5.x OVA or ISO file on your system.
For complete information and procedures, see the Cisco Mobility Services Engine Virtual Appliance Installation Guide for Cisco CMX Release 10.5.
– We recommend that you run Cisco CMX Release 10.5.x or later in parallel with the existing Cisco MSE Release 8.0 or earlier, and utilize the evaluation license for 120 days. After the evaluation period, the older Cisco MSE release can be decommissioned.
– No database migration or inline upgrade is supported from Cisco MSE Release 8.0 or earlier to Cisco CMX Release 10.5.x.
– Use https:// to access the Cisco CMX Connect portal page. Use of http:// is no longer supported.
– For Cisco CMX Analytics (generally, Cisco CMX as a whole), make sure that a valid SSL certificate is installed. Otherwise, slower UI performance can occur.
If you do not have a valid SSL certificate to install, you need a self-signed certificate.
If neither a valid SSL certificate nor a self-signed certificate is present, Cisco CMX Analytics might not work as expected.
For information on installing a certificate, see the “Importing Certificates” section in the Cisco Connected Mobile Experiences Configuration Guide for this release at: https://www.cisco.com/c/en/us/support/wireless/connected-mobile-experiences/products-installation-and-configuration-guides-list.html
If you must change the time zone setting—for example, it was incorrectly set or the Cisco CMX server is moved to a location in another time zone or is used to manage a new location in a different time zone—know that you will not be able to accurately view analytics data from the previous time zone. Therefore, change the time zone if you also do not need the previous analytics data.
Note We strongly recommend using the Cisco CMX CLI, not Linux commands, to change the time zone setting.
Cisco 3375 Appliance and Cisco MSE 3365 (physical appliance) |
A value that exceeds 500 can cause network latency and you might observe a drop in notifications. To reduce this value, configure the notification to send fewer updates (for example, send updates for only specific floors) or use a movement notification that only sends updates when a device moves a certain distance.
Note (CSCvi48997) Make sure to enable TCP acknowledgments (ACKs) on the receiving end for northbound notifications.
This is because the Cisco CMX agent cannot start the Matlab package. Use the following commands to resolve this:
Blocked writes to the Cassandra database can result in errors in Cisco CMX, such as this analytics error message:
You can prevent untimely memtable flushes by scheduling the flush during off-peak hours and running the /opt/apache-cassandra-2.1.13/bin/nodetool flush command.
If an imported floor map image is not an RGB/Truecolor image, Cisco CMX might take longer to prepare its image tiles, causing the floor map image to not display immediately after being imported. While the tiling process is in progress, the Detect and Locate window displays this warning message: This image is currently being processed, it will be ready for viewing shortly
.
The average time for a failover condition is 7 minutes, depending on your systems.
The failback time is dependent on the amount of data to resynchronize. For example, for 5 GB of data, the expected time for failback to complete is 1.5 hours.
Note If HA is configured, first disable HA and then turn off the Cisco CMX services.
ERROR com.cisco.mse.matlabengine.heatmap.BaseMatlabHeatmapBuilder - MatlabHeatmapBuilder#createApInterfaceHeatmap Number of heavy walls used by Matlab: <nn> not equal to count reported by Java: <nn> during heatmap calculation for AP Interface: 88:f0:31:08:06:70-5.0-2
.
The heatmaps are correctly generated and stored.
This error occurs because MATLAB only counts heavy walls for location calculation, while Java counts all obstacles on the floor map.
– Bluetooth Paging Inquiry—A Bluetooth discovery (802.11b/g/n only)
– Bluetooth Sco Acl—A Bluetooth link (802.11b/g/n only)
– Generic DECT—A digital enhanced cordless communication (DECT)-compatible phone
– Generic TDD—A time division duplex (TDD) transmitter
– Generic Waveform—A continuous transmitter
– Microwave—A microwave oven (802.11b/g/n only)
– Canopy—A canopy bridge device
– Spectrum 802.11 FH—An 802.11 frequency-hopping device (802.11b/g/n only)
– Spectrum 802.11 inverted—A device using spectrally inverted Wi-Fi signals
– Spectrum 802.11 non std channel—A device using nonstandard Wi-Fi channels
– Spectrum 802.11 SuperG—An 802.11 SuperAG device
– Spectrum 802.15.4—An 802.15.4 device (802.11b/g/n only)
– Video Camera—An analog video camera
– WiMAX Fixed—A WiMAX fixed device (802.11a/n/ac only)
– WiMAX Mobile—A WiMAX mobile device (802.11a/n/ac only)
– XBox—A Microsoft Xbox (802.11b/g/n only)
For the data to match, set the Dwell Threshold filter either to 0 Minutes To 24 Hours or to No filter, and then check the Include stationary devices check box.
Note these considerations about Analytics PDF reports on Cisco CMX:
– Scheduled PDF reports, which have widgets that use the table view and have a large number of rows, do not display long tables. Pages containing long tables appear blank.
To view a PDF report with long tables, we recommend that you use the direct PDF download instead of a scheduled PDF report.
– Adobe Acrobat Reader DC has a limit of pages being 200 in. and does not display tables that go over this limit. If a table in the report is larger than this limit, you will not be able to view it using Adobe Acrobat Reader DC. Other viewers without this limit, such as Chrome, do not have this problem.
– Large tables, even if they do not reach the 200 in. limit might not be immediately viewed on Adobe Acrobat Reader DC. This can be remedied by enabling the Show large images and Show art, trim, & bleed settings. To do this, select to Edit > Preferences > Page Display > Page Content and Information. Check the check boxes next to Show large images and Show art, trim, & bleed settings. Click Confirm. You will sometimes need to uncheck the check boxes, confirm, go back, check them again, and confirm.
Cisco CMX cannot calculate the location of clients associated to a filtered SSID and thus cannot track them. The Global location indicates that Cisco CMX is not able to determine the client’s location.
1. From Prime Infrastructure, remove all zones from the maps that you want to export to Cisco CMX.
2. Import the updated zone maps from Cisco Prime Infrastructure to Cisco CMX.
3. From Cisco CMX, select Manage > Locations, and then click the Tags icon located at the top right corner of the window. This displays the Location Tag Manager window.
4. From the Location Tag Manager window, create tags for the zone maps.
– Cisco Prime Infrastructure Release 3.2 supports either Cisco CMX or Cisco MSE, but it does not support both at the same time.
– Only data is synchronized between Cisco Prime Infrastructure and Cisco CMX. Changes to maps are not synchronized.
1. Enter the cmxctl stop –a command to shutdown the Cisco CMX services.
2. Enter the cmxctl start command to restart the services.
If you need to change the IP addresses of your primary or secondary Cisco CMX servers configured with the High Availability (HA) feature, follow these steps:
1. From the Cisco CMX CLI on the primary server (as cmxadmin user), enter the cmxha config disable command to disable HA on servers.
2. Enter the cmxctl stop -a command to shut down the Cisco CMX services.
3. Enter the cmxctl status command to verify that the Cisco CMX services are not running.
If the services are still running, enter the cmxos kill command to shut down the services, and then enter the cmxctl status command to verify the services are not running.
4. Edit the Cassandra YAML files to update the seeds information with the correct IP address:
/opt/cmx/sw/confd/templates/cassandra.template.yaml
/opt/cmx/etc/cassandra/cassandra.yaml
5. Verify the changes to the YAML files by using these command:
egrep -i "listen_address|seeds" /opt/cmx/etc/cassandra/cassandra.yaml
egrep -i "listen_address|seeds" /opt/cmx/sw/confd/templates/cassandra.template.yaml
6. Enter the cmxctl start command to start the Cisco CMX services.
7. From the Cisco CMX CLI on the primary server (as cmxadmin user), enter the cmxha config enable command to re-enable HA on the servers.
On Apple iPads, The custom portal page appears twice before authentication is successful.
[object Object]
is also displayed.With VMware vSphere ESXi 6.5 and VMware vSphere ESXi 6.5 Update 1, the deployment options are not displayed.
We recommend that you also clean up Redis, if high memory usage occurs:
2. cmxctl config analytics cleanRedis
3. cmxctl config qlesspyworker cleanRedis
Note As of Cisco CMX Release 10.4.1-15, the feature flags setting is disabled by default. If your system is running an earlier release of Cisco CMX, we recommend that you disable the feature flags setting.
To disable the feature flags setting, enter these commands:
With Cisco CMX Release 10.5.1 or later, Cisco CMX relies on WLC notification (INFO messages) to populate the SSID list. This means for an SSID to appear on Cisco CMX, the SSID must have clients associated to it. This new way of retrieving SSIDs is independent of maps on Cisco CMX. This behavior change is applicable for both Location and Analytics SSID filters on Cisco CMX.
The Bug Search Tool (BST), which is the online successor to the Bug Toolkit, is designed to improve the effectiveness of network risk management and device troubleshooting. The BST allows partners and customers to search for software bugs based on product, release, and keyword, and aggregates key data such as bug details, product, and version. The tool has a provision to filter bugs based on credentials. Perform the following task:
1. Access the BST (using your Cisco user ID and password) at:
https://tools.cisco.com/bugsearch/
2. Enter the bug ID in the Search For: field.
Note Using the BST, you can also find information about the bugs that are not listed in this document.
Use the BST to view the details of the caveats listed in this section. For more information about the BST, see the “Cisco Bug Search Tool” section.
Use the BST to view the details of the caveats listed in this section. For more information about the BST, see the “Cisco Bug Search Tool” section.
Use the BST to view the details of the caveats listed in this section. For more information about the BST, see the “Cisco Bug Search Tool” section.
Cisco Support Community is a forum for you to ask and answer questions, share suggestions, and collaborate with your peers. Join the forum at https://supportforums.cisco.com/index.jspa.
Get Cisco CMX Cloud support at: https://support.cmxcisco.com/hc/en-us
For additional information on Cisco CMX, see:
To receive timely, relevant information from Cisco, sign up at Cisco Profile Manager.
To get the business impact you’re looking for with the technologies that matter, visit Cisco Services.
To submit a service request, visit Cisco Support.
To discover and browse secure, validated enterprise-class apps, products, solutions and services, visit Cisco Marketplace.
To obtain general networking, training, and certification titles, visit Cisco Press.
To find warranty information for a specific product or product family, access Cisco Warranty Finder.
Cisco Bug Search Tool (BST) is a web-based tool that acts as a gateway to the Cisco bug tracking system that maintains a comprehensive list of defects and vulnerabilities in Cisco products and software. BST provides you with detailed defect information about your products and software.