Cisco Cisco 3365 Mobility Services Engine White Paper
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 52 of 55
Common Questions and Starting Points for Resolution
This section presents a set of known problems people have encountered in configuring and running Cisco CMX
Location Analytics. The section lists the high-level observation of the problem and then suggests possible causes
and ways to check or validate these possibilities.
Problem: No User Interface Is Available
This problem generally occurs because the Cisco CMX Location Analytics application is not up and running.
●
Verify that the analytics application is running from Cisco Prime Infrastructure.
●
If it is not running, then enable it in Cisco Prime Infrastructure.
●
If the analytics application cannot be enabled using Cisco Prime Infrastructure, go to the command-line
interface (CLI) and stop and start the application and look for any error messages:
/opt/mse/analytics/bin/analyticsServiceManager.sh stop
/opt/mse/analytics/bin/analyticsServiceManager.sh start
chown -R nobody:nobody /opt/mse/analytics" after every start
●
Check update.log.0 for error messages related to preparation of the user interface content.
Problem: Cannot Log into Application
●
Verify that the Oracle database is running:
ps ax| grep oracle
●
If the database is running, verify that the username and password are set correctly in Cisco Prime
Infrastructure.
Problem: No Data Is Available
●
This problem can occur because one of the links in the chain is not working. Check all links in order.
●
Verify that history is enabled.
●
If yes, verify that the analytics application is running.
●
If yes, verify that tracking is enabled in Cisco Prime Infrastructure.
●
If yes, verify that clients are being seen through Cisco Prime Infrastructure for the building and floors
expected.
●
If yes, verify that the mse.log.0 file is current and contains paths written to the database from the Cisco
MSE download:
/opt/mse/logs/analytics/mse.log.0
Problem: Floors Are Seen, but Are Black
●
This problem may occur if the floor image size is too large for the application to handle. Typically, images
larger than 1 MB can cause problems.
●
Check image sizes. Images are stored in /opt/mse/analytics/jboss-as-7.1.1.Final/images/. To check the
size, enter the following command to list the images with their sizes:
ls –la /opt/mse/analytics/jboss-as-7.1.1.Final/images/*.jpg
If the image size is too large, you can change the maximum pixel dimension of any image in the mse.properties
file. This file is located at /opt/mse/analytics/intellify/tools/MSEclient.