Cisco Cisco Aironet 1310 Access Point Bridge 情報ガイド
Q. What is Lightweight AP Protocol (LWAPP)?
A. LWAPP is an Internet Engineering Task Force (IETF) draft protocol that defines the
control messaging for setup and path authentication and run−time operations. LWAPP also
defines the tunneling mechanism for data traffic.
control messaging for setup and path authentication and run−time operations. LWAPP also
defines the tunneling mechanism for data traffic.
A LAP discovers a controller with the use of LWAPP discovery mechanisms. The LAP sends
an LWAPP join request to the controller. The controller sends the LAP an LWAPP join
response, which allows the AP to join the controller. When the LAP joins to the controller,
the LAP downloads the controller software if the revisions on the LAP and controller do not
match. Subsequently, the LAP is completely under the control of the controller. LWAPP
secures the control communication between the LAP and the controller by means of a secure
key distribution. The secure key distribution requires already provisioned X.509 digital
certificates on both the LAP and the controller. Factory−installed certificates are referenced
with the term "MIC", which is an acronym for Manufacturing Installed Certificate. Cisco
Aironet APs that shipped before July 18, 2005, do not have a MIC. So these APs create a
self−signed certificate (SSC) when they are upgraded in order to operate in lightweight mode.
Controllers are programmed to accept SSCs for the authentication of specific APs.
an LWAPP join request to the controller. The controller sends the LAP an LWAPP join
response, which allows the AP to join the controller. When the LAP joins to the controller,
the LAP downloads the controller software if the revisions on the LAP and controller do not
match. Subsequently, the LAP is completely under the control of the controller. LWAPP
secures the control communication between the LAP and the controller by means of a secure
key distribution. The secure key distribution requires already provisioned X.509 digital
certificates on both the LAP and the controller. Factory−installed certificates are referenced
with the term "MIC", which is an acronym for Manufacturing Installed Certificate. Cisco
Aironet APs that shipped before July 18, 2005, do not have a MIC. So these APs create a
self−signed certificate (SSC) when they are upgraded in order to operate in lightweight mode.
Controllers are programmed to accept SSCs for the authentication of specific APs.
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
♦
LWAPP−enabled access points can discover and join a CAPWAP controller, and conversion
to a CAPWAP controller is seamless. For example, the controller discovery process and the
firmware downloading process when you use CAPWAP are the same as when you use
LWAPP. The one exception is for Layer 2 deployments, which are not supported by
CAPWAP.
to a CAPWAP controller is seamless. For example, the controller discovery process and the
firmware downloading process when you use CAPWAP are the same as when you use
LWAPP. The one exception is for Layer 2 deployments, which are not supported by
CAPWAP.
You can deploy CAPWAP controllers and LWAPP controllers on the same network. The
CAPWAP−enabled software allows access points to join either a controller that runs
CAPWAP or LWAPP. The only exception is the Cisco Aironet 1140 Series Access Point,
which supports only CAPWAP and therefore joins only controllers that run CAPWAP. For
example, an 1130 series access point can join a controller that runs either CAPWAP or
LWAPP whereas an 1140 series access point can join only a controller that runs CAPWAP.
CAPWAP−enabled software allows access points to join either a controller that runs
CAPWAP or LWAPP. The only exception is the Cisco Aironet 1140 Series Access Point,
which supports only CAPWAP and therefore joins only controllers that run CAPWAP. For
example, an 1130 series access point can join a controller that runs either CAPWAP or
LWAPP whereas an 1140 series access point can join only a controller that runs CAPWAP.
For more information, refer to the Access Point Communication Protocols section of the
configuration guide.
configuration guide.