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

Help understanding AP debug log

This thread has been viewed 4 times

  • 1.  Help understanding AP debug log

    Posted Aug 30, 2013 06:15 AM

    Wondered if anyone could help understand the following messages I am seeing when I look at the debug log of an AP.

     

    Ive had reports of poor coverage within the area, but am struggling to actually pinpoint the problem.  

     

    I have just deployed some new AP93's (not used these before).  Running AOS 5.0.4.12

     

    This is just a sample of some of the messages I am seeing:

     

    Aug 30 06:58:11 sapd[306]: <404050> <WARN> |AP MOD-GND-3@20.150.201.58 sapd| ^[bssid d8:c7:c8:7c:13:80] [channel 1] [per 0] [mer 67] [frr 0] [arm_error_rate_threshold 50] [arm_error_rate_wait_time 30]
    Aug 30 06:58:12 sapd[306]: <404050> <WARN> |AP MOD-GND-3@20.150.201.58 sapd| ^[bssid d8:c7:c8:7c:13:80] [channel 1] [per 0] [mer 64] [frr 0] [arm_error_rate_threshold 50] [arm_error_rate_wait_time 30]
    Aug 30 06:58:13 sapd[306]: <404050> <WARN> |AP MOD-GND-3@20.150.201.58 sapd| ^[bssid d8:c7:c8:7c:13:80] [channel 1] [per 0] [mer 79] [frr 0] [arm_error_rate_threshold 50] [arm_error_rate_wait_time 30]

    Aug 30 09:10:07 stm[323]: <501100> <NOTI> |AP MOD-GND-3@20.150.201.58 stm| ^[tstr 09:10:07.372938] [mac 00:28:41:cb:AB:38] [ip 20.150.201.58] [bssid d8:c7:c8:7c:13:80] [name MOD-GND-3]
    Aug 30 09:10:10 stm[323]: <501105> <NOTI> |AP MOD-GND-3@20.150.201.58 stm| ^[mac 00:28:41:cb:AB:38] [ip 20.150.201.58] [bssid d8:c7:c8:7c:13:80] [name MOD-GND-3] [reason_code STA has left and is deauthenticated]
    Aug 30 09:11:11 stm[323]: <501105> <NOTI> |AP MOD-GND-3@20.150.201.58 stm| ^[mac 00:28:41:cb:AB:38] [ip 20.150.201.58] [bssid d8:c7:c8:7c:13:80] [name MOD-GND-3] [reason_code Prior authentication is not valid]
    Aug 30 09:11:11 stm[323]: <501044> <NOTI> |AP MOD-GND-3@20.150.201.58 stm| ^[sta 00:28:41:cb:AB:38] [bss d8:c7:c8:7c:13:80] [name MOD-GND-3]
    Aug 30 09:11:11 stm[323]: <501105> <NOTI> |AP MOD-GND-3@20.150.201.58 stm| ^[mac 00:28:41:cb:AB:38] [ip 20.150.201.58] [bssid d8:c7:c8:7c:13:80] [name MOD-GND-3] [reason_code Prior authentication is not valid]
    Aug 30 09:11:11 stm[323]: <501044> <NOTI> |AP MOD-GND-3@20.150.201.58 stm| ^[sta 00:28:41:cb:AB:38] [bss d8:c7:c8:7c:13:80] [name MOD-GND-3]

    Aug 30 09:21:29 stm[323]: <501044> <NOTI> |AP MOD-GND-3@20.150.201.58 stm| ^[sta 00:28:41:cb:AB:38] [bss d8:c7:c8:7c:13:80] [name MOD-GND-3]
    Aug 30 09:53:44 stm[323]: <501106> <NOTI> |AP MOD-GND-3@20.150.201.58 stm| ^[mac 18:00:3f:81:45:432] [ip 20.150.201.58] [bssid d8:c7:c8:7c:13:82] [name MOD-GND-3] [func handle_sapcp]
    Aug 30 09:53:44 stm[323]: <501080> <NOTI> |AP MOD-GND-3@20.150.201.58 stm| ^[mac 18:00:3f:81:45:432] [ip 20.150.201.58] [bssid d8:c7:c8:7c:13:82] [name MOD-GND-3] [reason Denied: AP Ageout]
    Aug 30 09:53:44 stm[323]: <501114> <NOTI> |AP MOD-GND-3@20.150.201.58 stm| ^[mac 18:00:3f:81:45:432] [ip 20.150.201.58] [bssid d8:c7:c8:7c:13:82] [name MOD-GND-3] [reason_code 255]
    Aug 30 09:53:44 stm[323]: <501044> <NOTI> |AP MOD-GND-3@20.150.201.58 stm| ^[sta 18:00:3f:81:45:432] [bss d8:c7:c8:7c:13:82] [name MOD-GND-3]

     

    Thanks



  • 2.  RE: Help understanding AP debug log

    EMPLOYEE
    Posted Aug 30, 2013 07:44 AM

    These messages are not sending any red flags my way.  Can you find a problem client's MAC address and issue this command in the configuration?

     

    logging level debugging user-debug xx:xx:xx:xx:xx:xx

     

    Where xx:xx is the actual mac?

     

    That will tell us about the actual client and what may be happening. Also, consider a code upgrade.  May I ask what controller hardware you're running?



  • 3.  RE: Help understanding AP debug log

    Posted Aug 30, 2013 07:47 AM

    Will be doing some more investigation this afternoon.. so will filter the client mac during debug.

     

    No go on the code upgrade due to the controllers and cards we have, alhtough planning hardware upgrade in the coming months and am looking forward to v6!



  • 4.  RE: Help understanding AP debug log

    Posted Sep 02, 2013 10:07 AM

    Hopefully doing some further testing tomorrow...

     

    Ive just rolled out some 105's, and they two seem to be having the same issues as the 93's which makes me wonder if they need to be treated any differently than non N class APs with regards to their config?  or are they simply  just another AP?

     

    My laptop was dropping pings all over th eplace, and couldnt even perform a simply taks of mapping a drive to my desktop pc.

     

    Ill do some troubleshooting tomorrow.. just seem coincidence that im having issues since using these N class APs.



  • 5.  RE: Help understanding AP debug log

    EMPLOYEE
    Posted Sep 02, 2013 01:20 PM

    Did you look at the Dashboard to see the health of those access points?



  • 6.  RE: Help understanding AP debug log

    Posted Sep 03, 2013 03:11 AM

    Dashobard? what dashboard??? :-p

     

    Done have the luxury of that wonderful tool on v5 code. :-(



  • 7.  RE: Help understanding AP debug log

    EMPLOYEE
    Posted Sep 03, 2013 06:36 AM

    I apologize.  You did say 5.x.

     

    How long has this problem been happening?  Has it ever worked?  How many users are on the WLAN?  How many SSIDs?  Encryption?