Is anyone aware of any known bugs with running gap-db commands? Running 'clear gap-db wired-mac c8:b5:ad:c6:6c:3e' doesn't appear to be removing the entry from the Conductor.We have a few hundred APs which need removing from the Conductor GUI which do not seem to budge from running the command above. In theory would running 'ap gap-db re-initialize' remove these stale entries without having to go run a command per MAC address? These entries have been removed from the allowlist and are speaking to a different Conductor completely. Software version: 18.104.22.168 - nothing in the release notes known issues.
Have you tried to reinitialize the DB?https://www.arubanetworks.com/techdocs/CLI-Bank/Content/aos8/ap-gap-db.htm
I haven't run this command yet. Which was kind of my question if I should or not. Are you aware of this being service affecting? Or this is purely a db change and will not affect the operation of the APs.
© Copyright 2023 Hewlett Packard Enterprise Development LPAll Rights Reserved.