09-25-2019 12:09 PM
Here is the output from "Show capwap client"
CAPWAP client: Enabled
CAPWAP transport mode: UDP
RUN state: Connected securely to the CAPWAP server
CAPWAP client IP: 10.0.0.83
CAPWAP server IP: 34.202.197.40
HiveManager Primary Name:cloud-va2-cws-8.aerohive.com
HiveManager Backup Name:
CAPWAP Default Server Name: 34.202.197.40
Virtual HiveManager Name: XQCLFAXH
Server destination Port: 12222
CAPWAP send event: Enabled
CAPWAP DTLS state: Enabled
CAPWAP DTLS negotiation: Enabled
DTLS next connect status: Enable
DTLS always accept bootstrap passphrase: Enabled
DTLS session status: Connected
DTLS key type: passphrase
DTLS session cut interval: 5 seconds
DTLS handshake wait interval: 60 seconds
DTLS Max retry count: 3
DTLS authorize failed: 0
DTLS reconnect count: 0
Discovery interval: 5 seconds
Heartbeat interval: 30 seconds
Max discovery interval: 10 seconds
Neighbor dead interval:105 seconds
Silent interval: 15 seconds
Wait join interval: 60 seconds
Discovery count: 0
Max discovery count: 3
Retransmit count: 0
Max retransmit count: 2
Primary server tries: 0
Backup server tries: 0
Keepalives lost/sent: 0/30788
Event packet drop due to buffer shortage: 0
Event packet drop due to loss connection: 23
09-25-2019 02:15 PM
This guide reviews how to manually connect HiveOS devices to the HiveManager: https://thehivecommunity.aerohive.com/s/article/CAPWAP-Guide-for-HiveManager-NG
Since your device is showing connected securely, my best guess is that it has outdated information for the HiveManager address. The guide I've linked to reviews how find the HiveManager information for your instance and how to manually add that information to the AP via the CLI. It also reviews some troubleshooting steps to take if the device still will not connect for you.