Wireless Access

last person joined: 20 hours ago 

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

Debugging ARM error thresholds?

This thread has been viewed 2 times
  • 1.  Debugging ARM error thresholds?

    Posted Sep 10, 2013 08:56 AM

    We had reports customer reports this morning complaining about general connectivity. Running some basic commands, I couldn't see anything for today, but could see that there were definate issues yesterday with error thresholds exceeded on 1 AP

     

    ) #show ap arm history ap-name ap105-xxxxxx

     

    Interface :wifi0

    Interface :wifi1

    ARM History

    -----------

    Time of Change       Old Channel  New Channel  Old Power  New Power  Reason

    --------------       -----------  -----------  ---------  ---------  ------

    2013-09-09 16:55:20  6            1            9          9          E

    2013-09-09 12:25:57  1            6            9          9          E

    2013-09-05 07:41:10  6            1            9          9          E

    2013-09-03 12:31:24  11           6            9          9          E

    2013-09-03 10:18:56  6            11           9          9          E

    2013-09-03 05:13:26  6            6            12         9          P-

    2013-09-03 04:59:31  6            6            9          12         P+

    I: Interference, R: Radar detection, N: Noise exceeded, E: Error threshold exceeded, INV: Invalid Channel, G: Rogue AP Containment, M: Empty Channel, P+: Increase Power, P-: Decrease Power, 40INT: 40MHZ intol detected on 2.4G, NO40INT: 40MHz intol cleared on 2.4G, OFF: Turn off Radio, ON: Turn on Radio

     

    Are there any additional commnads that I can run to find which error threshold has been exceeded?



  • 2.  RE: Debugging ARM error thresholds?

    Posted Sep 10, 2013 10:06 AM

     

    When the Error threshold has been execced it usually means that you have a lot PHY/MAC errors which could be cause by Layer 2 retransmissions , Interference , Low SNR , etc..

     

    You could run the following show ap arm rf summary <ap-name> , this command will tell you know whether there's a lot PHY/MAC errors , noice and retries on a particular channel

     

     



  • 3.  RE: Debugging ARM error thresholds?

    Posted Sep 10, 2013 11:54 AM

    Im not seeing much in the way of errors but the area is quiet at the moment - I will retrt later when it is busier - Thx for the command syntax

     

    Channel Summary
    ---------------
    channel  retry  phy-err  mac-err  noise  cov-idx(Total)  intf_idx(Total)
    -------  -----  -------  -------  -----  --------------  ---------------
    36       0      0        0        93     0/0(0)          0/15//0/0(15)
    40       0      0        0        92     8/0(8)          43/0//0/0(43)
    44       0      0        0        93     0/0(0)          0/15//0/0(15)
    48       0      0        0        93     0/0(0)          0/5//0/0(5)
    52       0      0        0        93     0/0(0)          14/0//0/0(14)
    56       0      0        0        93     0/0(0)          0/5//0/0(5)
    60       0      0        0        93     0/0(0)          0/3//0/0(3)
    64       0      0        0        93     0/0(0)          10/0//0/0(10)
    100      0      0        0        93     8/0(8)          0/0//0/0(0)
    104      0      0        0        93     0/0(0)          0/0//0/0(0)
    108      0      0        0        93     0/0(0)          0/0//0/0(0)
    112      0      0        0        93     0/0(0)          0/0//0/0(0)
    116      0      0        0        93     0/0(0)          0/0//0/0(0)
    120      0      0        0        93     0/0(0)          0/0//0/2(2)
    124      0      0        0        93     0/1(1)          0/0//7/0(7)
    128      0      0        0        93     0/0(0)          0/0//0/2(2)
    132      0      0        0        93     0/0(0)          0/0//0/0(0)
    136      0      0        0        93     0/0(0)          0/2//0/0(2)
    140      0      0        0        93     0/0(0)          6/0//0/0(6)
    1        6      0        2        94     7/24(31)        115/7//268/44(434)
    6        0      0        0        94     0/19(19)        43/37//232/130(442)
    11       0      0        0        93     0/44(44)        0/19//404/49(472)


    HT Channel Summary
    ------------------
    channel_pair  Pairwise_intf_index
    ------------  -------------------
    116-120       2
    52-56         19
    100-104       0
    124-128       9
    36-40         58
    60-64         13
    108-112       0
    132-136       2
    44-48         20

    Interface Name           :wifi0
    Current ARM Assignment   :100+/24
    Covered channels a/g     :2/0
    Free channels a/g        :16/0
    ARM Edge State           :enable
    Last check channel/pwr   :4m:38s/4m:27s
    Last change channel/pwr  :5h:54m:50s/5h:54m:50s
    Next Check channel/pwr   :2m:54s/4s
    Assignment Mode          :Single Band

    Interface Name           :wifi1
    Current ARM Assignment   :1/9
    Covered channels a/g     :0/3
    Free channels a/g        :0/0
    ARM Edge State           :disable
    Last check channel/pwr   :3m:15s/1m:42s
    Last change channel/pwr  :58m:14s/58m:14s
    Next Check channel/pwr   :3m:49s/5m:15s
    Assignment Mode          :Single Band