Lightweight Access points are part Cisco Unified Wireless Network architecture. The architecture centralized wireless LAN configuration and control on the controller.
In this Cisco Unified Wireless Network architecture, access points are "lightweight," meaning that they cannot act independently of a controller. The wireless LAN controller manages the access point configurations and firmware.
The access points are zero-touch and no individual configuration of access points is required.
Lightweight access points must be discovered by a controller before they can become an active part of the network. Cisco's lightweight access points use the Lightweight Access Point Protocol (LWAPP) to communicate between the controller and other lightweight access points on the network.
In an LWAPP environment, a lightweight access point discovers a controller by using LWAPP discovery mechanisms and then sends it an LWAPP join request. The controller sends the access point an LWAPP join response allowing the access point to join the controller. When the access point joins the controller, the controller manages its configuration, firmware, control transactions, and data transactions.
Layer 3 LWAPP WLC Discovery Algorithm
Over-the-Air Provisioning (OTAP)
DHCP option 43
Using the DNS server in order to return WLC IP addresses to the LAP
Use IP helper address on the Router
Although this is not a part of the Layer 3 discovery algorithm, this is a simpler method that can be used when WLC and LAPs are in different subnets. After the LAP gets an IP address from the DHCP server, the LAP broadcasts a Layer 3 LWAPP discovery message on to its local subnet. The IP address of the WLC is configured as the ip-helper address on the router. The router forwards these broadcasts to the IP addresses configured with the ip-helper command on the interface on which the broadcast is heard. When you use the ip helper-address command, DIRECTED BROADCASTS, as well as unicasts, eight different UDP ports are forwarded automatically. Those ports are Trivial File Transfer (TFTP) (Port 69), Domain Name System (Port 53), Time Service (Port 37), NetBIOS Name Server (Port 137), NetBIOS Datagram Server (Port 138), Boot Protocol (BOOTP) Client and Server (Port 67 and Port 68), TACACS service (Port 49). Since LWAPP broadcast uses UDP port 12223 it must be explicitly forwarded on the router. Here is an example scenario. Assume that you have a WLC in one subnet, such as 172.16.0.0/16, and the LAPs and the DHCP server in a different subnet, such as 192.168.1.0/24. Routing is enabled between the two subnets. This example shows the configuration on the router:
Router(config)#interface Fastethernet 0/1
Router(config-if)#ip helper-address 172.16.0.1!--- IP address of the WLC Router(config-if)#exitRouter(config)ip forward-protocol udp 12223
Hello, Anyone can explain the picture of AP signal. The picture shows signals strength in different angles so that we can know how strong the signal is at different angle. Do you think the picture show signal strength at some distance away from the AP? Fo...
We currently have a Cisco WLC 4402 with approximately 50 Aironet 1142 APs . When we we provision an AP both our guest and secure wlans are automatically setup on the APs. Is there a way or configuration where we could have certain APs "not" have the secur...
Hello, I'm using network environment based on AIR-AP3802I-E-K9 with WLC 5529 184.108.40.206. Could someone please tell me why some client devices which are using 2.4Ghz associating with AP only based on 802.11g?I've in NIC requirements tha...
i have tried to search everywhere without been able to get a real answer, does the vWLC (Cisco Virtual Wireless Controller) support the 802.11ac Radio Module installed on the 3600 and 3700 Cisco AP´s ?i can see the M module mentioned on the compatibi...
Hi,We have Catalyst 9800-40 WLC , and we are facing the issue "Two Access Points with same name are not able to join controller "I tried to add new access points . Initially APs joined controller and their MAC ID was shown in Access point list. ...