The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This module lists the following sections:
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Before configuring the AP manager interfaces in the controller you must ensure that you have separate dynamic AP manager interface per port.
For IPv4—The MAC address of the management interface and the AP-manager interface is the same as the base LAG MAC address.
If only one distribution system port can be used, you should use distribution system port 1.
You can configure multiple LAGs in the controller.
An AP-manager interface is not required to be configured. The management interface acts like an AP-manager interface by default, and the access points can join on this interface.
If link aggregation (LAG) is enabled, there can be only one AP-manager interface. But when LAG is disabled, one or more AP-manager interfaces can be created, generally one per physical port.
Port redundancy for the AP-manager interface is not supported. You cannot map the AP-manager interface to a backup port.
Note | A 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. |
Note | The controller 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.
A controller 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.
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.
1.
conf t
2.
wireless ap-manager interface vlan vlan-ID
3.
end
Command or Action | Purpose |
---|
You can view the access point join interfaces configured in the controller using the following steps:
1. show ap summary
2. show ap name
3. show ap name apname config general
4. show wireless interface summary
Release |
Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |