Network Management

last person joined: yesterday 

Keep an informative eye on your network with HPE Aruba Networking network management solutions
Expand all | Collapse all

Does RTLS collector work well with AirWave 8.0.6.1?

This thread has been viewed 0 times
  • 1.  Does RTLS collector work well with AirWave 8.0.6.1?

    Posted Mar 03, 2015 10:24 AM

    I was wondering if the RTLS collector works well into AirWave 8.0.6.1? In fact, it consummes a lot of ressources and it makes the platform unstable. Each time I restarted the complete VisualRF process I got a CPU peak during several days.

     

    cpu.jpg

    I'm sure that this CPU peak is due to the RTLS collector because when I disable it the CPU goes suddenly down and the Airwave platform is more stable.

     

    cpu_activity_rtls_collector_disable.jpg

     

    In my configuration, the RTLS information are sent to AirWave by IAP215 and IAP205. There is a total of 42 Instant AP and there are splitted into 10 different clusters.

     

    Instant version: 6.4.2.0-4.1.1.1

    AirWave version: 8.0.6.1

     

    Is it a known behavior or is it simply normal? Can the AirWave RTLS collector work with the RTLS information provided by Instant AP.

     

    Find below an extract of the VisualRF logs. All that logs for only one second of time (that could explain this high cpu activity). Do you know what could be the cause of that error message?

     

    2015-02-27 16:16:20,226 ERROR MessageQ[5]  com.airwave.model.external.RTLSMessageTask discovered client for mac[24:77:03:B3:FC:80] not found
    2015-02-27 16:16:20,227 ERROR MessageQ[5]  com.airwave.model.external.RTLSMessageTask discovered client for mac[24:77:03:B3:FC:80] not found
    2015-02-27 16:16:20,325 ERROR MessageQ[3]  com.airwave.model.external.RTLSMessageTask discovered client for mac[24:77:03:B3:FC:80] not found
    2015-02-27 16:16:20,331 ERROR MessageQ[3]  com.airwave.model.external.RTLSMessageTask discovered client for mac[24:77:03:B3:FC:80] not found
    2015-02-27 16:16:20,442 ERROR MessageQ[5]  com.airwave.model.external.RTLSMessageTask Cannot determine discovered AP radio with BSSID[40:01:C6:12:E0:51] radio count[0] , disregarding potential rogue
    2015-02-27 16:16:20,459 ERROR MessageQ[3]  com.airwave.model.external.RTLSMessageTask Cannot determine discovered AP radio with BSSID[40:01:C6:12:E0:51] radio count[0] , disregarding potential rogue
    2015-02-27 16:16:20,550 ERROR MessageQ[5]  com.airwave.model.external.RTLSMessageTask discovered client for mac[24:77:03:AC:17:30] not found
    2015-02-27 16:16:20,551 ERROR MessageQ[5]  com.airwave.model.external.RTLSMessageTask discovered client for mac[44:D4:E0:4E:AF:52] not found
    2015-02-27 16:16:20,551 ERROR MessageQ[5]  com.airwave.model.external.RTLSMessageTask discovered client for mac[44:D4:E0:4E:AF:52] not found
    2015-02-27 16:16:20,558 ERROR MessageQ[3]  com.airwave.model.external.RTLSMessageTask discovered client for mac[24:77:03:AC:17:30] not found
    2015-02-27 16:16:20,750 ERROR MessageQ[3]  com.airwave.model.external.RTLSMessageTask Cannot determine discovered AP radio with BSSID[40:01:C6:12:F0:52] radio count[0] , disregarding potential rogue
    2015-02-27 16:16:20,777 ERROR MessageQ[4]  com.airwave.model.external.RTLSMessageTask Cannot determine discovered AP radio with BSSID[40:01:C6:12:F0:52] radio count[0] , disregarding potential rogue
    2015-02-27 16:16:20,861 ERROR MessageQ[2]  com.airwave.model.external.RTLSMessageTask Cannot determine discovered AP radio with BSSID[00:24:73:5D:BB:70] radio count[0] , disregarding potential rogue
    2015-02-27 16:16:20,866 ERROR MessageQ[4]  com.airwave.model.external.RTLSMessageTask Cannot determine discovered AP radio with BSSID[00:24:73:5D:BB:70] radio count[0] , disregarding potential rogue
    2015-02-27 16:16:20,897 ERROR MessageQ[4]  com.airwave.model.external.RTLSMessageTask Cannot determine discovered AP radio with BSSID[40:01:C6:12:97:10] radio count[0] , disregarding potential rogue
    2015-02-27 16:16:20,904 ERROR MessageQ[5]  com.airwave.model.external.RTLSMessageTask Cannot determine discovered AP radio with BSSID[40:01:C6:12:97:10] radio count[0] , disregarding potential rogue

     

    Thanks in advance for your help and your comments,

    Regards

     

     

     

     

     

     

     

     

     



  • 2.  RE: Does RTLS collector work well with AirWave 8.0.6.1?

    EMPLOYEE
    Posted Mar 03, 2015 06:04 PM

    Please open a support case, this sounds like a defect that we'll want to debug.