cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1128
Views
5
Helpful
4
Replies
Beginner

Guest Anchor WLC w/ multiple guest VLANs

I have a situation where I have a single anchor WLC and two foreign WLC's.  Both foreign WLCs tunnel guest traffic to the anchor WLC.  Ideally, I would like to keep guest WLAN configuration the same among both foreign WLCs.  Is it possible to anchor guest traffic from each foreign WLC to a unique VLAN with both having the same WLAN configuration?  Example:  Foreign WLC A tunnels to VLAN A and foreign WLC B tunnels to VLAN B on the same anchor WLC.

 

Thanks in advance for the responses.

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Rising star

Yes, this is possible. You

Yes, this is possible. You have to create the new interface on the anchor WLC and change one of the two foreign maps on the currently existing SSID to that new interface.

View solution in original post

4 REPLIES 4
Highlighted
Rising star

Yes, this is possible. You

Yes, this is possible. You have to create the new interface on the anchor WLC and change one of the two foreign maps on the currently existing SSID to that new interface.

View solution in original post

Highlighted
Beginner

How would you map the new

How would you map the new interface on the foreign WLC?  Normally wouldn't you use the management VLAN?

Highlighted
Rising star

There is no need to make a

There is no need to make a change on the foreign WLC. It is the anchor controller who decides where you client is going to be.

Highlighted
Rising star

Whenever a wireless client

Whenever a wireless client connects to a wireless network (WLAN), the client is placed in a VLAN that is associated with the WLAN. In a large venue such as an auditorium, a stadium, or a conference where there may be numerous wireless clients, having only a single WLAN to accommodate many clients might be a challenge.

The VLAN select feature enables you to use a single WLAN that can support multiple VLANs. Clients can get assigned to one of the configured VLANs. This feature enables you to map a WLAN to a single or multiple interface VLANs using interface groups. Wireless clients that associate to the WLAN get an IP address from a pool of subnets identified by the interfaces. The IP address is derived by an algorithm based on the MAC address of the wireless client. This feature also extends the current AP group architecture where AP groups can override an interface or interface group to which the WLAN is mapped to, with multiple interfaces using the interface groups. This feature also provides the solution to auto anchor restrictions where a wireless guest user on a foreign location can get an IP address from multiple subnets based on their foreign locations or foreign controllers from the same anchor controller.

When a client roams from one controller to another, the foreign controller sends the VLAN information as part of the mobility announce message. Based on the VLAN information received, the anchor decides whether the tunnel should be created between the anchor controller and the foreign controller. If the same VLAN is available on the foreign controller, the client context is completely deleted from the anchor and the foreign controller becomes the new anchor controller for the client.

If an interface (int-1) in a subnet is untagged in one controller (Vlan ID 0) and the interface (int-2) in the same subnet is tagged to another controller (Vlan ID 1), then with the VLAN select, client joining the first controller over this interface may not undergo an L2 roam while it moves to the second controller. Hence, for L2 roaming to happen between two controllers with VLAN select, all the interfaces in the same subnet should be either tagged or untagged.

As part of the VLAN select feature, the mobility announce message carries an additional vendor payload that contains the list of VLAN interfaces in an interface group mapped to a foreign controller’s WLAN. This VLAN list enables the anchor to differentiate from a local to local or local to foreign handoff.

For more information please refer to the link-

http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-4/configuration/guides/consolidated/b_cg74_CONSOLIDATED/b_cg74_CONSOLIDATED_chapter_0100101.html

CreatePlease to create content
Content for Community-Ad

August's Community Spotlight Awards