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.
Interface groups are logical groups of interfaces. Interface groups facilitate user configuration where the same interface group can be configured on multiple WLANs or while overriding a WLAN interface per AP group. An interface group can exclusively contain either quarantine or nonquarantine interfaces. An interface can be part of multiple interface groups.
A WLAN can be associated with an interface or interface group. The interface group name and the interface name cannot be the same.
This feature also enables you to associate a client to specific subnets based on the foreign controller that they are connected to. The anchor controller WLAN can be configured to maintain a mapping between foreign controller MAC and a specific interface or interface group (Foreign maps) as needed. If this mapping is not configured, clients on that foreign controller gets VLANs associated in a round robin fashion from interface group configured on WLAN.
You must create the interface groups using the following commands after you configure the terminal.
1. vlan group groupname vlan-list 1-256
2. wlan wlanname 1 wlanname
3. client vlan vlangrp1
1. conf t
2. wlan wlanname 1 wlanname
3. client vlan vlangrp1
4. end
You must configure the VLAN after configuring the controller port as a trunk port. We recommend that you configure the trunk port first and then associate the VLANs to the trunk port.
1. show wireless interface summary
2. show run int te1/0/1
3. interface TenGigabitEthernet1/0/1
4. switchport trunk allowed vlan 1-10
5. switchport mode trunk
6. nmsp attachment suppress
7. end
You can configure VLANs in the controller using the web UI. To do this, you must follow the steps defined in this module in the web UI.
1. Choose
2. Click the VLAN ID field in the table to view the details of the selected VLAN.
3. Enter the values.
4. Click Apply.
5. To create a new VLAN, click New.
6. To delete a VLAN, check the check box in the VLAN summary page, and click Remove.
Release |
Modification |
---|---|
Cisco IOS XE 3.2SECisco IOS XE 3.2SE |
This command was introduced. |