Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

Client association detailed history

This thread has been viewed 9 times
  • 1.  Client association detailed history

    Posted Jun 17, 2015 07:58 AM

    Hi,

    I am interested in collecting client association detailed history for few clients (minute by minute recording all movements to APs) for over one week period. What is the best way to get detailed data for client for this period? I have seen Airwave but it doe snot provide details as probably it is based on polling interval. 

    Can someone suggest the best approach on either Controller or Airwave to get this information?

     

    Thanks



  • 2.  RE: Client association detailed history

    Posted Jun 17, 2015 08:19 AM

    HI Friend,

     

    You can achieve this by configuring a SYS Log server in Airwave.( Try with 3cDaemon )

     

    Please feel free for any further help on this.



  • 3.  RE: Client association detailed history

    Posted Jun 17, 2015 08:46 AM

    Hi Dhanraj,

    Thanks for your reply. I thought Airwave does not gather live information. In my case I have seen it polling data every 10 or 15 minutes. Do you think the syslog from Airwave would work or should it be done on controller?  I am also trying to understand where and how to reduce the polling time interval on Airwave. 



  • 4.  RE: Client association detailed history

    EMPLOYEE
    Posted Jun 17, 2015 08:52 AM

    Airwave will NOT work in this situation.  You need to turn on user debugging on the controller and then send syslog from the controller to a syslog server.

     

    To turn on user debugging for all users:

    config t
    logging level debugging user

     

    If you turn on user debugging on the controller and you type "show log user all | include roamed", you would see a message like this:

     

    Dec 18 13:00:48  stm[2025]: <501105> <NOTI> |AP 2NAP04-225@10.1.1.149 stm|  Deauth from sta: 80:86:f2:3b:f4:70: AP 10.1.1.149-6c:f3:7f:ee:57:30-2NAP04-225 Reason STA has roamed to another AP

    You can send that to an external syslog  to look at detailed roaming.  It can get very chatty, because users roam all of the time, so make sure your syslog server can handle it.