Config Cannot be Uploaded to RADIUS APs

  • 1
  • Question
  • Updated 4 years ago
  • Answered
In a Hive which has been running fine for over a year, I can successfully upload a config change the APs, but not to the 3 APs which are RADIUS functioning servers.
I think it may be related to when the school cut over to a new ISP, as the external router has been replaced, so they have a new external IP.

Any ideas if this could have caused this kind of problem??

When I try a auto or complete update, it gets to the Loading 0% status, then fails jumping to Abort Rety message.

I’ve tried rebooting those APs and retrying, but have the same problem. It’s odd how the other APs are fine.

Could the new external router be affecting the CAPWAP ports?
Wonder what is different for the RADIUS ones? The other APs can still client to the RADIUS APs and authenticate properly.

Looking forward to solving this annoying problem.

Photo of Jason Hills

Jason Hills

  • 78 Posts
  • 3 Reply Likes
  • confused!

Posted 4 years ago

  • 1
Photo of Brian Powers

Brian Powers, Champ

  • 391 Posts
  • 91 Reply Likes
If you hover over the message, what does it say as a reason for the failure? 

Photo of Jason Hills

Jason Hills

  • 78 Posts
  • 3 Reply Likes
Thanks Brian, sorry I didn't think of hovering.

Is this straight forward?

I guess the reason for the current clients being able to authenticate is thanks to the cache on the APs.
Photo of Roberto Casula

Roberto Casula, Champ

  • 231 Posts
  • 111 Reply Likes
Might they be blocking SSH outbound from the AP management network to HiveManager as well as CAPWAP (UDP 12222). CAPWAP is used for most things, but SSH is required for anything that involves a file transfer, such as distributing certificates, CWP files and updating the OS.