Release Notes for Cisco Connected Mobile Experiences (CMX), Release 10.4.0 and Later

Release Notes for Cisco CMX Release 10.4.x

---

First Published: November 27, 2017

Last Modified: June 16, 2020

This document describes what is new and important in Cisco Connected Mobile Experiences (Cisco CMX) Release 10.4.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.

• Use faceted search to locate content that is most relevant to you.
• Create customized PDFs for ready reference.
• Benefit from context-based recommendations.

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.

Contents

• Introduction to Cisco CMX Release 10.4.x
• What’s New
• Supported Platforms
• Requirements
• Licensing Information
• Upgrading Information
• Important Notes
• Caveats
• Cisco Support Community
• Related Documentation
• Communications, Services, and Additional Information
• Cisco Bug Search Tool

Introduction to Cisco CMX Release 10.4.x

Cisco CMX Release 10.4.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:

• Detect & Locate
• Analytics
• Presence Analytics
• Connect
• Hyperlocation
• Fast

This release is not suitable for deployments where the following are required:

• Cisco Adaptive Wireless Intrusion Prevention System (aWIPS) feature
• Federal Information Processing Standard (FIPS) FIPS deployment

What’s New

 

 

 

 

Supported Platforms

Cisco CMX Release 10.4.x can be installed on the Cisco MSE 3365 platform.

---

Note Cisco CMX Release 10.4.x and later does not support the Cisco MSE 3355 platform.

Cisco CMX Release 10.4.x can be installed as a Virtual Cisco MSE appliance, which requires either VMware ESXi 5.1 to ESXi 6.5 versions, or Microsoft Hyper-V. 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/connected-mobile-experiences/products-installation-guides-list.html

Table 5 lists the Cisco CMX Release 10.4.x hardware guidelines for a virtual Cisco MSE appliance, such as VMWare or Microsoft Hyper-V. 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

 

Requirements

---

Note ● Before you deploy Cisco CMX, we strongly recommend that you refer to the VM sizing guidelines described in the Cisco CMX Dimensioning Calculator at: http://calculator.cmxcisco.com/aspnet_client/system_web/2_0_50727/CMX_calculator_v2.07/CMX_calculator_v2.07.aspx

• For information about system scaling, 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

 

• Cisco CMX Release 10.4.x (which includes Cisco CMX Location, Connect, and Configuration APIs) has been tested using Google Chrome up to version 63.

---

Note If you are using Google Chrome version 72 or above, we recommend that you use Mozilla Firefox as your browser, or downgrade to Google Chrome version 63.

• Cisco CMX supports input and output only in English.
• For compatibility information, see the “Cisco Connected Mobile Experiences (CMX) Compatibility Matrix” section in the Cisco Wireless Solutions Software Compatibility Matrix at: https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html
• (CSCvf91346) Cisco CMX Release 10.4 provides feature parity when using Cisco Prime Infrastructure (PI) Release 3.2 with Cisco PI Release 3.2 and Cisco MSE Release 8.0:

---

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.

 

1.Requires Cisco CMX Release 10.4 or later and Cisco Prime Infrastructure Release 3.2 or later.

Licensing Information

 

• The Cisco CMX Evaluation License provides full functionality for a period of 120 days. The countdown starts when you start Cisco CMX and enable a service.

Two weeks before the evaluation license expires, you will receive a daily alert to obtain a permanent or term 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 or term license and regain access to it.

• The Cisco CMX Base License no longer provides access to Cisco CMX Hyperlocation or Partner Stream. The Cisco CMX Advanced License is required to access these services.
• Cisco CMX now includes license changes that warn that the use of Cisco Hyperlocation capabilities requires the Cisco CMX Advanced License. If you have any questions about licensing, contact your Cisco account team.
• The High-Availability feature on Cisco CMX Release 10.4.x is part of the Cisco CMX Release 10.4.x “CMX Base” license, which you would install on the primary HA server. The secondary HA server automatically receives a copy of the Cisco CMX license during sync up. There is no HA-specific license to install.
• You can add any license file from Cisco CMX Release 10.0 or later to Cisco CMX Release 10.4.x.
• For information about procuring Cisco CMX licenses, see the Cisco Connected Mobile Experiences (CMX) Version 10 Ordering and Licensing Guide for this release at: https://www.cisco.com/c/en/us/solutions/collateral/enterprise-networks/connected-mobile-experiences/guide-c07-734430.html
• For information about adding and deleting licenses, see the “Managing Licenses” 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

