Wireless Access

View Only

Back to discussions

Expand all | Collapse all

ARM not working?

This thread has been viewed 30 times

1. ARM not working?

Kudos

safranek

Posted Mar 12, 2024 10:26 AM

I started investigating a problem in Aruba system (many adjacent AP use the same 5GHz channel) and noticed an interesting thing about the ARM statistics. By issuing the "show ap arm rf-summary ap-name" command for each AP, I see that the "Last Check Channel/pwr" and "Last Change Channel/pwr" are almost equal to the AP uptime. Using the "show ap arm history ap-name" command, the history was empty for each AP I checked.
Is this normal? I don't think this is how it should work. What could be the problem, what can I check? In ARM settings everything is on default.

MMs in the DC, MD clusters on sites, running software AOS 8.10.0.10

(WLC1) [MDC] *#show ap active | include xxx-xxx-AP09
xxx-xxx-AP09  xxx_xxx      10.xx.x.xxx  534      A2a    13d:18h:54m:32s  N/A       A                      AP:5GHz-HE:40-/19.0/23.0/2            AP:2.4GHz-HE:11/12.0/20.0/0           
(WLC1) [MDC] *#show ap arm rf-summary ap-name xxx-xxx-AP09

Channel Summary
---------------
phy-type  channel  retry  phy-err  mac-err  noise  util(Qual)     cov-idx(Total)  intf_idx(Total)
--------  -------  -----  -------  -------  -----  ----------     --------------  ---------------
5GHz      36       0      0        0        92     4/0/3/0/99     0/0(0)          12/9//0/0(21)
5GHz      40       3      0        5        94     9/5/3/0/99     6/0(6)          24/0//0/0(24)
5GHz      44       0      0        0        92     4/1/3/0/100    0/0(0)          6/13//0/0(19)
5GHz      48       0      0        0        92     13/9/3/0/99    0/0(0)          14/7//0/0(21)
5GHz      52       0      0        0        92     2/2/0/0/100    0/0(0)          23/7//0/0(30)
5GHz      56       0      0        0        92     1/1/0/0/100    0/0(0)          17/10//0/0(27)
5GHz      60       0      0        0        92     3/2/0/0/99     0/0(0)          14/6//0/0(20)
5GHz      64       0      0        0        92     0/0/0/0/100    0/0(0)          13/3//0/0(16)
5GHz      100      0      0        0        92     0/0/0/0/100    0/0(0)          17/12//0/0(29)
5GHz      104      0      0        0        92     0/0/0/0/100    7/0(7)          35/5//0/0(40)
5GHz      108      0      0        0        92     1/1/0/0/100    3/0(3)          16/12//0/0(28)
5GHz      112      0      0        0        92     1/0/0/0/99     0/0(0)          8/5//0/0(13)
5GHz      116      0      0        0        92     0/0/0/0/100    0/0(0)          13/9//0/0(22)
5GHz      120      0      0        0        92     13/12/0/0/99   3/0(3)          26/7//0/0(33)
5GHz      124      0      0        0        92     0/0/0/0/100    4/0(4)          22/10//0/0(32)
5GHz      128      0      0        0        92     4/3/0/0/99     0/0(0)          14/10//0/0(24)
5GHz      132      0      0        0        92     10/9/0/0/99    0/0(0)          13/3//0/0(16)
5GHz      136      0      0        0        92     6/5/0/0/99     0/0(0)          12/3//0/0(15)
5GHz      140      0      0        0        92     0/0/0/0/100    0/0(0)          0/2//0/0(2)
2.4GHz    1        0      0        0        94     72/39/19/0/86  14/13(27)       138/45//115/13(311)
2.4GHz    6        0      0        0        94     63/39/18/0/94  18/8(26)        160/72//55/46(333)
2.4GHz    11       0      0        4        96     16/5/8/0/97    8/6(14)         127/39//62/8(236)

