I would recommend reaching out to TAC Support, as NesaM sees the same. What is strange to me is that the AP is coming up with 6.4 firmware, but that would indicate that there is an issue with the 8.7.1.1 firmware after being pushed, AP will use backup firmware (6.4), connect to the controller, gets upgraded again, then fails again. What I see in other case notes is that the firmware should be 6.5 or up to allow the upgrade to 8.7, and if your backup image is 6.4 and in addition, there is a problem pushing the 8.7.1.1 version, that may result in what you see. I don't know if you can easily upgrade the backup firmware.
TAC will be able to do a better analysis and find a solution.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
------------------------------
Original Message:
Sent: Mar 19, 2021 01:26 AM
From: Tuna AKYOL
Subject: APs are going up and down repeadetly
I did not say that the APs trying to communicate with MM, they already resolved controller vrrp ip address and trying to communicate with cluster.
Thanks
------------------------------
Tuna AKYOL
Original Message:
Sent: Mar 18, 2021 08:53 PM
From: Colin Joseph
Subject: APs are going up and down repeadetly
Remember that the APs need to terminate and communicate with the Mobility Controller, NOT the MM.
------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
Original Message:
Sent: Mar 17, 2021 03:31 PM
From: Tuna AKYOL
Subject: APs are going up and down repeadetly
Hi community,
My customer has 2 different MMs and there are two different cluster 7210 controllers under the MMs. All APs (count 525) were terminated on the first MM which is 8.6.0.6. And then i moved all APs to the new deployed MM which is 8.7.1.1 ( at same DC ). Some APs could not registered to new cluster. When i look for the logs i saw this message;
-<399803> <3680> <ERRS> |stm| An internal system error has occurred at file sapm_ap_mgmt.c function sapm_proc_hello_req line 19376 error AP: ap-01-01 image version mismatch. bootfile is ipq806x.ari, build string is ArubaOS version 6.4.4.16 for 32x
And then i trace the AP boot process via console, AP is trying to come up with 6.4.4.16 version and controller refused as expected.
These 32x APs at the remote locations and there is MPLS line between DC and locations.
Any suggestion for this situation ?
------------------------------
Tuna AKYOL #ACCA #ACMP
------------------------------