cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
751
Views
0
Helpful
7
Replies
Highlighted
Beginner

Why do MSE API clients dissapear?

When we query the MSE API with https://IP_MSE/api/contextaware/v1/location/clients/

we lack devices.

We have some devices that appear in PRIME and MSE API in the url

https://IP_MSE/api/contextaware/v1/location/clients/

Although these devices stay in the same location all the time they disappear from MSE API but they do not from PRIME, WLC.

Example:

A device is in the same place for 4 hours.

When we query mse  API we can see it for two hours and after two hours it does not longer appear in  MSE API

although you can see it in PRIME and WLC.

 

We also have devices that never appear in MSE APIbut they are in PRIME.

Of course, we know that devices will not  appear instantly on MSE API, but sometimes they never appear.

Everyone's tags (2)
7 REPLIES 7
Highlighted
Cisco Employee

Re: Why do MSE API clients dissapear?

I've moved this forum post to the Mobility Services API forum.

Highlighted
Not applicable

Re: Why do MSE API clients dissapear?

Hi kiko,

Could you please provide screenshots of API response and Prime ?

Highlighted
Beginner

Re: Why do MSE API clients dissapear?

MAC c8:f6:50:97:e8:b1 is in Prime but not in MSE.

prime.pngmse.png

Highlighted
Cisco Employee

Re: Why do MSE API clients dissapear?

Hi Kiko

MSE moves clients to the location history table after sometime. Please check the MSE history API instead of the real time APIs.

Abhishek

Highlighted
Beginner

Re: Why do MSE API clients dissapear?

We don't  have  active location in history in the mse. We couldn't check  MSE history API.

Today we realize that most of the clients that we couldn't find in

http://IPMSE/api/contextaware/v1/location/clients/

we found it if we do the following search

http://IPMSE/api/contextaware/v1/location/clients/clientMACaddress

We have the same problem shown in this url, but the mac is not fake:

https://ciscomarketing.jiveon.com/thread/47282

Highlighted
Beginner

Re: Why do MSE API clients dissapear?

We know why a MAC appears on http://ipmse/api/contextaware/v1/location/clients/clientMACaddress and not in http://ipmse/api/contextaware/v1/location/clients/

The difference is that in the first search the currentlyTracked parameter default setting is "false" while the second is "true".

The problem now is why this client has currentlyTracked="false" if it is associated to an access point?

This client doesn't move. First it has currentlyTracked="true" and later it is has currentlyTracked="false".

Could be this note the cause?

When devices are associated they PROBE much less often.  MSE only calculates location based on PROBE and not based on data packets.  In an upcoming release, we are supporting DATA RSSI and will be able to update location more often of an ASSOCIATED device.

Highlighted
Not applicable

Re: Why do MSE API clients dissapear?

Hello Kiko,

Apologies for the delay in response.

Your observations is right. If the currentlyTracked value is FALSE, the device will not appear in 'Get all clients API' i.e. HTTP GET /api/contextaware/v1/location/clients/

The currentlyTracked value changes to FALSE if the controller doesn't receive any 'Probes' from the device for 5 minutes. But the API 'Get client by mac-id' i.e. HTTP GET /api/contextaware/v1/location/clients/<your-mac-id> will still return data with last known attributes of the device.

Content for Community-Ad
Cisco Community July 2020 Spotlight Award Winners
This widget could not be displayed.