ā07-09-2018 01:56 PM
Solved! Go to Solution.
ā07-19-2018 10:09 PM
There are many different things that can affect an APs CAPWAP connection. Commonly firewalls, IDP, content filters and MPLS networks are the culprits. Please be sure you have white listed/allowed the APs full access on ports UDP 12222 and TCP 22. As a test you can switch an AP over to HTTP over TCP on 80 and 443.
SSH into an AP and run the following commands in order.
no capw cli en
capw cli transport http
capw cli en
save conf
The AP will now traverse ports 80 and 443 instead of 12222 and 22.
ā07-19-2018 10:09 PM
There are many different things that can affect an APs CAPWAP connection. Commonly firewalls, IDP, content filters and MPLS networks are the culprits. Please be sure you have white listed/allowed the APs full access on ports UDP 12222 and TCP 22. As a test you can switch an AP over to HTTP over TCP on 80 and 443.
SSH into an AP and run the following commands in order.
no capw cli en
capw cli transport http
capw cli en
save conf
The AP will now traverse ports 80 and 443 instead of 12222 and 22.
ā07-10-2018 05:56 PM
ā07-10-2018 02:49 PM
Are these APs in a remote facility across a WAN? It's possible the capwap threshold is being triggered. If you have ssh our console access you can run the "show version" common to check the APs uptime. A command to check capwap status is "show capwap client."
Best,
BJ
ā07-09-2018 04:53 PM