Setup:
- MM & MC running 8.6.x
- "AP-xyz" already provisioned with customer assigned name and group
- CPsec enabled, CAP whitelist, AP is approved but no other settings applied
- new group created for Spectrum Monitor functions, no AP yet assigned
Situation:
- Customer reprovisions AP-xyz to new AP-Group and AP-Name, AP reboots, at nvram, new name and group are there
- AP connected to cluster, shows new name, reboots again
- AP connects again but has reverted back to original name and original group
Solution: (maybe there is a better solution, but this worked)
- MM # export gab-db (copy to PC, notice the sql dump has your old AP name, not the new one you tried to create)
- power off AP-xyz, delete AP-zyz from CAP whitelist
- on MM /mm context # clear gap-db ap-name AP-xyz
- MM # export gab-db (copy to PC, notice the sql dump does not have your old or new AP name)
- MM # show ap database (notice AP-xyz old or new name is not there)
- lms MC # show ap database (notice AP-xyz old name is still there)
- lms MC # write erase all.... let it re-ZTP and get managed by you MM with a fresh install
- lms MC, after ztp, notice show ap database does not have "AP-xyz" anymore
- boot AP-zyx, purge, save, boot, (or setenv with new desired name and group to save time), CPsec allow it, provision it
- notice it works now
------------------------------
Neal Vadekar
------------------------------