I did find the issue.
In the AP-Group was a LMS - IP configured from a test from a former colleague...
This was an old controller...
We did not use this AP-Group yet, we use this AP-Group only on the new Controller, thats why did not recognized that there is a LMS IP configured.
------------------------------
Markus Rost
------------------------------
Original Message:
Sent: Feb 19, 2021 05:16 AM
From: Markus Rost
Subject: Accesspoints (AP-20X) will not connect new Controller after migtrating from Alcatel-Lucent V6.5.5.3 to Aruba AOS 8.6.0.5
here are some loginfos from one of the Accesspoints:
Feb 18 17:55:48 localdb[20726]: <133006> <20726> <ERRS> |localdb| User 80:8d:b7:ca:34:0a Failed Authentication (Processing FETCH_REQ on DBType(3))
Feb 18 17:56:09 cluster_upgrade_mgr[21263]: <396001> <22126> <ERRS> |cluster_upgrade_mgr| update_aac_in_ap_info, Unable to find controller_info for new aac 172.28.240.227 of AP 80:8d:b7:ca:34:0a
Feb 18 17:56:09 cluster_upgrade_mgr[21263]: <396001> <22126> <ERRS> |cluster_upgrade_mgr| update_aac_in_ap_info, Unable to find controller_info for old aac 172.28.240.227 of AP 80:8d:b7:ca:34:0a
Feb 18 17:56:19 cluster_upgrade_mgr[21263]: <396001> <22126> <ERRS> |cluster_upgrade_mgr| update_aac_in_ap_info, Unable to find controller_info for new aac 172.28.240.227 of AP 80:8d:b7:ca:34:0a
Feb 18 17:56:19 cluster_upgrade_mgr[21263]: <396001> <22126> <ERRS> |cluster_upgrade_mgr| update_aac_in_ap_info, Unable to find controller_info for old aac 172.28.240.227 of AP 80:8d:b7:ca:34:0a
Feb 18 17:56:31 cluster_upgrade_mgr[21263]: <396001> <22126> <ERRS> |cluster_upgrade_mgr| update_aac_in_ap_info, Unable to find controller_info for new aac 172.28.240.227 of AP 80:8d:b7:ca:34:0a
Feb 18 17:56:31 cluster_upgrade_mgr[21263]: <396001> <22126> <ERRS> |cluster_upgrade_mgr| update_aac_in_ap_info, Unable to find controller_info for old aac 172.28.240.227 of AP 80:8d:b7:ca:34:0a
Auto-cert Provision is enabled.
on a packet capture on one of the devices between the controller and accesspoint i can see that the accesspoint will only connect to the new controller.
On ap-debug there is nothing. Perhaps i do something wrong with the commands???
------------------------------
Markus Rost
Original Message:
Sent: Feb 19, 2021 05:07 AM
From: Koen V
Subject: Accesspoints (AP-20X) will not connect new Controller after migtrating from Alcatel-Lucent V6.5.5.3 to Aruba AOS 8.6.0.5
You have auto-cert provisioning enabled I suppose?
Did the AP get a certified state? Check with show whitelist-db cpsec.
Could it possibly be 'ping-ponging' between controllers with different firmware?
Do you see the AP show up anywhere in ap-debug? Does that give any hints on whatever is goign on?
------------------------------
Koen V
Original Message:
Sent: Feb 19, 2021 04:57 AM
From: Markus Rost
Subject: Accesspoints (AP-20X) will not connect new Controller after migtrating from Alcatel-Lucent V6.5.5.3 to Aruba AOS 8.6.0.5
Hello,
i have a strange issue. Some words of out setup.
Old-Environment 2 Alcatel-Lucent Controller ( similiar Aruba 7210) with Version 6.5.5.3 and still 130 Accesspoints in differnet locations.
New-Environment 2 Aruba Controller 7210 with Version 8.6.0.5 and 250 Accesspoints in different locations. Managed by a MobilityMaster. These two controllers are in MD - Group "Prod".
i moved already a lot of Accesspoints from the old Alcatel Controllers to the new Environment without any problems.
Now i took a one of the Alcatel - Controllers (the Backup) and upgraded this to a Aruba 8.6.0.5 and put it to the Mobility Master in MD-Group "Office".
This works also fine. Now i moved some of the Accesspoints from the Aruba-Controllers in "Prod" to the Controller in "Office" This works also fine.
All Controllers have the same Groups and VLANs.
Now i want to move some Accesspoints from the old Alcatel - Controllers to the new "Office"-Controller.
After changing the IP of the MasterSwitch the Accesspoints did a reboot and i can see it connecting to the "Office"-controller. Then the Accesspoint did a next reboot (i think after Firmwareupgrade) and after that it will not connect anymore. It is still down on Mobility Master but it is still pingable.
I did not have console-Access to these Accesspoints.
I also tried to do a ap-debug on the controller, but i can not see anything on the controller.
Are there some other troubleshooting tipps, where i can see why the controller did not accept the Accesspoint.
I can reboot the Accesspoints with changing the power settings on the Switch.
Thanks
regards
Markus
------------------------------
Markus Rost
------------------------------