Upgrading Information

---

• Downgrading from Cisco CMX Release 10.4.x to any release is not supported.
• Anticipate an increase in the client count if you upgrade from Cisco CMX Release 10.2.1 to Cisco CMX Release 10.3.0 (CSCux31137) or if you upgrade from Cisco CMX Release 10.2.3 to Cisco CMX Release 10.3.0 (CSCvd15253). This is due to the way Cisco CMX Release 10.3.0 counts visits to different areas. For more details, see the Analytics Documentation that is available from the UI on Cisco CMX Release 10.3.0.
• There are three ways to upgrade from Cisco CMX Release 10.x to Cisco CMX Release 10.4.x:

– Option 1: Copy the Cisco CMX image to the Cisco CMX node, and then use the cmxos upgrade < cmx-file > command from the command line to perform the upgrade.

– Option 2: Use the web installer on port 1984, and choose Remote File to download the Cisco CMX image from a hosted site, for example, the Cisco CMX image could be placed on an internal web server for the download.

– Option 3: Use the web installer on port 1984, and choose Local File to upload the Cisco CMX image from your local machine through the web browser.

---

Note We recommend that you use Option 1.

With Option 3, the upload of the Cisco CMX image might fail. This is due to a memory leak in a third-party library used in the installer. However, this library is fixed in subsequent versions of the installer.

However, if you chose Option 3 and the upload fails, restart the installer program by using the cmxos adminui stop command and then the cmxos adminui start command. Option 3 might succeed after several tries.

• For information about upgrading from an earlier Cisco CMX release to a later release, see the applicable to Cisco Mobility Services Engine Virtual Appliance Installation Guide for Cisco CMX at: https://www.cisco.com/c/en/us/support/wireless/connected-mobile-experiences/products-installation-guides-list.html
• For information about upgrading from Cisco MSE Release 8.x to Cisco CMX Release 10.x, see the applicable Release Notes for Cisco Mobility Services Engine, Release 8.0.x at: https://www.cisco.com/c/en/us/support/wireless/mobility-services-engine/products-release-notes-list.html

– We recommend that you run Cisco CMX Release 10.4.x 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.4.x.

Important Notes

• Cisco CMX Release 10.4.x supports the Cisco Mobility Express wireless network solution.
• Cisco CMX requires interaction with Cisco Prime Infrastructure only during the initial installation stage. After the maps and controllers are imported, Cisco CMX and Cisco Prime Infrastructure do not have any run-time dependencies.
• Do not use Internet Explorer 8.0 to edit the Cisco Wireless Controller's (WLC) SNMPv3 credentials. Use Google Chrome 50 to 63.
• The Cisco FlexConnect feature does not support DNS ACL and as such you cannot use DNS ACLs when configuring Cisco CMX Connect and Engage.
• The SSL mode is enabled by default.

– To use the Cisco CMX Connect portal page in HTTP, disable the SSL mode by entering the cmxctl node sslmode disable command.

