Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

Cisco Mobility Services Engine (MSE) unable to discover clients and rogues

     

     

    Introduction

    In CAS infrastructure, Cisco Mobility Services Engine (MSE) is unable to track clients and rogues but able to track the tags. MSE Partner Engine is running and Tags are positioned in maps with both permanent licenses and demo license.

    Hardware

    • MSE: 7.4.100.0
    • Prime Infrastructure: 1.3.0.20
    • WLC: 7.4.100

    Details

    Wireless clients are not counted while tags are counted. However, there are active clients in the page below but they do not show up in the map screen.

    Untitled.jpg

     

    On PI, under mobility service engine ->context aware services, the following screen is shown which indicates that clients are tracked:

    Untitled.jpg

     

    Under mobility service engine-> General, the following screen is shown: the client should be tracked even if the Cisco CAS engine shows status down.

    Untitled.jpg

     

    MSE is already added to the floor plan map and synced:

    CAS3.png

    Reinstall MSE application on server didn't help.

    Resources Required

    The MSE is a Virtual Machine.

    Untitled.jpg

    Logs

    Below is the output from mse status:

    -------------

    Context Aware Service

    -------------

    Total Active Elements(Wireless Clients, Tags, Rogue APs, Rogue Clients, Interferers, Wir
    ed Clients): 27
    Active Wireless Clients: 0
    Active Tags: 27
    Active Rogue APs: 0
    Active Rogue Clients: 0
    Active Interferers: 0
    Active Wired Clients: 0
    Active Elements(Wireless Clients, Rogue APs, Rogue Clients, Interferers, Wired Clients)
    Limit: 1000
    Active Tag Limit: 100
    Active Sessions: 1
    Wireless Clients Not Tracked due to the limiting: 0
    Tags Not Tracked due to the limiting: 0
    Rogue APs Not Tracked due to the limiting: 0
    Rogue Clients Not Tracked due to the limiting: 0
    Interferers Not Tracked due to the limiting: 0
    Wired Clients Not Tracked due to the limiting: 0
    Total Elements(Wireless Clients, Rogue APs, Rogue Clients, Interferers, Wired Clients) N
    ot Tracked due to the limiting: 0

    -------------------------

    Context Aware Sub Services

    -------------------------

    Subservice Name: Aeroscout Tag Engine
    Admin Status: Enabled
    Operation Status: Up
    Subservice Name: Cisco Tag Engine
    Admin Status: Disabled
    Operation Status: Down

    -------------

    Aeroscout Tag Engine

    -------------

    Version: 04.04.02.04 - CIL3
    Description: AeroScout® Location Engine for RSSI and TDOA asset tracking
    Registered: true
    Active: true
    Engine flap Count: 0
    Failed Connection attempts: 1

    Clients seen on WLC but not on map

    show client <mac> detail:
    ......
    Nearby AP Statistics:
          APacf2.c506.a7c9(slot 0)
            antenna0: 47 secs ago.................... -86 dBm
            antenna1: 47 secs ago.................... -82 dBm
          APacf2.c506.a782(slot 0)
            antenna0: 47 secs ago.................... -71 dBm
            antenna1: 47 secs ago.................... -77 dBm
          APacf2.c506.a7ce(slot 0)
            antenna0: 47 secs ago.................... -59 dBm
            antenna1: 47 secs ago.................... -55 dBm
          AP0006.f616.e708(slot 0)
            antenna0: 47 secs ago.................... -57 dBm
            antenna1: 47 secs ago.................... -52 dBm
          AP0006.f66b.d3d6(slot 0)
            antenna0: 47 secs ago.................... -63 dBm
            antenna1: 47 secs ago.................... -65 dBm

    Logs - logserver.log file

    MeasurementNotification-message-225.Groups.0.Entries.5.ApRssiMeasurements.Entries.1.ApMacAddress = 84:78:ac:f0:81:20
    MeasurementNotification-message-225.Groups.0.Entries.5.ApRssiMeasurements.Entries.1.AntennaId = 1
    MeasurementNotification-message-225.Groups.0.Entries.5.CcxTagPayloadList = null
    MeasurementNotification-message-225.Groups.0.Entries.5.TransmitPower@729103289
    MeasurementNotification-message-225.Groups.0.Entries.5.TransmitPower.Value = -128
    MeasurementNotification-message-225.Groups.0.Entries.5.BatteryStatus = null
    MeasurementNotification-message-225.Groups.0.Entries.5.Chokepoint = null
    MeasurementNotification-message-225.Groups.0.Entries.5.ChokepointOptions = null
    MeasurementNotification-message-225.Groups.0.Entries.5.SequenceRange = null
    MeasurementNotification-message-225.Groups.0.Entries.5.RssiSource = null
    MeasurementNotification-message-225.Groups.0.Entries.5.DirectedStatsList = null
    MeasurementNotification-message-225.Groups.0.DeviceCategory = <MeasurementNotification-message-225.Groups.0.Entries.0.DeviceCategory@1022133318>
    MeasurementNotification-message-225.Groups.0.EntryCount@497288441
    MeasurementNotification-message-225.Groups.0.EntryCount.Count = 6
    MeasurementNotification-message-225.ServiceDescriptor@2067957410
    MeasurementNotification-message-225.ServiceDescriptor.ServiceId = RSSI
    MeasurementNotification-message-225.ServiceDescriptor.ServiceMask = 1
    MeasurementNotification-message-225.EntryCount = null
    MeasurementNotification-message-225.Context@1284846822
    MeasurementNotification-message-225.Context.SequenceNumber = 225
    MeasurementNotification-message-225.Context.MessageId = MEASUREMENT_NOTIFICATION
    MeasurementNotification-message-225.MessageType = NOTIFICATION
    MeasurementNotification-message-225.Rawbytes = null
    MeasurementNotification-message-225.NanoTimestamp = 486808371199663
    4/10/13 06:56:36.54 TRACE[location] [35] AesLocationModule.handleModuleMsg handle NMSP Msg
    4/10/13 06:56:36.54 INFO[location] [46] Failed to find heatmap for AP interface 84:78:ac:f0:81:20-5.0-0
    4/10/13 06:56:36.54 INFO[location] [46] Failed to find heatmap for AP interface 84:78:ac:f0:81:20-5.0-0
    4/10/13 06:56:36.54 INFO[location] [46] Failed to find heatmap for AP interface 84:78:ac:f0:84:b0-5.0-0
    4/10/13 06:56:36.54 INFO[location] [46] Failed to find heatmap for AP interface 84:78:ac:f0:84:b0-5.0-0

    From this all client/tag measurement information is received by the location server, but that AP heat maps cannot be retrieved.

    From the Matlab-process-heatmap-engine.log:

    4/09/13 10:47:31 INFO[location] [11] MatlabHeatmapBuilder#createAPInterfaceHeatmap CREATE heat map (heatmapkey,binsize,rssiCutoff): 84:78:ac:f0:84:b0-2.4-1 8 -112
    4/09/13 10:47:31 INFO[location] [11] MatlabHeatmapBuilder#createAPInterfaceHeatmap Calling Matlab method site_survey_ap_info_compute_heatmap

    So the heatmap key created is: 84:78:ac:f0:84:b0-2.4-1 but the one asked for is: 84:78:ac:f0:84:b0-5.0-0

    Solution

    The problem seems to be an incompatibility (read a bug) in the MSE that does not handle RSSI measurements coming from single band Access Points (2.4 GHz). When we received a dual band Access Point from Cisco, things started to work as expected. This behavior is consistent with the logs displayed further up in this post.

    Untitled.jpg

    The bug was CSCuh07165

     

    Known Fixed Releases - Download software for  Cisco Mobility Services Engine

    Reference