Columns:util(Qual): ch-util/rx/tx/ext-ch-util/quality
Noise followed by "*" indicates that the last scan on this channel was a split-scan, which was
triggered by high channel noise. Check show ap arm split-scan-history.

HT/VHT Channel Summary
----------------------
Phy-Type  Bandwidth  Channel range  Total interference index
--------  ---------  -------------  ------------------------
5GHz      40MHz      116-120        55        
5GHz      40MHz       52-56         57        
5GHz      40MHz      100-104        69        
5GHz      40MHz      124-128        56        
5GHz      40MHz       36-40         45        
5GHz      40MHz       60-64         36        
5GHz      40MHz      108-112        41        
5GHz      40MHz      132-136        31             
5GHz      40MHz       44-48         40        
5GHz      80MHz      116-128        111       
5GHz      80MHz       52-64         93        
5GHz      80MHz      100-112        110       
5GHz      80MHz       36-48         85        

Interface Name           :wifi0
Phy-Type                 :5GHz
Current ARM Assignment   :40-/19.0
Covered channels 5/2.4GHz     :16/0
Free channels 5/2.4GHz        :0/0
ARM Edge State           :enable
Last check channel/pwr   :13d:15h:44m:29s/13d:15h:44m:29s
Last change channel/pwr  :13d:15h:44m:29s/13d:15h:44m:29s
Next Check channel/pwr   :0s/0s
Assignment Mode          :Single Band

Interface Name           :wifi1
Phy-Type                 :2.4GHz
Current ARM Assignment   :11/12.0
Covered channels 5/2.4GHz     :0/3
Free channels 5/2.4GHz        :0/0
ARM Edge State           :disable                  
Last check channel/pwr   :13d:15h:44m:29s/13d:15h:44m:29s
Last change channel/pwr  :13d:15h:44m:29s/13d:15h:44m:29s
Next Check channel/pwr   :0s/0s
Assignment Mode          :Single Band
(WLC1) [MDC] *#

Thanks!

2. RE: ARM not working?

Kudos
chulcher

MVP GURU ELITE
Posted Mar 12, 2024 10:53 AM

Reply Reply Privately
Since your controller is managed by a Mobility Conductor (MCR), your environment is using AirMatch and not ARM.

------------------------------
Carson Hulcher, ACEX#110
------------------------------
3. RE: ARM not working?

Kudos
802.zak

MVP EXPERT
Posted Mar 12, 2024 10:55 AM

Reply Reply Privately
Are you using AirMatch?

From the MM you can use the "show airmatch solution ap-name" - as well as other optimization commands - to get additional details.

------------------------------
If my post was useful, please Accept Solution and Give Kudos.
------------------------------
Zak Chalupka
Principal Engineer - HPE Aruba
ACDX | ACMP | ACSP | ACCP
wifizak@hpe.com
------------------------------
Ideas expressed here are solely my own and not necessarily that of HPE Aruba.
------------------------------

4. RE: ARM not working?

Kudos

safranek

Posted Mar 13, 2024 04:27 AM
Edited by safranek Mar 13, 2024 04:35 AM

If I issue this command on MM, see nothing.

(mm1) [mynode] #show airmatch solution list-all


# Band Radio              Chan/Opt#     CBW      EIRP(dBm)/Opt# Client Band  APName
                                                                 Pref  Pref
  ---- -----------------  ------------- -------- -------------- ------ ----  ----------