– If SSL is enabled and you enable HTTPS for Cisco CMX Analytics (generally, Cisco CMX as a whole), make sure that a valid SSL certificate is installed. Otherwise, slower UI performance will 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
• Observe disk space utilization by going to the Overall Disk Usage section in Metrics from the Systems tab. For information about increasing hard disk space, see the “Increasing the Hard Disk Space” section in the “Performing Administrative Tasks” chapter 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
• When more than 85 percent of the disk space is consumed, all the Cisco CMX services shut down. For information about how to care of this issue, see the “Troubleshooting Cisco CMX Server Shutdown Problems” section in the “Performing Administrative Tasks” chapter 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
• Accuracy results for Cisco FastLocate are reflected in the Cisco CMX Accuracy Tool under the 50% Error Distance column. Accuracy is considered good if the distance displayed under those columns is 10 m or less, meaning the client will be detected less than 10 m from its actual position. For information on how to configure Cisco FastLocate, refer to the “FastLocate for Cisco Wave 2 Access Points” section in the Cisco Wireless Controller Configuration Guide, Release 8.6 : https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-6/config-guide/b_cg86/location_services.html#ID2048
• When the probing filter is enabled, Cisco CMX tracks up to 90,000 devices, including associated and probing devices. Tracking beyond this recommended limit can cause Cisco CMX to overload.
• While using v3 client APIs, Cisco CMX supports up to 6 unique IP addresses per second and 54 unique MAC addresses per second.
• (CSCvg23023) Cisco Hyperlocation cannot be enabled from two Cisco CMX instances on the same Cisco WLC.
• (CSCva36827) With Cisco CMX Release 10.4.0 and later, Cisco CMX users should transition to using the /api/location/v3/clients API. You must use the Cisco CMX CLI to configure your username and password to access this API.
• (CSCvc36715) We recommend that you monitor your northbound notifications. The Send rate per second can be monitored with the /api/config/v1/notifications/stats API. The one minute rate should be less than 500 per second.
• (CSCvc44074) Cisco CMX tracks up to 90,000 devices. Tracking beyond this recommended limit can cause an outage of the Cisco CMX Analytics service. If this occurs, restart Cisco CMX after the number of tracked devices decrease to less than 90,000 devices.
• (CSCvc89944) If the hostname of Cisco CMX is changed using the cmxos reconfigure command, and then changed back to localhost.localdomain, the following error is displayed:

This is because the Cisco CMX agent cannot start the Matlab package. Use the following commands to resolve this:

cmxctl stop -a

cmxctl agent start

cmxctl start

• (CSCvc94895) Cisco CMX supports Google Earth coordinates on imported maps from Cisco Prime Infrastructure. Use the Cisco CMX /api/config/v1/maps/ REST API to verify the GPS coordinates on Cisco CMX floor maps, and then use the Cisco CMX /api/location/v3/clients REST API to check that the GPS coordinates are available for the devices. For information about adding GPS markers, see the Cisco Prime Infrastructure documentation.
• (CSCvd17090) In Cisco CMX Release 10.3.0, the dwell-time calculation is improved to provide a more accurate total duration value. The dwell time is now based on the median values of the different types of visits (repeat or new, and associated or probing). For more information, see the Analytics Documentation and Definitions Online Help available in the Cisco CMX user interface. Choose Documentation from the admin drop-down list, and then click Analytics Documentation and Definitions.
• (CSCvd17114) Cisco CMX uses the Apache Cassandra database to store location history, raw visits for the Analytics service, and user statistics for the Connect service. Cassandra provides fast read and write performance by writing its data to a memcache, which is periodically written to disk. When the memtable contents exceed a configurable threshold, the memtable data, which includes indexes, is put in a queue to be flushed to disk. If the data to be flushed exceeds the queue size, Cassandra blocks writes until the next flush succeeds. Note that the timing of such memtable flushes would vary from installation to installation.

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.

• (CSCvd21695) Image tiling can take a few seconds to complete if images need to first be converted to RGB. Once the tiling completes, the image properly displays on the user interface.

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 & Locate window displays this warning message: This image is currently being processed, it will be ready for viewing shortly.

• (CSCvd29399) In Cisco CMX Release 10.3.1, the Compare Data to and the Hourly Trend views shown on Analytics > Realtime were removed.
• Initial HA configuration is dependent on data size. For example, for 5 GB of data, initial configuration could take up to 1 hour to complete.

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.

• (CSCvd35578) When you import a new or existing map containing zones from Cisco Prime Infrastructure to Cisco CMX, make sure that you check the Delete & replace existing zones check box. Even if you are updating a map that was previously imported, check the Delete & replace existing zones check box.
• (CSCvd41641) Data loss will occur with the Cassandra database when restoring data with Cisco CMX Release 10.2.3 and earlier. We recommend upgrading to and using Cisco CMX Release 10.3.0 to successfully restore data from a previously made backup.
• For backup and restore information, see the “Performing Administrative Tasks” chapter 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
• (CSCvd53632) Restoring Cisco CMX data must be done on a device that has the same local time as the device from which the data is collected. Otherwise, you will not be able to correctly access the analytics data. In addition, the data will result in errors or zero values on reports.
• (CSCvd73907) In certain situations, such as high traffic for the day, all visitors for that day, including new ones, are added to the collection of repeat visitors before the data for that day has been aggregated completely. This results in the visitor count showing 100% repeat visitors for that day.
• (CSCvd80519) Starting from Cisco CMX Release 10.3.1, you can use the cmxctl config analytics setNumMonthsRepeatHistory < number > command to change the number of months of repeat history used and maintained by the Cisco CMX Analytics service. You do not need to restart Cisco CMX for the change to take effect.

