A controller configured with
IPv4 has one or more AP-manager interfaces, which are used for all Layer 3
communications between the controller and lightweight access points after the
access points have joined the controller.
Release 8.2 does not support multiple non-AP Manager dynamic
interfaces, untagged management interfaces, management interfaces mapped to
physical ports, and non-LAG scenarios.
The AP-manager IP address is used as the tunnel source for CAPWAP
packets from the controller to the access point and as the destination for
CAPWAP packets from the access point to the controller.
configured with IPv6 has only one AP-manager and is applicable on management
interface. You cannot remove the AP-manager configured on management interface.
does not support transmitting the jumbo frames. To avoid having the controller
transmit CAPWAP packets to the AP that will necessitate fragmentation and
reassembly, reduce MTU/MSS on the client side.
The AP-manager interface
communicates through any distribution system port by listening across the Layer
3 network for access point CAPWAP or LWAPP join messages to associate and
communicate with as many lightweight access points as possible.
The controller sends the
access point a CAPWAP join response allowing the access point to join the
controller. When the access point joins the controller, the controller manages
its configuration, firmware, control and data transactions.
When an access point performs
a reboot or is disconnected from the controller, the join statistics for an
access point is maintained from the controller. But this statistics are lost
when the controller performs a reboot or disconnects.
configured with IPv6 does not support Dynamic AP-Manager. By default, the
management interface acts like an AP-manager interface. Link Aggregation (LAG)
is used for IPv6 AP load balancing.