cancel
Showing results for 
Search instead for 
Did you mean: 

AP122 turns irresponsive when upload config / upgrade firmware / reboot.

AP122 turns irresponsive when upload config / upgrade firmware / reboot.

sergi_dupe
New Contributor III

Everytime I upload any configuration, upgrade the firmware of my AP122 or a simply reboot, the AP losses the connection with HiveManager and the status led of the AP turns orange. Then the AP keeps irresponsive and the only solution is to push the reset button of the AP or perform a 'reset config' command through CLI.

25 REPLIES 25

sergi_dupe
New Contributor III

Hi Brian,

capwap server 34.253.190.206 (server in which my ap is attacking) responds to ping requests.

 

When I ran Sam's commands, all of them worked well...

Respect to changes in native VLAN or mgt0 VLAN are set to 1 (default).

AnonymousM
Valued Contributor II

Sergi,

 

Can you also run a "capwap ping <server IP>"? This will send ICMP over the CAPWAP port. This should succeed. I say that only because it was connected prior to you updating the AP in some form.

 

It's odd that a firmware update is also impacting its connection. I'd expect the config update to possibly cause this if something was improperly configured and being pushed to the AP (native VLAN, or mgt0 VLAN change).

 

Also intriguing that a simple reboot of the AP breaks the connection.

 

When you ran Sams above commands, did they all work? I traditionally use "capwap client server name <HM IP or name> vs. "hivemanager <hivemanager address> primary". It looks like "hiveManager <server> primary" does indeed work as does "hiveManager vhm-name <vhm name>"! Learned something new from this thread.

 

sergi_dupe
New Contributor III

Sent email with tech data.

sergi_dupe
New Contributor III

Bingo! again the ip appears. However, AP is still without connection.

We will wait 15 minutes. If there is no CAPWAP connection, then I will resend techdata log via email.

samantha_lynn
Esteemed Contributor III

That's good news. The AP is likely just trying to find the correct server. If you run the "show capwap client" command, then wait about 10-20 seconds, then run it again, do you see anything change or any information fill in for you? It can take up to 15 minutes for the APs to complete the connection process as well, so it might just be taking its time.

GTM-P2G8KFN