
Instant APs Managed by Aruba Central |
20
In Central managed networks, the AP and Central communicate over a websocket connection to exchange
configuration and monitoring data. Therefore, uninterrupted connectivity is integral in Central managed
networks and loss in internet connectivity can stall configuration changes and monitoring updates.
The following procedure describes how to troubleshoot issues, if the AP fails to receive configurations from
Central:
1.
Check the Configuration Status of Central
2.
Ensure That the AP is Placed in a Configuration Group in Central
3.
Verify the Configurations Received from Central
4.
Restart the Central Websocket Connection
Before starting the troubleshooting process, ensure that the AP is connected to Central.
Check the Configuration Status of Central
Run the
show ap debug cloud-server
command in the CLI of the AP to view the status of the Central
connection. Check
cloud config recved
to identify if the AP has received configurations from Central. A
TRUE
state implies that the AP has received configurations and a
FALSE
state implies that the AP has not
received configurations.
The sample below displays the Central connection status, generated by the
show ap debug cloud-server
command:
(Instant AP)# show ap debug cloud-server
IAP mgmt mode
:athena-mgmt
cloud config recved
:TRUE
autojoin mode
:disable
state diff
:disable
Device Cert status
:SUCCESS
Device info send
:SUCCESS
Aruba Central server
:internal.central.arubanetworks.com
Aruba Central server path
:/ws
Aruba Central proxy server
:None
Aruba Central redirect from
:internal.central.arubanetworks.com
Aruba Central Protocol
:WSS
Aruba Central uptimes
:1h:0m:48s
Aruba Central status
:Login_done
Cloud Debug Statistics
-----------------------
Key
Value
---
-----
Connect establish success
1(10)
Connect establish failed
0(2)
Login done to init
0(9)
Login done times
1(10)
Connect retry times
1(12)
clarity send
60(871)
Device Info send
1(10)
Domain list receive
1(10)
Domain response send
1(10)
Cloud Last connect status
-------------------------
Last connect ID
:12
Last connect time
:2020-04-24 00:23:20
Last connect trigger
:login down, retry
Cloud Last connect fail status
-------------------------
Last fail server
:internal.central.arubanetworks.com
Last fail time
:2020-04-23 22:44:38
Last fail reason
:tcp connect error
Cloud Last login down status