Информационное Руководство для Cisco Cisco 2000 Series Wireless LAN Controller
Wireless LAN Controller (WLC) FAQ
Document ID: 69561
Contents
Introduction
General FAQ
Troubleshoot FAQ
Related Information
General FAQ
Troubleshoot FAQ
Related Information
Introduction
This document provides information on the most frequently asked questions (FAQ) about the Cisco Wireless
LAN Controller (WLC).
LAN Controller (WLC).
Refer to Cisco Technical Tips Conventions for more information on document conventions.
General FAQ
Q. What is a wireless LAN controller (WLC)?
A. Wireless networks have become a necessity today. Many corporate environments require
deployment of wireless networks on a large scale. Cisco has come up with the concept of the
Cisco Unified Wireless Network (CUWN) solution, which helps make it easier to manage
such large scale deployments. WLC is a device that assumes a central role in the CUWN.
Traditional roles of access points, such as association or authentication of wireless clients, are
done by the WLC. Access points, called Lightweight Access Points (LAPs) in the unified
environment, register themselves with a WLC and tunnel all the management and data
packets to the WLCs, which then switch the packets between wireless clients and the wired
portion of the network. All the configurations are done on the WLC. LAPs download the
entire configuration from WLCs and act as a wireless interface to the clients. For more
information on how a LAP registers with a WLC, refer to the document Lightweight AP
(LAP) Registration to a Wireless LAN Controller.
deployment of wireless networks on a large scale. Cisco has come up with the concept of the
Cisco Unified Wireless Network (CUWN) solution, which helps make it easier to manage
such large scale deployments. WLC is a device that assumes a central role in the CUWN.
Traditional roles of access points, such as association or authentication of wireless clients, are
done by the WLC. Access points, called Lightweight Access Points (LAPs) in the unified
environment, register themselves with a WLC and tunnel all the management and data
packets to the WLCs, which then switch the packets between wireless clients and the wired
portion of the network. All the configurations are done on the WLC. LAPs download the
entire configuration from WLCs and act as a wireless interface to the clients. For more
information on how a LAP registers with a WLC, refer to the document Lightweight AP
(LAP) Registration to a Wireless LAN Controller.
Q. What is CAPWAP?
A. In controller software release 5.2 or later, Cisco lightweight access points use the IETF
standard Control and Provisioning of Wireless Access Points protocol (CAPWAP) in order to
communicate between the controller and other lightweight access points on the network.
Controller software releases prior to 5.2 use the Lightweight Access Point Protocol (LWAPP)
for these communications.
standard Control and Provisioning of Wireless Access Points protocol (CAPWAP) in order to
communicate between the controller and other lightweight access points on the network.
Controller software releases prior to 5.2 use the Lightweight Access Point Protocol (LWAPP)
for these communications.
CAPWAP, which is based on LWAPP, is a standard, interoperable protocol that enables a
controller to manage a collection of wireless access points. CAPWAP is being implemented
in controller software release 5.2 for these reasons:
controller to manage a collection of wireless access points. CAPWAP is being implemented
in controller software release 5.2 for these reasons:
To provide an upgrade path from Cisco products that use LWAPP to next−generation
Cisco products that use CAPWAP
Cisco products that use CAPWAP
♦
To manage RFID readers and similar devices
♦
To enable controllers to interoperate with third−party access points in the future
♦