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.
While configuring on the dynamic interface of the controller, you must ensure the following:
The following restrictions apply for configuring the dynamic interfaces on the controller:
You must not configure a dynamic interface in the same subnetwork as a server that is reachable by the controller CPU, such as a RADIUS server, as it might cause asymmetric routing issues.
The controller does not respond to SNMP requests if the source address of the request comes from a subnet that is configured as a dynamic interface.
For SNMP requests that come from a subnet that is configured as a dynamic interface, the controller responds but the response does not reach the device that initiated the conversation.
If you are using DHCP proxy and/or a RADIUS source interface, ensure that the dynamic interface has a valid routable address. Duplicate or overlapping addresses across controller interfaces are not supported.
A dynamic interface is created as a WLAN interface by default. However, any dynamic interface can be configured as an AP-manager interface, with one AP-manager interface allowed per physical port. A dynamic interface with the Dynamic AP Management option enabled is used as the tunnel source for packets from the controller to the access point and as the destination for CAPWAP packets from the access point to the controller. The dynamic interfaces for AP management must have a unique IP address and are usually configured on the same subnet as the management interface.
Note | If link aggregation (LAG) is enabled, there can be only one AP-manager interface. |
We recommend having a separate dynamic AP-manager interface per controller port.
You must create the Layer 2 interface that you plan to use in the WLAN.
You can configure the dynamic interface using the following steps:
1.
show VLAN
2.
show int VLAN
3.
configure terminal
4.
wlan wlan-name wlan-ID wlan-SSID
5.
client vlan vlan-name
6.
show vlan
7.
end
8.
Show WLAN summary
Release |
Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |