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.
Back to discussions
Expand all | Collapse all

Obtaining Client roaming history through an Aruba Controller

This thread has been viewed 16 times

  • 1.  Obtaining Client roaming history through an Aruba Controller

    Posted Jan 29, 2018 02:37 AM

    Hello Experts,

     

    How can we verify a particular client's roam history through an ARuba Controller?

    I don't have Airwave on my setup. Insterested in knowing if this could be facilitated through any cli/debug.

     



  • 2.  RE: Obtaining Client roaming history through an Aruba Controller
    Best Answer

    Posted Jan 29, 2018 11:21 PM

    I think this is what you're after:

     

    summary:                   show ap client trail-info

    detail for one mac:     show ap client trail-info <mac>

     

    for more detail or more history, you should use syslog

     

     

     



  • 3.  RE: Obtaining Client roaming history through an Aruba Controller

    Posted Jan 31, 2018 07:32 AM

    Thanks Jeff G.

     

    Thats precisely the output, I was looking for :)

     

    (WLC_LAB) #show ap client trail-info 98:f1:70:40:3d:80

    Client Trail Info
    -----------------
    MAC BSSID ESSID AP-name VLAN Deauth Reason Alert
    --- ----- ----- ------- ---- ------------- -----
    98:f1:70:40:3d:80 94:3a:0e:9b:14:23 TEST-SSID IAP-0009 150 Sapcp Ageout (internal ageout) STA has roamed to another AP

    Deauth Reason
    -------------
    Reason Timestamp
    ------ ---------
    Sapcp Ageout (internal ageout) Jan 31 12:05:46
    Internal deauth Jan 31 11:53:51
    Internal deauth Jan 31 11:47:48
    STA has left and is disassociated Jan 31 10:55:57
    Internal deauth Jan 31 09:23:16
    Internal deauth Jan 31 09:22:46
    Internal deauth Jan 31 09:17:34
    Sapcp Ageout (internal ageout) Jan 31 08:56:43
    STA has left and is disassociated Jan 31 08:55:14
    Internal deauth Jan 31 08:54:43
    Num Deauths:10

    Alerts
    ------
    Reason Timestamp
    ------ ---------
    STA has roamed to another AP Jan 31 11:53:51
    STA has roamed to another AP Jan 31 11:47:48
    STA has roamed to another AP Jan 31 09:23:16
    STA has roamed to another AP Jan 31 09:22:46
    STA has roamed to another AP Jan 31 09:17:34
    STA has roamed to another AP Jan 31 08:54:43
    STA has roamed to another AP Jan 31 08:49:52
    STA has roamed to another AP Jan 31 07:55:20
    STA has roamed to another AP Jan 31 07:54:22
    STA has roamed to another AP Jan 31 07:54:02
    Num Alerts:10

    Mobility Trail
    --------------
    BSSID ESSID AP-name VLAN Timestamp
    ----- ----- ------- ---- ---------
    94:3a:0e:9b:14:23 TEST-SSID IAP-0009 150 Jan 31 12:05:48
    94:3a:0e:9b:14:23 TEST-SSID IAP-0009 150 Jan 31 12:05:48
    94:3a:0e:9b:19:83 TEST-SSID IAP-0005 150 Jan 31 12:05:46
    94:3a:0e:9b:19:83 TEST-SSID IAP-0005 150 Jan 31 11:53:51
    63:e3:d6:18:cb:c2 TEST-SSID OAP-0002-UPDATED 150 Jan 31 11:53:51
    94:3a:0e:9b:19:83 TEST-SSID IAP-0005 150 Jan 31 11:53:51
    63:e3:d6:18:cb:c2 TEST-SSID OAP-0002-UPDATED 150 Jan 31 11:47:48
    94:3a:0e:9b:19:83 TEST-SSID IAP-0005 150 Jan 31 11:47:48
    63:e3:d6:18:cb:c2 TEST-SSID OAP-0002-UPDATED 150 Jan 31 11:47:48
    94:3a:0e:9b:19:83 TEST-SSID IAP-0005 150 Jan 31 10:56:00
    Num Mobility Trails:10

    (WLC_LAB) #



  • 4.  RE: Obtaining Client roaming history through an Aruba Controller

    Posted Jan 22, 2020 10:27 AM

    I am looking for a way to identify why a specific client was disconnected on an Aruba IAP, but the commands below don't work. summary: show ap client trail-info detail for one mac: show ap client trail-info What is the alternative command on ArubaOS (MODEL: 105), Version 6.4.4.8-4.2.4.13 ?