Cisco Connected Mobile Experiences (CMX) Analytics 8.0 FAQ What is CMX Analytics? Cisco’s CMX Location Based Analytics takes anonymous device location data gathered by the Cisco Mobility Services Engine’s (MSE) Base Location Service, and leverages that data to provide clear, concise and relevant information. For example, how many people are using the Wi-Fi network or on which floor are people spending the most time. It is a historical location reporting tool and it does take a few hours to aggregate all the received location data and information and to complete its calculations. There are 2 types of data sources that can be used by CMX Analytics: • Location Based Analytics Data • Presence Analytics Data (introduced in MSE 8.0)
At least 3 access points (APs) are required for CMX Location Based Analytics to be rendered with a degree of accuracy. Presence Analytics is used to determine device location on the basis of the closest Wi-Fi access point. A single AP is required to calculate presence and dwell time for clients. Multiple APs can be supported per site but only the strongest AP is used. All reports are supported in Presence Analytics except for movement between zones.
The 2 types of Analytics can be run at the same time and the same Analytics Dashboard is used for location and presence reporting.
Please refer to the CMX Analytics Configuration guide http://www.cisco.com/c/en/us/td/docs/wireless/mse/8-0/CMX_Analytics/Guide/CMX_Analytics_Guide.html
What are the requirements for CMX Analytics? • A well-tuned Cisco Wireless Network o Now is a good time to revisit and recalibrate an existing wireless network. Consult o http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Mobility/WiFiLBS-DG.html and o http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Mobility/emob73dg/emob73/ch3_WLAN.html • Cisco Prime Infrastructure (PI) release 1.4.2 or 2.1 available with accurate floor maps and any TAC recommended patches. • Zones of interest are defined in PI floor maps when using Location Based Analytics • Time and care should be taken to plan and define zones of interest • Tracking and history are enabled when using Location Based Analytics (see question below) • This is not mandatory when using Presence Analytics • At least 1 Presence Site is defined in the Presence Analytics page of the MSE if using Presence Analytics • https:// <MSE_IP>//ui/#settings • This is not mandatory when using Location Analytics • Base Location Services and CMX Analytics are running • CMX Ordering and Licensing • http://www.cisco.com/c/en/us/products/collateral/wireless/mobility-services-engine/data_sheet_c07-473865.html Where can I find Tracking and History Parameters? • In Prime Infrastructure • Services > Mobility Services Engines > MSE-180 > Context Aware Service > Administration > Tracking Parameters
• Services > Mobility Services Engines > MSE-180 > Context Aware Service > Administration > History Parameters
Or • In the MSE administrative web interface • https://<MSE_IP>/settings/trackingParams after logging in
• https://<MSE_IP>/settings/historyParams after logging in
How do I start or stop CMX analytics? Access the MSE Administrative web interface (https://<MSE name or IP Address>/mseui/) with the appropriate credentials. Slide the Status button to “Up” or “Down” in the CMX Analytics tab of the Services pane.
You can also use Cisco Prime Infrastructure to start or stop CMX Analytics and view the Service Status. In the Classic Theme: • Service -> Mobility Services Engines then click on the MSE link In the Lifecycle Theme • Design -> Mobility Services Engines then click on the MSE link Then click the check box beside CMX Analytics and click the Save button.
Notes: - The Mobility Services Engine (MSE) needs to be added to Cisco Prime Infrastructure (PI), - If only Analytics is running on the MSE do not synchronize the MSE with any wireless controllers (WLC) in Cisco Prime Infrastructure (PI). This is the case in a dual MSE configuration with 1 MSE for Base Location Services (CAS) and 1 MSE for CMX Analytics. - Make certain that the Base Location MSE IP address is set in the CMX Analytics Setup page (https://<MSE name or IP Address>/settings/casAnalyticsSetup)
How do I access the CMX Analytics web interface? You can access the CMX analytics UI at the following URL: https://<MSE_name or MSE_IP_Address>/ui/ with the appropriate credentials.
What are the CMX Analytics web interface and MSE administrative web interface username and password? The setup script during the installation of the MSE requires that the Prime Infrastructure (PI) admin password be changed. This PI admin user and password are the same username and password used by the CMX analytics UI and the MSE administrative UI. The default admin username is “admin”. The password is set during installation. You access the installation /setup script at /opt/mse/setup/setup.sh.
How do I configure, change, or add the username and password for the CMX Analytics web interface? Access the MSE Administrative web interface at the following URL: https://<MSE_name or MSE_IP_Address>/mseui/ with the appropriate credentials. Click on CONFIGURATION in top right hand corner and then click on “Users” under ACCOUNTS in the left hand column. Alternatively, you can access the Users page directly: https:// <MSE_name or MSE_IP_Address>/settings/users after logging in. Click on the “Add User” button or click on the username to edit an existing user.
How do I configure, change, or add user groups? Access the MSE Administrative web interface at the following URL: https://<MSE_name or MSE_IP_Address>/mseui/ with the appropriate credentials. Click on CONFIGURATION in top right hand corner and then click on “Groups” under ACCOUNTS in the left hand column. Alternatively, you can access the Groups page directly: https:// <MSE_name or MSE_IP_Address>/settings/groups after logging in. Click on the “Add Group” button or click on the group name to edit an existing group. However, we do not currently recommend the use of READ ONLY groups. How do I get the status of CMX from command line? Use the command “service msed status” or “getserverinfo” to get the status of the MSE and its services.
Verify that the CMX Analytics service is “Enabled” and “Up”. How do I verify the health of the MSE and CMX? Go to https://<MSE_name or MSE_IP_Address>/health/.
When do I split the mobility services across 2 different MSEs? Especially Base Location (CAS) service and CMX Analytics service. As soon as an MSE is receiving data from more than 1000 end devices, splitting the Base Location (CAS) and CMX Analytics services onto 2 different MSEs should be considered. When the Base Location (CAS) and CMX Analytics services are running 2 different MSEs, how do I sync the CMX Analytics MSE to the Base Location (CAS) MSE? On the Analytics MSE, click on CONFIGURATION in top right hand corner, then click on “CMX ANALYTICS” in the left hand column, click on “Setup”, and then click on the existing IP address or click on “Add Context Aware MS” in top right hand corner. Alternatively, you can directly access the CMX Analytics setup page on the Analytics MSE: https://<Analytics_MSE_name or Analycis_MSE_IP_Address>/settings/casAnalyticsSetup How does licensing work when splitting services? Please consult the Ordering and Licensing Guide http://www.cisco.com/c/en/us/products/collateral/wireless/mobility-services-engine/data_sheet_c07-473865.html. Troubleshooting I can get to the MSE administrative web interface but not the CMX Analytics web interface, how come? If you go to the CMX analytics web interface (https://<MSE_name or MSE_IP_Address>/ui/) and get the following message: “Service Unavailable The server is temporarily unable to service your request due to maintenance downtime
or capacity problems. Please try again later.”
then the analytics service has not been started. To view the CMX Analytics web interface, you must first have the CMX Analytics service started (see above). If your deployment contains 2 MSEs with 1 MSE configured for Base Location Services (CAS) and 1 MSE configured for CMX Analytics, make sure you are accessing the correct MSE. I've started analytics for the first time. How long should I wait before using the UI? It usually takes analytics ~1-1.5 hours after the first start before the user can run queries from the Analytics UI. Why is CMX Analytics not showing any data? Make sure that the MSE is: • Tracking wireless clients o In the MSE administrative web interface under "Settings" >> "Context Aware Service" >> "Tracking" o In the PI administrative web interface • Logging historical transactions for client stations o In the MSE administrative web interface under "Settings" >> "Context Aware Service" >> "History" o In the PI administrative web interface • See “Where can I find Tracking and History Parameters?” in the previous pages • Monitor /opt/mse/logs/analytics/mse.log.0 to make sure that analytics is downloading points/paths from location history. How frequently does CMX Analytics process data from the location service? Analytics gets location history from MSE Location database for every 15 minutes. Why does the CMX Analytics web interface not show floor maps? • You probably have not synchronized the MSE with floor maps. o on PI. Go to "Services" >> "Synchronize Services" o on PI. Select appropriate floor maps and synchronized with your MSE • The map or maps may be too large. o Reduce the map file size. Why is the data on CMX Analytics not in the same timezone? Make sure that your MSE is configured in the correct timezone using the setup script on the MSE (/opt/mse/setup/setups.sh) Why is the CMX Analytics Reports time displayed incorrectly? The CMX Analytics Reports time is set in the /opt/mse/analytics/intellify/tools/MSEclient/mse.properties file.
- options, see http://joda-time.sourceforge.net/timezones.html
timezone=America/Los_Angeles Change the value to the desired time zone. The time zone definitions can be found at http://joda-time.sourceforge.net/timezones.html.
No CMX Analytics data is available, what are the troubleshooting steps? The following should be checked in order: 1. Verify that tracking is enabled in PI or in the MSE Administrative web interface. 2. If yes, then verify that there are clients being seen through the Prime Infrastructure map for the building/floor expected. 3. Verify that history is enabled. 4. If yes, then verify that CMX Analytics is running. 5. If yes, then verify the /opt/mse/logs/analytics/mse.log.0 file is current and contains paths written to the database from the MSE processing.
Why are the maps black or very slow to load? This is possibly because the floor map images size is too large for WebGL to handle. Typically images over 1MB can cause issues. Check image sizes. • Images are stored in /opt/mse/analytics/jboss-as-7.1.1.Final/images/ • To check size ls –la /opt/mse/analytics/jboss-as-7.1.1.Final/images/*.jpg • If the files are too large, change the maximum pixel dimension of any image in the /opt/mse/analytics/intellify/tools/MSEclient/mse.properties file. o Set max-dimension=4096 or max-dimension=8192
Why are the maps not seen in 3D? • Verify that the floor is synched between the controller and the MSE. • Verify that the image files are being accessed via updater.log. o /opt/mse/logs/analytics/update.log • Verify the size of the image files o If the files are greater than 1MB this can be an issue.
Why are buildings missing from the menu? • Verify that the building is synched between the controller and MSE.
Why are zones not appearing? Zones are created as coverage areas in Prime Infrastructure. • Verify that they exist on for the building and floor o Note that a floor is by default designated as a zone. • Verify the update.log.0 to see if they are being uploaded. o /opt/mse/analytics/logs/update.log
Why does CMX Analytics take so long to run? This happens when the MSE is busy, usually with other location services. 1. Go to the CLI and check the running processes to see if any if above 100% by using “ps” or “top” 2. If so, it is worth considering the option below. On MSE’s with many clients, the workload can be quite high to also process Analytics. The solution can be to move the Analytics to a separate MSE with less services or location traffic Why are the points outside the floor? Points may be expected outside the building when on the ground floor, as the APs may detect points there. This is not necessarily a problem. If this is on an upper floor, then the points may have been inaccurately placed. 1. Are points outside on the ground level? 2. If yes, then either create an outside zone or create an inclusion area. 3. If the points are on higher floors then create an inclusion zone for that floor so that points are pushed back inside Why are location results not where expected? 1. Verify that the location is set correctly in Prime Infrastructure by looking at where the clients are placed. 2. Are points shown outside the building where the floor is above ground level? 3. If yes, consider putting inclusion region in Prime Infrastructure 4. If not, are the devices also shown outside the building through Prime Infrastructure? 5. If yes, then PI needs recalibrating What are the expected times for the different changes to propagate? When analytics is configured or changes made to the network, there is often an elapsed time before the end result can be seen. Many of the processes for updating are based on timers so it is not always apparent how long it will take. The table below gives some guidance on how long to wait given some change. Table 1: Expected Times for Changes to Propagate Change/Situation Time to see it reflected through the UI Comments Startup with no data >1hr 15min One path needs to be complete and written to the database and then reflected in the UI Startup with restored database A few minutes Defining a new zone/coverage areas About 90min Data soonest written after 60minutes plus 15 min polling time, plus 15 minutes to refresh the server side cache with building parameters. Note: the old coverage areas will still be there in the menus as long as they are referenced in the database. Currently can only delete data to get rid of them Add new floor About 90min or 5hrs 30min If we restart the Analytics service it will refetch the building parameters and take 90 minutes for the new data to appear. Else, the system reloads the building parameters every 4 hours Data retrieved from the MSE database Every 15minutes This is the default and can be set in the mse.properties file Building characteristics refreshed for UI Every 15 minutes Useful Links
CMX Analytics Configuration guide http://www.cisco.com/c/en/us/td/docs/wireless/mse/7-6/CMX_Analytics/Guide/CMX_Analytics_Guide.html
Wi-Fi Location-Based Services 4.1 Design Guide http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Mobility/WiFiLBS-DG.html
WLAN RF Design Considerations http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Mobility/emob73dg/emob73/ch3_WLAN.html
MSE Ordering and Licensing Guide http://www.cisco.com/c/en/us/products/collateral/wireless/mobility-services-engine/data_sheet_c07-473865.html