Cisco Cisco 3365 Mobility Services Engine 白書
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 54 of 55
Problem: Points Outside the Floor Are Detected
Points may be expected outside the building for the ground floor because the access points may detect points
there. This behavior is not necessarily a problem. For an upper floor, however, the points may have been
inaccurately placed.
●
Are the outside points on the ground level?
●
If yes, then either create an outside zone or create an inclusion area.
●
If the points are on higher floors, then create an inclusion zone for that floor so that points are pushed back
inside.
Problem: Result Locations Are Not Where Expected
●
Verify that the locations are set correctly in Cisco Prime Infrastructure by viewing the placement of the
clients.
●
Are points shown outside the building where the floor is above ground level?
●
If yes, consider adding an inclusion zone through Cisco Prime Infrastructure.
●
If no, are the devices also shown outside the building through Cisco Prime Infrastructure?
●
If yes, then you must recalibrate the map using Cisco Prime Infrastructure.
Expected Time for Changes to Propagate
When analytics processes are configured or changes made to the network, there is often an elapsed time before
the end results can be seen. Many of the processes for updating are on timers, so it is not always apparent how
long propagation of changes will take. Table 3 provides some guidance on how long to wait for changes to
propagate or other events to complete.
Table 3.
Expected Wait Times
Change or Event
Time to See Change or
Event Reflected in User
Interface
Event Reflected in User
Interface
Comments
Startup with no data
Less than 1 hour and 15
minutes
minutes
One path needs to be complete and written to the database and then reflected in
the user interface.
the user interface.
Startup with restored
database
database
Immediate
Addition of GPS markers
Less than 15 minutes
The analytics application polls Cisco MSE every 15 minutes for data. A new
transition matrix appears and 2D is enabled and shows all historical results.
transition matrix appears and 2D is enabled and shows all historical results.
Addition of new coverage
areas
areas
About 90 minutes
The earliest that data is written is after 60 minutes, plus 15 minutes polling time,
plus 15 minutes for refreshing the server-side cache with building parameters.
plus 15 minutes for refreshing the server-side cache with building parameters.
Note: The old coverage areas will remain in the menus as long as they are
referenced in the database. Currently, you can only delete data to get rid of them.
referenced in the database. Currently, you can only delete data to get rid of them.
Addition of new floor
About 90 minutes, or 5 hours
and 30 minutes
and 30 minutes
If you restart the analytics service, it will refetch the building parameters and take 90
minutes to display the new data. Otherwise, the system reloads the building
parameters every 4 hours.
minutes to display the new data. Otherwise, the system reloads the building
parameters every 4 hours.
Change to maximum
dimension in mse.properties
dimension in mse.properties
Immediate
Changes apply immediately after file is changed and MSE is restarted.
Data retrieved from Cisco
MSE database
MSE database
Every 15 minutes
This is the default and can be set in the mse.properties file.
Building characteristics
refreshed for user interface
refreshed for user interface
Every 15 minutes
This is the default