Wireless Access

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
------------------------------

Common solution:  If an APs information in the CPSEC whitelist is modified by a user (name or ap-group), that will  silently revert any changes made through manual provisioning.  That is why I advise either to ONLY use the CPSEC OR Manual provisioning to change the ap-group, but not both at one time.

Edit: To be clear, just leave CPSEC on auto approve or approve APS manually (more administrative work), but do not modify the ap-name or ap-group in the CPSEC whitelist if you don't want to run into the issue above.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
------------------------------

Original Message:
Sent: Jun 13, 2021 12:15 AM
From: Neal Vadekar
Subject: AP reprovisioning does not work, the AP always reverts back to original name and group - one possible Solution

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
------------------------------

Hi,

This may not be related but I found that when I re-provisioned some APs if the AP Whitelist has the AP Name and group populated for that AP MAC Address it will always revert to that name and group. Update the name and group in the whitelist and reboot the AP, it will come back with the correct group and name.

Again, may not be related to your issue but worth checking.

Regards

Adrian

------------------------------
Adrian Jones
------------------------------

Original Message:
Sent: Jun 13, 2021 12:15 AM
From: Neal Vadekar
Subject: AP reprovisioning does not work, the AP always reverts back to original name and group - one possible Solution

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
------------------------------