Aerohive access point, Руководство по развертыванию

Страница: 131 / 221

Chapter 11 Basic Configuration Examples
130 Aerohive
Figure 4 CAPWAP Connection process—beginning from the run state
The CAPWAP client (HiveAP) pings the CAPWAP server (HiveManager)
but receives no responses within the neighbor dead interval.
The client transitions to the Discovery state and begins sending
Discovery Request messages (broadcast or unicast).
If the client continues to send Discovery Request messages until it
reaches the max discovery interval and max discovery count but
receives no Discovery Responses, the client then enters the Sulking
state and remains in this state until the silent interval elapses.
CAPWAP Client
(HiveAP)
CAPWAP Server
(HiveManager)
Discovery
State
The CAPWAP client returns to the Discovery state and sends
Discovery Request messages.
The CAPWAP server receives the Discovery Request message
and responds with a Discovery Response.
Discovery
State
Sulking
State
The client sends a Join Request. Join
State
. . .
. . .
Run
State
Idle
State
When the client determines its neighbor is dead, it transitions
from the Run state to the Idle state.
The CAPWAP client and server perform a DTLS (Datagram Transport
Layer Security) handshake to establish a secure DTLS connection.
The server sends a Join Response.
If the Join Response indicates “success”, the client
clears its WaitJoin timer and enters the Run state.
Note: If the WaitJoin timer expires before the client
receives a successful Join Response, the client
terminates the DTLS connection and returns to the
Discover state.
If the Join Response indicates “failure”,
the CAPWAP server enters a Reset
state and terminates the DTLS session.