Wireless Access

last person joined: 4 hours ago 

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

Timer tick - what it equal to?

This thread has been viewed 0 times

  • 1.  Timer tick - what it equal to?

    Posted Jan 25, 2019 05:39 AM

    Hi , 

    I'm new to aruba technologies, and need someone to clarify on this "timer tick" concept. Is it equal to second or measured any other way? 

     

    here is example below. I thought it is how much seconds ago it happen, but the counters do not increase, as I expect.

     

    Thank you in advance.

    ====================

    # show ap monitor containment-info

    wifi0: Wireless Containment Counters
    -------------------------------------
    Parameter Value
    --------- -----
    Last Deauth Timer Tick 5822414
    Deauth frames to AP 5610795
    Deauth frames to Client 5610795
    Last Tarpit Timer Tick 0
    Tarpit Frames: Probe Response 0



  • 2.  RE: Timer tick - what it equal to?
    Best Answer

    EMPLOYEE
    Posted Jan 27, 2019 04:18 AM

    it's equivalent to a second (there are a few places it's shown as msec, usually it's noted though) and just increases monotonically with AP uptime. The current value can be seen from the following command on an IAP

     

     

    iap115# show log driver | include "Log C"
    Current Log Level 3 Log Counter 78 Timestamp 1116298.213064
    iap115#

    in this case the AP has been up for 1116298 seconds, which is just under 13 days. Cross check against the APs uptime:

     

     

     

    iap-115# show aps

iap115  192.168.1.24*  access  disable   3        115(indoor)  fe80::1a64:72ff:fec1:367e  N/A        -     CJ0000000  -            -               -                    -                      149+         21              28(good)             -93(good)              No                   none       0          5204         enable           12d:22h:0m:0s   

iap-115#

    you can subtract your event timestramp from the current value and work backwards from that.