@gsaldarriaga@cosma.com wrote:
Did you remove the AP from controller? ... then try to purge the AP..
connect the AP again and wait until controller apply config..
From the CLI, do the command "clear gap-db ap-name xxx", where xxx is the name of the down AP. Do this for each AP you want to remove.
GUI - click on Monitoring > All Access Points > Clear (to the right of the AP you want removed).
Regasrds,
Giovanni Saldarriaga
Thank you Giovanni, your hints helped to clear the situation!
1) show ap database | include Down
2) "clear gap-db ap-name xxx"
3) Power cycle each AP *
AP does reconnect to a controller
4) show ap database | include xxx
If it reconnected to the lms-backup controller
5) apboot ap-name
Else if connected to the home- / aruba-master controller directly
all APs are working properly again:
6) sh ap active
* rather difficult if the APs at all the remote sites are attached to an non-PoE switch...
Now I am searching for a) the cause,
and b) why it did not switch back from the lms-backup to the main- /aruba-master controller
@
ap system-profile <profile>
lms-preemption
lms-hold-down period <seconds>
I have no "lms-hold-down period" , normally it does /did work did failback
do you know what is the default time in <seconds> ?