---

Note If you change the repeat history setting, existing history will be deleted.

• (CSCve05677) Cisco CMX Release 10.2.x and later uses the default Cisco 3365 Mobility Services Engine (MSE) power and fan settings displayed from the Cisco Integrated Management Controller (CIMC) interface.The default power and fan settings can vary, based on the installed Cisco MSE firmware. The current firmware version has these default power and fan settings:

– Power setting is Power On

– Fan setting is Balanced

• (CSCve13731) Use the System > Presence Metrics window and the System > Metrics > System Summary window to understand the overall Cisco CMX system health. Changes in normal patterns, such as unusual spikes, could indicate network issues.

– The P resence Metrics window displays the number of clients being tracked and the number of clients reported with locally administered MAC addresses.

– The System Summary window displays metrics that mainly describe the incoming message rate, data persistence rate, and so on.

• (CSCve15152) If the Analytics report uses the Summary view with the This Week time frame option, the Daily Trend chart will only show data points for the days of the week that have been completed. For example, on Monday, no data points will appear on the Daily Trend chart because Monday is considered the first day of the week and the day has not yet completed. If you want to display a breakdown of the data for the day, use the Chart or Table view to display details by a different granularity.
• (CSCve19090) If you perform an online backup of a Cisco CMX server, the backup might fail if a change to the system occurs during the backup. If a backup fails, try again during an off-peak period when there is low activity on the server. If the backup still fails, turn off the Cisco CMX services and then perform the backup offline.

---

Note If HA is configured, first disable HA and then turn off the Cisco CMX services.

• (CSCve24919) When generating a map report, we recommend that the number of floors that you select not exceed 100. Use tags to restrict the data gathered by the report. If you exceed the recommended amount, the report might not generate and an error message might be displayed.
• (CSCve28851) Ignore this error message:

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.

• (CSCve37513) Cisco CMX detects the same sources of interferences as the Cisco CleanAir system. For more information, see the “Configuring Cisco CleanAir on the Cisco Wireless LAN Controller (GUI)” section in the “Wireless Quality of Service” chapter of the Cisco Wireless Controller Configuration Guide, Release 8.4 at: https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-4/config-guide/b_cg84/wireless_quality_of_service.html#ID51

– 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

– Jammer—A jamming device

– 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)

• (CSCve39234) Use the cmxos sysproxy command to configure proxy settings. Do not edit the /etc/profile.d/cmxprof.sh file to configure proxy settings, because those settings will be overwritten when you upgrade Cisco CMX.
• (CSCve47829) On Cisco CMX, Redis memory is allocated based on system memory. If you try to restore data from a 64 GB machine onto a low-end 24 GB machine, downstream failures might occur.

 

 

• (CSCve51867) The Dwell Threshold setting affects the Visitors widget but does not affect the Dwell Time Breakdown widget. The Dwell Time Breakdown widget always uses the 0 Minutes To 24 Hours setting, and always includes stationary devices regardless of the report settings. Thus, the data in Visitors widget and the Dwell Time Breakdown widget might not match.

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.

