Controller Based WLANs

How to manually re-classify an AP or client on the WMS database?
Q:

How to manually re-classify an AP or client on the WMS database? 



A:

AP Re-classification: 

An AP on the WMS database can be manually re-classified as interfering, manually-contain, neighbor, rogue, suspected-rogue or valid using the below command: 

#wms ap <bssid> mode <classification> add

 

An AP can be classified into the below types: 

(Rajaguru-3400) #wms ap ac:a3:1e:b2:f6:c0 mode ?
interfering             mark it as AP outside the enterprise. Kick off
                        classification
manually-contain        manually enable denial of service from this AP
neighbor                mark it as AP outside the enterprise. Do not kick
                        off classification
rogue                   mark it as rogue AP inside the enterprise
suspected-rogue         mark it as suspected rogue AP inside the enterprise
valid                   setting it to valid makes it part of enterprise

 

Examples:  

(Rajaguru-3400) #show wms ap list | include ac:a3:1e:b2:f6:c0
94:b4:0f:c3:a7:2c  2      ac:a3:1e:b2:f6:c0  test                             25    183  288   interfering           0                  wpa2-psk-aes    no

(Rajaguru-3400) #wms ap ac:a3:1e:b2:f6:c0 mode manually-contain add
(Rajaguru-3400) #show wms ap list | include ac:a3:1e:b2:f6:c0
94:b4:0f:c3:a7:2c  2      ac:a3:1e:b2:f6:c0  test                             25    176  0     manually-contain      0                  wpa2-psk-aes    no

(Rajaguru-3400) #wms ap ac:a3:1e:b2:f6:c0 mode neighbor add
(Rajaguru-3400) #show wms ap list | include ac:a3:1e:b2:f6:c0
94:b4:0f:c3:a7:2c  2      ac:a3:1e:b2:f6:c0  test                             34    197  1     neighbor              0                  wpa2-psk-aes    no​

 

Note:
We cannot re-classify a suspected-rogue to an interfering AP, however, we can change the confidence-level of the suspected-rogue. 

(Rajaguru-3400) #show wms ap list | include 6c:f3:7f:77:a5:34
ac:a3:1e:c6:36:38  1      6c:f3:7f:77:a5:34  test-preauth                     13    202  9     suspected-rogue(20%)  0                 wpa2-psk-aes    no

(Rajaguru-3400) #wms ap 6c:f3:7f:77:a5:34 mode interfering add
(Rajaguru-3400) #show wms ap list | include 6c:f3:7f:77:a5:34
ac:a3:1e:c6:36:38  1      6c:f3:7f:77:a5:34  test-preauth                     13    202  9     suspected-rogue(20%)  0                 wpa2-psk-aes    no

(Rajaguru-3400) #wms ap 6c:f3:7f:77:a5:34 mode suspected-rogue 70 add
(Rajaguru-3400) #show wms ap list | include 6c:f3:7f:77:a5:34
ac:a3:1e:c6:36:38  1      6c:f3:7f:77:a5:34  test-preauth                     13    202  9     suspected-rogue(70%)  0                 wpa2-psk-aes    no

 

Client Re-classification: 
A Client on the WMS database can be manually re-classified as interfering, manually-contain or valid using the below command: 

#wms client <client-mac> mode <classification> add

 

Examples: 

(Rajaguru-3400) #show wms client list | include cc:29:f5:6d:8b:d6
94:b4:0f:c3:a7:2c  2      cc:29:f5:6d:8b:d6  WebTest           30    1    1     interfering  18:64:72:5c:8b:a0

(Rajaguru-3400) #wms client cc:29:f5:6d:8b:d6 mode manually-contain add
(Rajaguru-3400) #show wms client list | include cc:29:f5:6d:8b:d6
94:b4:0f:c3:a7:2c  2      cc:29:f5:6d:8b:d6  WebTest           30    1    1     manually-contain  18:64:72:5c:8b:a0

(Rajaguru-3400) #wms client cc:29:f5:6d:8b:d6 mode valid add
(Rajaguru-3400) #show wms client list | include cc:29:f5:6d:8b:d6
94:b4:0f:c3:a7:2c  2      cc:29:f5:6d:8b:d6  WebTest           30    1    1     valid        18:64:72:5c:8b:a0

 

In a Master-local setup, the WMS database is maintained on the Master controller. Hence the re-classification can be done only on the Master, not on the Local controller. 

Version History
Revision #:
2 of 2
Last update:
‎03-27-2017 07:42 AM
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.