Controller Based WLANs

How to delete stale entries (like Aps showing down in show ap database) on the Local controller?
Q:

How to delete stale entries (like Aps showing down in show ap database) on the Local controller?



A:

 

In Master controller these ap stale entries been deleted by executing clear gap-db command however in local controller this command was not executable. It will throw error message "This command must be run on the active master"

On Local controller:
===================

 #clear gap-db ap-name AP-93H
This command must be run on the active master.

 #clear gap-db lms lms-ip  10.17.170.101
This command must be run on the active master.

In this case there are two ways we can clear the ap stale entries on the local controller.

1. Restarting the STM process on Local controller.
2. Executing clear gapdb command on the Master controller using LMS Ip address as shown below:
#clear gap-db lms lms-ip < IP address of the local controller showing APs as down )

 

Example:

(local-3600) #show ap database

AP Database
-----------
Name    Group     AP Type  IP Address     Status  Flags  Switch IP      Standby IP
----    -----     -------  ----------     ------  -----  ---------      ----------
AP-93H  cube-psk  93H      10.17.170.123  Down           10.17.170.101  0.0.0.0

local-3600) #process restart stm
WARNING: Do you really want to restart process: stm (y/n): y
Restarting: stm

local-3600) #show ap database

AP Database
-----------
Name  Group  AP Type  IP Address  Status  Flags  Switch IP  Standby IP
----  -----  -------  ----------  ------  -----  ---------  ----------

Flags: U = Unprovisioned; N = Duplicate name; G = No such group; L = Unlicensed
       I = Inactive; D = Dirty or no config; E = Regulatory Domain Mismatch
       X = Maintenance Mode; P = PPPoE AP; B = Built-in AP
       R = Remote AP; R- = Remote AP requires Auth; C = Cellular RAP;
       c = CERT-based RAP; 1 = 802.1x authenticated AP; 2 = Using IKE version 2
       u = Custom-Cert RAP; S = Standby-mode AP; J = USB cert at AP
       M = Mesh node; Y = Mesh Recovery

Version History
Revision #:
2 of 2
Last update:
‎05-17-2016 10:53 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.