Controller-less WLANs

How to manually re-classify a monitored AP in Instant?
Requirement:

Aruba APs can monitor the other APs in the RF environment and classify them as valid, Interfering, rogue, or suspected-rogue. Sometimes we may need to manually re-classify a monitored AP. 

How to manually re-classify a monitored AP as valid, Interfering, rogue, suspected-rogue, manually-contained or neighbor in Instant? 



Solution:

We can manually re-classify a monitored AP by specifying the phy_type and rap_type. Below are the different phy_type and rap_type values. 

 

Rajaguru-IAP# show ids phy-types

Physical Types
--------------
Keyword  Value
-------  -----
b        0
a        1
g        2
ag       3

Rajaguru-IAP# show ids rap-types

RAP Types
---------
Keyword            Value
-------            -----
valid              0
interfering        1
rogue              2
dos-attack         3   (Manually contained) 
unknown            4
known-interfering  5   (Neighbor) 
suspect-rogue      6

 



Configuration:

The command to manually re-classify a monitored AP is: 

Rajaguru-IAP# ids-reclassify ap <monitored-AP-bssid> <phy_type> <rap_type> 



Verification

Below is an example of re-classifying an AP to a different type.

 

Rajaguru-IAP# show ap monitor ap-list | include testssid
18:64:72:19:76:c0  testssid               11    interfering            80211b/g-HT-20  disable  116215/45805  25/1   wpa2-psk-aes    0      0        54        0         41         0      no    58151
18:64:72:19:76:d0  testssid               149   interfering            80211a-VHT-80   disable  115190/12283  6/0    wpa2-psk-aes    0      0        60        0         35         0      no    0
Rajaguru-IAP#
Rajaguru-IAP# ids-reclassify ap 18:64:72:19:76:c0 0 2
Rajaguru-IAP# ids-reclassify ap 18:64:72:19:76:d0 1 2
Rajaguru-IAP#
Rajaguru-IAP# show ap monitor ap-list | include testssid
18:64:72:19:76:c0  testssid               11    rogue                  80211b/g-HT-20  enable   116293/45806  21/2    wpa2-psk-aes    0      0        54        0         41         0      no    58151
18:64:72:19:76:d0  testssid               149   rogue                  80211a-VHT-80   enable   115268/12284  1/0     wpa2-psk-aes    0      60       60        35        35         0      no    0
Rajaguru-IAP#
Rajaguru-IAP# ids-reclassify ap 18:64:72:19:76:c0 0 5
Rajaguru-IAP# ids-reclassify ap 18:64:72:19:76:d0 1 5
Rajaguru-IAP#
Rajaguru-IAP# show ap monitor ap-list | include testssid
18:64:72:19:76:c0  testssid               11    neighbor               80211b/g-HT-20  disable  116420/45903  0/0     wpa2-psk-aes    0      53       55        41        40         0      no    58151
18:64:72:19:76:d0  testssid               149   neighbor               80211a-VHT-80   disable  115395/12285  3/0     wpa2-psk-aes    0      0        60        0         35         0      no    0
Rajaguru-IAP#
Rajaguru-IAP# ids-reclassify ap 18:64:72:19:76:c0 2 3
Rajaguru-IAP# ids-reclassify ap 18:64:72:19:76:d0 1 3
Rajaguru-IAP#
Rajaguru-IAP# show ap monitor ap-list | inc testssid
18:64:72:19:76:c0  testssid               1     manually-contain       80211b/g-HT-20  enable   117090/46181  0/0      wpa2-psk-aes    0      59       57        35        38         0      no    58151
18:64:72:19:76:d0  testssid               149   manually-contain       80211a-VHT-80   enable   116065/12291  66/1     wpa2-psk-aes    0      0        60        0         35         0      no    0
Rajaguru-IAP#

 

Version History
Revision #:
2 of 2
Last update:
‎03-07-2016 12:35 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.