Cisco Cisco Wireless LAN Controller Module Information Guide

Page of 21
  
Contents
Introduction
Design FAQ
Features FAQ
Related Information
Introduction
This document provides information on the most frequently asked questions (FAQ) about the
design and the features available with a Wireless LAN Controller (WLC).
Refer to 
Cisco Technical Tips Conventions
 for more information on document conventions.
Design FAQ
Q. How do I configure the switch to connect with the WLC?
A. Configure the switch port, to which the WLC is connected, as an IEEE 802.1Q trunk port. Make
sure that only the necessary VLANs are allowed on the switch. Usually, the management and the
AP-Manager interface of the WLC are left untagged. This means that they assume the native
VLAN of the connected switch. This is not necessary. You can assign a separate VLAN to these
interfaces. For more information, refer to the 
Configure the Switch for the WLC 
section of 
Wireless
LAN Controller and Lightweight Access Point Basic Configuration Example
.
Q. Does all network traffic from and to a WLAN client tunnel through a
Wireless LAN Controller (WLC) once the access point (AP) gets registered
with the controller?
A. When the AP joins a WLC, a Control and Provisioning of Wireless Access Points protocol
(CAPWAP) tunnel is formed between the two devices. All traffic, which includes all client traffic, is
sent through the CAPWAP tunnel.
The only exception to this is when an AP is in hybrid-REAP mode. The hybrid-REAP access points
can switch client data traffic locally and perform client authentication locally when their connection
to the controller is lost. When they are connected to the controller, they can also send traffic back
to the controller.
Q. Can I install Lightweight Access Points (LAPs) at a remote office and install
a Cisco Wireless LAN Controller (WLC) at my headquarters? Does the
LWAPP/CAPWAP work over a WAN?
A. Yes, you can have the WLCs across the WAN from the APs. LWAPP/CAPWAP works over a