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.
configured with IPv6 has only one AP-manager and is applicable on management
interface. You cannot remove the AP-manager configured on management interface.
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.
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.
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.
Configuring AP Manager Interface
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.
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
When LAG is enabled—Supports only one AP Manager, which can
either be on the management or dynamic interface with AP management.
When LAG is disabled—Supports one AP Manager per port. The
Dynamic Interface tied to a VLAN can act as an AP Manager (when enabled).
When you enable LAG, all the ports would lose their AP
Manager status and the AP management reverts back onto the Management
Port redundancy for the
AP-manager interface is not supported. You cannot map the AP-manager interface
to a backup port.
Configuring the AP-Manager Interface (GUI)
Interfaces to open the Interfaces page.
Interface > Edit page appears.
only—A controller configured with IPv6 address does not support Dynamic
AP-Manager. By default, the management interface acts like an AP-manager
AP-Manager Interface parameters:
5500 Series Controllers, you are not required to configure an AP-manager
interface. The management interface acts like an AP-manager interface by
Physical port assignment
Enter 0 for an untagged VLAN
or a nonzero value for a tagged VLAN. We recommend using tagged VLANs for the
gig/wired subinterface is numbered with VLAN number and dot11 subinterface is
numbered with the WLAN ID. The first configured WLAN becomes dot11 0.1 &
dot11 1.1 and second WLAN ID subinterface becomes dot11 0.2 & dot11 1.2
onwards. This dot11 sub interface number cannot be mapped with a VLAN ID
because multiple WLAN can be assigned with a same VLAN number. We cannot have
duplicate subinterface created in the system. The native subinterface
configuration in wired interface is the AP native VLAN configuration, if VLAN
support is enabled in FlexConnect mode or else the native interface is always
gig prime interface in AP(Local / Flex with no VLAN support).
Fixed IP address, IP netmask,
and default gateway
Primary and secondary DHCP
Access control list (ACL)
name, if required
Save Configuration to
save your changes.
If you made any
changes to the management or virtual interface, reboot the controller so that
your changes take effect.
Configuring the AP Manager Interface (CLI)
Before You Begin
For Cisco 5500 Series
Controllers, you are not required to configure an AP-manager interface. The
management interface acts like an AP-manager interface by default.
A controller configured with IPv6 address does not support Dynamic
AP-Manager. The management interface acts like an AP-manager interface by
show interface summary command to view the current
If the system is operating in
Layer 2 mode, the AP-manager interface is not listed.
show interface detailed ap-manager command to view
the current AP-manager interface settings.
config wlan disablewlan-number
command to disable each WLAN that uses the AP-manager interface for
distribution system communication.
Enter these commands to
define the AP-manager interface:
save config command to save your changes.
show interface detailed ap-manager command to
verify that your changes have been saved.
Configuration Example: Configuring AP-Manager on a Cisco 5500
Cisco 5500 Series Controller, we recommend that you have eight dynamic
AP-manager interfaces and associate them to the eight Gigabit ports of the
controller when LAG is not used. If you are using the management interface,
which acts like an AP-manager interface by default, you must create only seven
more dynamic AP-manager interfaces and associate them to the remaining seven
For IPv6 only—A controller configured with IPv6 address does not
support Dynamic AP-Manager. By default, the management interface acts like an
AP-manager interface. Use LAG for IPv6 AP load balancing.
Figure 1. Dynamic Interface Example
with Dynamic AP Management. This figure shows
a dynamic interface that is enabled as a dynamic AP-manager interface and
associated to port number 2.
Figure 2. Cisco 5500 Series Controller
Interface Configuration Example. This figure shows
a Cisco 5500 Series Controller with LAG disabled, the management interface used
as one dynamic AP-manager interface, and seven additional dynamic AP-manager
interfaces, each mapped to a different Gigabit port.