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 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 to which they are connected. 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 acquire VLANs associated from the interface group configured on the WLAN.
You can also configure AAA override for interface groups. This feature extends the current AP group and AAA override architecture where AP groups and AAA override can be configured to override the interface group WLAN to which the interface is mapped. This is accomplished with multiple interfaces using interface groups.
This feature enables network administrators to configure guest anchor restrictions where a wireless guest user at a foreign location can obtain an IP address from multiple subnets on the foreign location and controllers from within the same anchor controller.
Configuration of Interface Group
Use this command in order to create VLAN group on WLC:
vlan group word vlan-list 100-200
show vlan group
Use this command in order to map VLAN group to WLAN:
wlan corporate 1 corporate client vlan word
show wlan summary
Information about AP Groups
After you create up to 512 WLANs on the controller, you can selectively publish them (using AP groups) to different APs to improve the management of your wireless network. In a typical deployment, all users on a WLAN are mapped to a single interface on the controller. Therefore, all users associated with that WLAN are on the same subnet or VLAN. However, you can choose to distribute the load among several interfaces or to a group of users based on specific criteria such as individual departments (for example, Marketing) through the creation of AP groups. Additionally, these AP groups can be configured in separate VLANs to simplify network administration.
Figure 11-1 Access Point Groups
In Figure 11-1, three configured dynamic interfaces are mapped to three different VLANs (VLAN 61, VLAN 62, and VLAN 63). Three AP groups are defined, and each is a member of a different VLAN, but all are members of the same SSID. A client within the wireless SSID is assigned an IP address from the VLAN subnet of which its AP is a member. For example, any user that associates with an AP that is a member of AP group VLAN 61 is assigned an IP address from that subnet.
In the example shown in Figure 11-1, the controller internally treats roaming between APs as a Layer 3 roaming event. In this way, WLAN clients maintain their original IP addresses.
After all APs join the controller, you can create AP groups and assign up to 16 WLANs to each group. Each AP advertises only the enabled WLANs that belong to its AP group. The AP does not advertise disabled WLANs in its AP group or WLANs that belong to another group.
Note The default access point group can have up to 16 WLANs associated with it. The WLAN IDs for the default access point group must be less than or equal to 16. If a WLAN with an ID greater than 16 is created in the default access point group, the WLAN SSID will not be broadcasted. All WLAN IDs in the default access point group must have an ID that is less than or equal to 16. WLANs with IDs greater than 16 can be assigned to custom AP groups.
Use this command in order to create an AP Group Name:
ap group <WORD> wlan <apgroup> vlan < VLAN#>
This command maps an AP to an AP Group:
ap name <name> ap-groupname <apgroup>
AP will reload after the above command is executed.