[*] regarded frozen | [#] result adjusted to match feasibility 
Client Preference    - [p] HE Preferred | [n] Non-HE Preferred | [a] Allow-All
Band Preference      - [L] 5GHz-Lower | [U] 5GHz-Upper | [F] 5GHz-Full 

(mm1) [mynode] #
(mm1) [mynode] #show ap database-summary 

AP Database Summary
-------------------
AP Mode              Total Up  Total Down  Total Upgrading*  Total Rebooting*  RAP Up  RAP Down  RAP Upgrading*  RAP Rebooting*  Active Up  Standby Up
-------              --------  ----------  ----------------  ----------------  ------  --------  --------------  --------------  ---------  ----------
Access Points        600       0           0                 0                 0       0         0               0               0          0
Air Monitors         0         0           0                 0                 0       0         0               0               0          0
Wired Access Points  0         0           0                 0                 0       0         0               0               0          0
Mesh Portals         0         0           0                 0                 0       0         0               0               0          0
Mesh Points          0         0           0                 0                 0       0         0               0               0          0
Spectrum Monitors    0         0           0                 0                 0       0         0               0               0          0

*Upgrading, Rebooting, Active and Standby counts only reflect APs registered on this controller.

Unprovisioned Access Points:1                      
Duplicated AP Name:0
(mm1) [mynode] #

However something working about Airmatch, I see radar detection events:

(mm1) [mynode] #show airmatch event all-events all-aps


Band Event Type   Radio             Timestamp           Chan    CBW      New Chan    New CBW   APName
---- ------------ ----------------- ------------------- ------- -------- ----------- --------- ----------
5GHz RADAR_DETECT bc:9f:e4:aa:aa:aa 2024-03-13_09:06:14     116    40MHz          52     40MHz 
5GHz RADAR_DETECT b8:3a:5a:bb:bb:bb 2024-03-13_08:05:33     120    40MHz          60     40MHz 
5GHz RADAR_DETECT bc:9f:e4:cc:cc:cc 2024-03-13_08:01:56      60    40MHz         108     40MHz 
5GHz RADAR_DETECT bc:9f:e4:dd:dd:dd 2024-03-13_07:30:39     128    40MHz         132     40MHz 
5GHz RADAR_DETECT bc:9f:e4:ee:ee:ee 2024-03-12_17:34:26     100    40MHz         116     40MHz 
5GHz RADAR_DETECT b8:3a:5a:ff:ff:ff 2024-03-12_14:50:20     116    40MHz         112     40MHz 
5GHz RADAR_DETECT bc:9f:e4:aa:aa:aa 2024-03-12_14:38:57     108    40MHz         124     40MHz 
5GHz RADAR_DETECT bc:9f:e4:bb:bb:bb 2024-03-12_14:33:04     116    40MHz         124     40MHz 
5GHz RADAR_DETECT bc:9f:e4:cc:cc:cc 2024-03-12_14:28:08     132    40MHz         128     40MHz 
5GHz RADAR_DETECT bc:9f:e4:dd:dd:dd 2024-03-12_13:05:18     124    40MHz         120     40MHz 
5GHz RADAR_DETECT b8:3a:5a:ee:ee:ee 2024-03-12_12:54:44      60    40MHz         100     40MHz 
5GHz RADAR_DETECT bc:9f:e4:ff:ff:ff 2024-03-12_10:57:00     136    40MHz          64     40MHz 
5GHz RADAR_DETECT bc:9f:e4:aa:aa:aa 2024-03-12_10:56:53      56    40MHz          64     40MHz 
5GHz RADAR_DETECT bc:9f:e4:bb:bb:bb 2024-03-12_10:33:19     124    40MHz         108     40MHz 
5GHz RADAR_DETECT bc:9f:e4:cc:cc:cc 2024-03-12_09:27:23     132    40MHz         116     40MHz 
5GHz RADAR_DETECT bc:9f:e4:dd:dd:dd 2024-03-12_09:23:51      52    40MHz         116     40MHz 
5GHz RADAR_DETECT b8:3a:5a:ee:ee:ee 2024-03-12_09:00:19     124    40MHz         132     40MHz 
5GHz RADAR_DETECT bc:9f:e4:ff:ff:ff 2024-03-11_14:32:16     116    40MHz         124     40MHz 
5GHz RADAR_DETECT bc:9f:e4:aa:aa:aa 2024-03-11_14:23:27      64    40MHz          56     40MHz 
--More-- (q) quit (u) pageup (/) search (n) repeat

Original Message

5. RE: ARM not working?

Kudos

802.zak

MVP EXPERT

Posted Mar 13, 2024 10:36 AM

What is the output of:

#show airmatch debug optimization
#show airmatch profile

------------------------------
If my post was useful, please Accept Solution and Give Kudos.
------------------------------
Zak Chalupka
Principal Engineer - HPE Aruba
ACDX | ACMP | ACSP | ACCP
wifizak@hpe.com
------------------------------
Ideas expressed here are solely my own and not necessarily that of HPE Aruba.
------------------------------

Original Message

Original Message:
Sent: Mar 13, 2024 04:26 AM
From: safranek
Subject: ARM not working?

If I issue this command on MM, see nothing.

(mm1) [mynode] #show airmatch solution list-all# Band Radio              Chan/Opt#     CBW      EIRP(dBm)/Opt# Client Band  APName                                                                 Pref  Pref  ---- -----------------  ------------- -------- -------------- ------ ----  ----------[*] regarded frozen | [#] result adjusted to match feasibility Client Preference    - [p] HE Preferred | [n] Non-HE Preferred | [a] Allow-AllBand Preference      - [L] 5GHz-Lower | [U] 5GHz-Upper | [F] 5GHz-Full (mm1) [mynode] #(mm1) [mynode] #show ap database-summary AP Database Summary-------------------AP Mode              Total Up  Total Down  Total Upgrading*  Total Rebooting*  RAP Up  RAP Down  RAP Upgrading*  RAP Rebooting*  Active Up  Standby Up-------              --------  ----------  ----------------  ----------------  ------  --------  --------------  --------------  ---------  ----------Access Points        600       0           0                 0                 0       0         0               0               0          0Air Monitors         0         0           0                 0                 0       0         0               0               0          0Wired Access Points  0         0           0                 0                 0       0         0               0               0          0Mesh Portals         0         0           0                 0                 0       0         0               0               0          0Mesh Points          0         0           0                 0                 0       0         0               0               0          0Spectrum Monitors    0         0           0                 0                 0       0         0               0               0          0*Upgrading, Rebooting, Active and Standby counts only reflect APs registered on this controller.Unprovisioned Access Points:1                      Duplicated AP Name:0(mm1) [mynode] #

However something working about Airmatch, I see radar detection events:

(mm1) [mynode] #show airmatch event all-events all-apsBand Event Type   Radio             Timestamp           Chan    CBW      New Chan    New CBW   APName---- ------------ ----------------- ------------------- ------- -------- ----------- --------- ----------5GHz RADAR_DETECT bc:9f:e4:aa:aa:aa 2024-03-13_09:06:14     116    40MHz          52     40MHz 5GHz RADAR_DETECT b8:3a:5a:bb:bb:bb 2024-03-13_08:05:33     120    40MHz          60     40MHz 5GHz RADAR_DETECT bc:9f:e4:cc:cc:cc 2024-03-13_08:01:56      60    40MHz         108     40MHz 5GHz RADAR_DETECT bc:9f:e4:dd:dd:dd 2024-03-13_07:30:39     128    40MHz         132     40MHz 5GHz RADAR_DETECT bc:9f:e4:ee:ee:ee 2024-03-12_17:34:26     100    40MHz         116     40MHz 5GHz RADAR_DETECT b8:3a:5a:ff:ff:ff 2024-03-12_14:50:20     116    40MHz         112     40MHz 5GHz RADAR_DETECT bc:9f:e4:aa:aa:aa 2024-03-12_14:38:57     108    40MHz         124     40MHz 5GHz RADAR_DETECT bc:9f:e4:bb:bb:bb 2024-03-12_14:33:04     116    40MHz         124     40MHz 5GHz RADAR_DETECT bc:9f:e4:cc:cc:cc 2024-03-12_14:28:08     132    40MHz         128     40MHz 5GHz RADAR_DETECT bc:9f:e4:dd:dd:dd 2024-03-12_13:05:18     124    40MHz         120     40MHz 5GHz RADAR_DETECT b8:3a:5a:ee:ee:ee 2024-03-12_12:54:44      60    40MHz         100     40MHz 5GHz RADAR_DETECT bc:9f:e4:ff:ff:ff 2024-03-12_10:57:00     136    40MHz          64     40MHz 5GHz RADAR_DETECT bc:9f:e4:aa:aa:aa 2024-03-12_10:56:53      56    40MHz          64     40MHz 5GHz RADAR_DETECT bc:9f:e4:bb:bb:bb 2024-03-12_10:33:19     124    40MHz         108     40MHz 5GHz RADAR_DETECT bc:9f:e4:cc:cc:cc 2024-03-12_09:27:23     132    40MHz         116     40MHz 5GHz RADAR_DETECT bc:9f:e4:dd:dd:dd 2024-03-12_09:23:51      52    40MHz         116     40MHz 5GHz RADAR_DETECT b8:3a:5a:ee:ee:ee 2024-03-12_09:00:19     124    40MHz         132     40MHz 5GHz RADAR_DETECT bc:9f:e4:ff:ff:ff 2024-03-11_14:32:16     116    40MHz         124     40MHz 5GHz RADAR_DETECT bc:9f:e4:aa:aa:aa 2024-03-11_14:23:27      64    40MHz          56     40MHz --More-- (q) quit (u) pageup (/) search (n) repeat

Original Message:
Sent: Mar 12, 2024 10:55 AM
From: 802.zak
Subject: ARM not working?

Are you using AirMatch?

From the MM you can use the "show airmatch solution ap-name" - as well as other optimization commands - to get additional details.

6. RE: ARM not working?

Kudos

safranek

Posted Mar 13, 2024 10:41 AM

(mm1) [mynode] #show airmatch debug optimization 


                                                                                                                                                            Channel  Opmode
Seq   Time                   APs   [5GHz] Radios Cost  Conflict      [2GHz] Radios Cost  Conflict      [6GHz] Radios Cost  Conflict    Type                 Computed Computed
----- -------------------   -----         ------ ----- --------             ------ ----- --------             ------ ----- --------    -------------------- -------- --------
#606    2024-03-02_05:00:12       2              2     2        0                  2     4        0                  0    NA       NA               Scheduled      Yes       No

* EIRP is always computed in optimization

(mm1) [mynode] #show airmatch profile


AirMatch profile
----------------
Parameter          Value
---------          -----
schedule           Enabled
deploy-hour        5 AM
quality-threshold  8 percent
(mm1) [mynode] #

Original Message

Original Message:
Sent: Mar 13, 2024 10:35 AM
From: 802.zak
Subject: ARM not working?

What is the output of:

#show airmatch debug optimization
#show airmatch profile

If I issue this command on MM, see nothing.

(mm1) [mynode] #show airmatch solution list-all# Band Radio              Chan/Opt#     CBW      EIRP(dBm)/Opt# Client Band  APName                                                                 Pref  Pref  ---- -----------------  ------------- -------- -------------- ------ ----  ----------[*] regarded frozen | [#] result adjusted to match feasibility Client Preference    - [p] HE Preferred | [n] Non-HE Preferred | [a] Allow-AllBand Preference      - [L] 5GHz-Lower | [U] 5GHz-Upper | [F] 5GHz-Full (mm1) [mynode] #(mm1) [mynode] #show ap database-summary AP Database Summary-------------------AP Mode              Total Up  Total Down  Total Upgrading*  Total Rebooting*  RAP Up  RAP Down  RAP Upgrading*  RAP Rebooting*  Active Up  Standby Up-------              --------  ----------  ----------------  ----------------  ------  --------  --------------  --------------  ---------  ----------Access Points        600       0           0                 0                 0       0         0               0               0          0Air Monitors         0         0           0                 0                 0       0         0               0               0          0Wired Access Points  0         0           0                 0                 0       0         0               0               0          0Mesh Portals         0         0           0                 0                 0       0         0               0               0          0Mesh Points          0         0           0                 0                 0       0         0               0               0          0Spectrum Monitors    0         0           0                 0                 0       0         0               0               0          0*Upgrading, Rebooting, Active and Standby counts only reflect APs registered on this controller.Unprovisioned Access Points:1                      Duplicated AP Name:0(mm1) [mynode] #

However something working about Airmatch, I see radar detection events:

(mm1) [mynode] #show airmatch event all-events all-apsBand Event Type   Radio             Timestamp           Chan    CBW      New Chan    New CBW   APName---- ------------ ----------------- ------------------- ------- -------- ----------- --------- ----------5GHz RADAR_DETECT bc:9f:e4:aa:aa:aa 2024-03-13_09:06:14     116    40MHz          52     40MHz 5GHz RADAR_DETECT b8:3a:5a:bb:bb:bb 2024-03-13_08:05:33     120    40MHz          60     40MHz 5GHz RADAR_DETECT bc:9f:e4:cc:cc:cc 2024-03-13_08:01:56      60    40MHz         108     40MHz 5GHz RADAR_DETECT bc:9f:e4:dd:dd:dd 2024-03-13_07:30:39     128    40MHz         132     40MHz 5GHz RADAR_DETECT bc:9f:e4:ee:ee:ee 2024-03-12_17:34:26     100    40MHz         116     40MHz 5GHz RADAR_DETECT b8:3a:5a:ff:ff:ff 2024-03-12_14:50:20     116    40MHz         112     40MHz 5GHz RADAR_DETECT bc:9f:e4:aa:aa:aa 2024-03-12_14:38:57     108    40MHz         124     40MHz 5GHz RADAR_DETECT bc:9f:e4:bb:bb:bb 2024-03-12_14:33:04     116    40MHz         124     40MHz 5GHz RADAR_DETECT bc:9f:e4:cc:cc:cc 2024-03-12_14:28:08     132    40MHz         128     40MHz 5GHz RADAR_DETECT bc:9f:e4:dd:dd:dd 2024-03-12_13:05:18     124    40MHz         120     40MHz 5GHz RADAR_DETECT b8:3a:5a:ee:ee:ee 2024-03-12_12:54:44      60    40MHz         100     40MHz 5GHz RADAR_DETECT bc:9f:e4:ff:ff:ff 2024-03-12_10:57:00     136    40MHz          64     40MHz 5GHz RADAR_DETECT bc:9f:e4:aa:aa:aa 2024-03-12_10:56:53      56    40MHz          64     40MHz 5GHz RADAR_DETECT bc:9f:e4:bb:bb:bb 2024-03-12_10:33:19     124    40MHz         108     40MHz 5GHz RADAR_DETECT bc:9f:e4:cc:cc:cc 2024-03-12_09:27:23     132    40MHz         116     40MHz 5GHz RADAR_DETECT bc:9f:e4:dd:dd:dd 2024-03-12_09:23:51      52    40MHz         116     40MHz 5GHz RADAR_DETECT b8:3a:5a:ee:ee:ee 2024-03-12_09:00:19     124    40MHz         132     40MHz 5GHz RADAR_DETECT bc:9f:e4:ff:ff:ff 2024-03-11_14:32:16     116    40MHz         124     40MHz 5GHz RADAR_DETECT bc:9f:e4:aa:aa:aa 2024-03-11_14:23:27      64    40MHz          56     40MHz --More-- (q) quit (u) pageup (/) search (n) repeat

Original Message:
Sent: Mar 12, 2024 10:55 AM
From: 802.zak
Subject: ARM not working?

Are you using AirMatch?

From the MM you can use the "show airmatch solution ap-name" - as well as other optimization commands - to get additional details.

7. RE: ARM not working?

Kudos

chulcher

MVP GURU ELITE

Posted Mar 13, 2024 10:46 AM
Edited by chulcher Mar 13, 2024 10:46 AM

Reboot the MCR.

Run "airmatch runnow full".

A solution should be generated after a time.

If that doesn't work, open a case with TAC as you've got some sort of issue going on.

------------------------------
Carson Hulcher, ACEX#110
------------------------------

Original Message

Original Message:
Sent: Mar 13, 2024 10:41 AM
From: safranek
Subject: ARM not working?

(mm1) [mynode] #show airmatch debug optimization                                                                                                                                                             Channel  OpmodeSeq   Time                   APs   [5GHz] Radios Cost  Conflict      [2GHz] Radios Cost  Conflict      [6GHz] Radios Cost  Conflict    Type                 Computed Computed----- -------------------   -----         ------ ----- --------             ------ ----- --------             ------ ----- --------    -------------------- -------- --------#606    2024-03-02_05:00:12       2              2     2        0                  2     4        0                  0    NA       NA               Scheduled      Yes       No* EIRP is always computed in optimization(mm1) [mynode] #show airmatch profileAirMatch profile----------------Parameter          Value---------          -----schedule           Enableddeploy-hour        5 AMquality-threshold  8 percent(mm1) [mynode] #

Original Message:
Sent: Mar 13, 2024 10:35 AM
From: 802.zak
Subject: ARM not working?

What is the output of:

#show airmatch debug optimization
#show airmatch profile

If I issue this command on MM, see nothing.

(mm1) [mynode] #show airmatch solution list-all# Band Radio              Chan/Opt#     CBW      EIRP(dBm)/Opt# Client Band  APName                                                                 Pref  Pref  ---- -----------------  ------------- -------- -------------- ------ ----  ----------[*] regarded frozen | [#] result adjusted to match feasibility Client Preference    - [p] HE Preferred | [n] Non-HE Preferred | [a] Allow-AllBand Preference      - [L] 5GHz-Lower | [U] 5GHz-Upper | [F] 5GHz-Full (mm1) [mynode] #(mm1) [mynode] #show ap database-summary AP Database Summary-------------------AP Mode              Total Up  Total Down  Total Upgrading*  Total Rebooting*  RAP Up  RAP Down  RAP Upgrading*  RAP Rebooting*  Active Up  Standby Up-------              --------  ----------  ----------------  ----------------  ------  --------  --------------  --------------  ---------  ----------Access Points        600       0           0                 0                 0       0         0               0               0          0Air Monitors         0         0           0                 0                 0       0         0               0               0          0Wired Access Points  0         0           0                 0                 0       0         0               0               0          0Mesh Portals         0         0           0                 0                 0       0         0               0               0          0Mesh Points          0         0           0                 0                 0       0         0               0               0          0Spectrum Monitors    0         0           0                 0                 0       0         0               0               0          0*Upgrading, Rebooting, Active and Standby counts only reflect APs registered on this controller.Unprovisioned Access Points:1                      Duplicated AP Name:0(mm1) [mynode] #

However something working about Airmatch, I see radar detection events:

(mm1) [mynode] #show airmatch event all-events all-apsBand Event Type   Radio             Timestamp           Chan    CBW      New Chan    New CBW   APName---- ------------ ----------------- ------------------- ------- -------- ----------- --------- ----------5GHz RADAR_DETECT bc:9f:e4:aa:aa:aa 2024-03-13_09:06:14     116    40MHz          52     40MHz 5GHz RADAR_DETECT b8:3a:5a:bb:bb:bb 2024-03-13_08:05:33     120    40MHz          60     40MHz 5GHz RADAR_DETECT bc:9f:e4:cc:cc:cc 2024-03-13_08:01:56      60    40MHz         108     40MHz 5GHz RADAR_DETECT bc:9f:e4:dd:dd:dd 2024-03-13_07:30:39     128    40MHz         132     40MHz 5GHz RADAR_DETECT bc:9f:e4:ee:ee:ee 2024-03-12_17:34:26     100    40MHz         116     40MHz 5GHz RADAR_DETECT b8:3a:5a:ff:ff:ff 2024-03-12_14:50:20     116    40MHz         112     40MHz 5GHz RADAR_DETECT bc:9f:e4:aa:aa:aa 2024-03-12_14:38:57     108    40MHz         124     40MHz 5GHz RADAR_DETECT bc:9f:e4:bb:bb:bb 2024-03-12_14:33:04     116    40MHz         124     40MHz 5GHz RADAR_DETECT bc:9f:e4:cc:cc:cc 2024-03-12_14:28:08     132    40MHz         128     40MHz 5GHz RADAR_DETECT bc:9f:e4:dd:dd:dd 2024-03-12_13:05:18     124    40MHz         120     40MHz 5GHz RADAR_DETECT b8:3a:5a:ee:ee:ee 2024-03-12_12:54:44      60    40MHz         100     40MHz 5GHz RADAR_DETECT bc:9f:e4:ff:ff:ff 2024-03-12_10:57:00     136    40MHz          64     40MHz 5GHz RADAR_DETECT bc:9f:e4:aa:aa:aa 2024-03-12_10:56:53      56    40MHz          64     40MHz 5GHz RADAR_DETECT bc:9f:e4:bb:bb:bb 2024-03-12_10:33:19     124    40MHz         108     40MHz 5GHz RADAR_DETECT bc:9f:e4:cc:cc:cc 2024-03-12_09:27:23     132    40MHz         116     40MHz 5GHz RADAR_DETECT bc:9f:e4:dd:dd:dd 2024-03-12_09:23:51      52    40MHz         116     40MHz 5GHz RADAR_DETECT b8:3a:5a:ee:ee:ee 2024-03-12_09:00:19     124    40MHz         132     40MHz 5GHz RADAR_DETECT bc:9f:e4:ff:ff:ff 2024-03-11_14:32:16     116    40MHz         124     40MHz 5GHz RADAR_DETECT bc:9f:e4:aa:aa:aa 2024-03-11_14:23:27      64    40MHz          56     40MHz --More-- (q) quit (u) pageup (/) search (n) repeat

Original Message:
Sent: Mar 12, 2024 10:55 AM
From: 802.zak
Subject: ARM not working?

Are you using AirMatch?

From the MM you can use the "show airmatch solution ap-name" - as well as other optimization commands - to get additional details.

Wireless Access

ARM not working?

safranekMar 12, 2024 10:26 AM

chulcherMar 12, 2024 10:53 AM

802.zakMar 12, 2024 10:55 AM

safranekMar 13, 2024 04:27 AM

802.zakMar 13, 2024 10:36 AM

safranekMar 13, 2024 10:41 AM

chulcherMar 13, 2024 10:46 AM

1. ARM not working?

2. RE: ARM not working?

3. RE: ARM not working?

4. RE: ARM not working?

5. RE: ARM not working?

6. RE: ARM not working?

7. RE: ARM not working?

Airheads Community

Contact

Company

Support

Partners

Wireless Access

ARM not working?

safranekMar 12, 2024 10:26 AM

chulcherMar 12, 2024 10:53 AM

802.zakMar 12, 2024 10:55 AM

safranekMar 13, 2024 04:27 AM

802.zakMar 13, 2024 10:36 AM

safranekMar 13, 2024 10:41 AM

chulcherMar 13, 2024 10:46 AM

1. ARM not working?

2. RE: ARM not working?

3. RE: ARM not working?

4. RE: ARM not working?

5. RE: ARM not working?

6. RE: ARM not working?

7. RE: ARM not working?

Related Content

Does AirMatch avoid using channels where radar is detected?

Detecting Radar event

ARM with Airmatch

Airmatch ap freeze - high noise/radar?

40Mhz Channel Width 5Ghz

Airheads Community

Contact

Company

Support

Partners