• (CSCve56353) End users using Android devices are unable to open the landing page URL (Success Page) configured from Connect & Engage > Connect Experiences. In addition, the Guest Portal might also close after the end user registers. This is a known 'Redirection to Success Page' Android bug from Google. For more information, see https://support.cmxcisco.com/hc/en-us/articles/115007357987.
• (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.
• (CSCve76843) For scheduled PDF reports, there are limitations for viewing tables that have a large number of rows. These limitations do not occur for direct PDF reports that are directly downloaded.

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.

• (CSCve76843) Note these considerations about PDFs on Cisco CMX:

– Download the PDF to view extremely long tables.

– Adobe Acrobat Reader DC has a limit of pages being 200 inches, and does not display tables that go over this limit. This does not occur with other viewers such as Chrome.

– With Adobe Acrobat Reader, sometimes if you check the Show large images check box and the Show art, trim, & bleed check box on Edit > Preferences > Page Display > Page Content and Information, the changes are not saved. If this occurs, uncheck the check boxes, save, and confirm. Then, check the check boxes, save, and confirm. This problem occurs in scheduled PDF reports if you change a widget to a table view and it has a lot of rows.

• (CSCvf25629) Due to the nondeterministic nature of Wi-Fi signals from mobile devices, Cisco CMX makes a best effort in calculating and updating the location of probing wireless clients. The Wi-Fi probing behavior of each client can be different, therefore no guarantee can be made with respect to the accuracy of the client’s location. For more guidance, see the “CMX Solution Components” chapter in the Cisco Connected Mobile Experiences (CMX) CVD : https://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Borderless_Networks/Unified_Access/CMX/CMX_Components.html
• (CSCvf60571) Cisco CMX does not support VMWare tools.
• If a map is modified in Cisco Prime Infrastructure, you must import the modified map to Cisco CMX. Similar with Cisco MSE.
• Cisco Prime Infrastructure Release 3.2 does not support Cisco CMX High Availability but it does support Cisco MSE High Availability.
• Cisco Prime Infrastructure Release 3.2 does not display RFID tags. Cisco CMX displays RFID tags
• (CSCvg10317) Cisco MSE virtual machine (VM) running Cisco CMX might not function properly after being powered on after a power outage. If this occurs,:

1. Enter the cmxctl stop –a command to shutdown the Cisco CMX services.

2. Enter the cmxctl start command to start the services.

• (CSCvg23023) Cisco Hyperlocation cannot be enabled from two Cisco CMX instances on the same Cisco WLC.
• (CSCvg28274) If NMSP tunnel flapping occurs, ping an external address to check if the DNS resolution is slow. If it is slow, delete all the external DNS server entries in the /etc/resolv.conf file, except for the entry that maps to the localhost.
• (CSCvg31522) The Client Playback feature applies only to associated devices (clients). This feature is not applicable to RFID tabs because they are not associated devices.
• (CSCvg37621) The BLE beacon has the same characteristics as a wireless client. Thus, on Cisco CMX, the device appears to move around the map even though the device is considered stationary. The movement should be the same as a wireless client.
• (CSCvg48564) Note that due to CSCvg70464, synchronization problems can occur after changing the IP address and reenabling the High Availability (HA) feature. Refer to the CSCvg70464 bug details for further information.

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.

• (CSCvg68045) Cisco CMX Release 10.4.0 UI and API do not display the zone of impact for a rogue access point.
• (CSCvg72780) The Cloud Applications window displays BLE notifications only if you log in to Cisco CMX as an admin user. Otherwise, the Notifications area on the window displays as blank.
• (CSCvg81107) Notification subscriptions—manually crated in Cisco CMX Release 10.3.x through the Manage > Notifications window—for sending data to CMX Cloud applications need to be deleted and then recreated from the Cisco CMX Cloud Applications page in Cisco CMX Release 10.4.x or 10.5.x. Notification subscriptions created in Cisco CMX Release 10.3.x do not display on the Cloud Applications page.
• (CSCvj52515) There is significant overhead seen in maintaining the compact history, which allows to query the unique clients seen on a floor or zone per day. This does not affect the regular clients history that is stored in the Cassandra database.

---

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:

• The GitHub version of API version 3 is supported through the Cisco DevNet Community, not by Cisco Technical Support.

Caveats

• Cisco Bug Search Tool
• Open Caveats
• Resolved Caveats in Cisco CMX Release 10.4.1-34
• Resolved Caveats in Cisco CMX Release 10.4.1-15
• Resolved Caveats in Cisco CMX Release 10.4.1-2
• Resolved Caveats in Cisco CMX Release 10.4.0

Cisco Support Community

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

Related Documentation

For additional information on Cisco CMX, see:

• https://www.cisco.com/c/en/us/solutions/enterprise-networks/connected-mobile-experiences/index.html
• https://www.cisco.com/c/en/us/support/wireless/connected-mobile-experiences/tsd-products-support-series-home.html
• https://www.cisco.com/c/en/us/support/wireless/mobility-services-engine/tsd-products-support-series-home.html
• Cisco CMX documentation embedded in the product. From the Cisco CMX user interface, choose admin > Documentation.

Communications, Services, and Additional Information

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

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.