Lightweight Access Point Protocol (LWAPP) is a protocol that can control multiple Wi-Fi wireless access points at once. This can reduce the amount of time spent on configuring, monitoring and troubleshooting a large network. The system will also allow network administrators to closely analyze the network.
This system is installed in a central server that gathers data from RF devices from different brands and settings. The server can command a selected group of devices to apply given settings simultaneously.
YouTube Encyclopedic
-
1/3Views:12 44736 258936
-
How does a Lightweight AP discover a controller, part I
-
How to convert a Cisco AP from Lightweight to Autonomous (CAP to SAP)
-
CCNA 28_Cisco Access Point Rommon Recovery AP: + Lightweight to Autonomous AP + DHCP Server Internet
Transcription
Standardization
LWAPP was proposed by Airespace, as a standard protocol to provide interoperability between any brands of access point. Airespace was purchased by Cisco Systems. Its purpose was to standardize "lightweight" access points with the Internet Engineering Task Force (IETF), but it was approved as a standard. Sponsored by Cisco Systems, it has been submitted to IETF in RFC 5412.[1]
Although this protocol has so far not been popular beyond the Airespace/Cisco product lines, the CAPWAP standard is based on LWAPP. Support for LWAPP is also found in analysis products from AirMagnet, who has implemented a software based on this protocol to analyze Cisco wireless products.[2]
Still considered proprietary, LWAPP systems compete with other non-standard lightweight wireless mechanisms from companies like Meru Networks and Aruba Networks.
LWAPP Layer 2
On Layer 2, LWAPP only requires a data link connection in order to transfer frames and Layer 2 broadcasts. Even if IP connectivity is not established it will still operate at layer 2.
LWAPP Layer 3 and 4
Layer 4 UDP 12222 (data channel) and 12223 (control channel) connectivity must be established to work with this form of the protocol. Broadcasts or DHCP option 43 can be used to prime the access-points of the network. The controller must be on the same subnet if DHCP is not configured to handle layer 3 LWAPP provisioning. Another option for directing an AP to the controller is by defining the controller on the DNS server of the network.
See also
- CAPWAP - Control and provisioning of wireless access points (CAPWAP) protocol specification
References
- ^ RFC 5412, Lightweight Access Point Protocol, P. Calhoun, R. Suri, N. Cam-Winget, M. Williams, S. Hares, B. O'Hara, S. Kelly (February 2010)
- ^ Griffith, Eric (2007-02-20). "AirMagnet Analyzes Cisco". Wi-Fi Planet. Archived from the original on 2008-11-22.
{{cite web}}: CS1 maint: unfit URL (link)
External links
- Cisco Wireless LAN Controller Configuration Guide, Release 4.0
- Steven J. Vaughan-Nichols (August 22, 2003). "LWAPP: Standardizing Centralized Wi-Fi Management". Wi-Fi Planet. Archived from the original on 2008-12-03.
{{cite web}}: CS1 maint: unfit URL (link) - Lightweight Access Point Protocol IETF Standard
- Control And Provisioning of Wireless Access Points (CAPWAP)Protocol Specification
This page was last edited on 20 March 2024, at 04:00