After upgrading the controller software, the AP can't come up. We can see PAPI getting setup on the controller datapath. What could be the reason for which the APs stuck at upgrading state on the Controller?
Why do we see some strange ports for traffic between AP and Controller after code upgrade of Controller?
Environment Information :
Any Aruba Controller
Any Access Points
Any Aruba OS
Symptoms : We can see there is PAPI established from AP to the Controller, however the AP never completes upgrade. We can see from the switch logs that the AP is trying to access ports like 1025, 1026, 1039 etc.
Cause : File Transfer Protocol (FTP) dynamically uses high ports for transferring data between client and server. If the intermediate device between the FTP client and server blocks the ephemeral ports, then FTP fails.
Related Links : https://kb.arubanetworks.com/app/answers/detail/a_id/63