The Cisco unified wireless network concept includes the following elements:
- Wireless clients: This component includes laptops, workstations, PDAs, IP phones, smartphones, tablets, and manufacturing devices that have embedded wireless technology.
- Access points: This component provides access to the wireless network and it should be placed strategically in the correct locations to get the best performance and minimal interference.
- Network management: Network management is accomplished through the network wireless control system. This is the central management tool that allows the design, control, and monitoring of wireless networks.
- Network unification: The wireless LAN system should be able to support wireless applications by offering unified security policies, QoS, IPS, and RF management. Cisco Wireless LAN Controllers (WLCs) offer this unified integration functionality to all of its major switching platforms and routing platforms.
- Network services: Wireless network services are also referred to as mobility services and include guest access, voice services, location services, and threat detection and mitigation.
One of the advantages of using the Cisco unified wireless solution is that as a centralized control architecture, it offers reduced TCO, improved visibility, dynamic RF management, enhanced WLAN security, enterprise mobility, and improved productivity and collaboration.
Standalone versus Lightweight Access Points
Standalone APs are also known as autonomous APs. They are easy to install but they can be difficult to manage in large deployments. They are not as desirable as the lightweight APs from Cisco because they must be managed individually. In addition, different parameters must be configured manually on each device; this includes the SSID, VLAN information, and security features.
The Cisco Unified Wireless Network (CUWN) introduced the concept of lightweight APs (LWAPs) and wireless LAN controllers (WLCs). These two types of wireless devices divide the responsibilities and the functionalities that an autonomous AP would perform on its own. This technology adds scalability by separating the WLAN data plane from the control plane into a split-MAC design, as illustrated in Figure 10.7 below.
LWAPs focus only on the actual RF transmissions and the necessary real-time control operations, such as beaconing, probing, or buffering. At the same time, WLCs manage all non real-time tasks, such as the following:
- SSID management
- VLAN management
- Access points association management
- Authentication
- Wireless QoS
Figure 10.7 – WLAN Split-MAC Operation
Modern LWAPs have plug-and-play capabilities and require WLCs for operation. They can be connected directly to the network without the need for additional configuration. The management logic and the way it functions are dictated by the WLC configuration. This makes the implementation process much easier than would be the case if autonomous APs were used.
LWAP to WLC Communication
When using LWAPs, all RF traffic they receive must first go to the WLC device that manages the specific AP. This changes the way in which traditional WLAN communications work, even for hosts associated to the same AP.
The RF communication between LWAPs and WLCs is handled (tunneled) using the Lightweight Access Point Protocol (LWAPP). The LWAP tunnel can operate either in Layer 2 or Layer 3 mode. In Layer 2 mode, the AP and the WLC share the same VLAN, subnet, and functions with the LWAP, receiving 802.11 frames and encapsulating them inside Ethernet toward the WLC. When the LWAP tunnel operates in Layer 3 mode, the LWAP receives 802.11 frames and encapsulates them inside UDP toward the WLC. This implies the WLC can be anywhere, as long as it is reachable by the AP.
The LWAP Protocol
The LWAP protocol (LWAPP) allows the moving of intelligence away from the AP and sharing it with WLCs. WLCs handle the wireless policies, the control messaging setup, authentication, and wireless operations. WLCs can also be considered the bridge between wireless networks and wired networks. WLC devices can manage multiple APs, providing configuration information as well as firmware updates on an ad-hoc basis.
LWAPP is an IETF draft standard for wireless LAN control messaging between APs and the WLCs. It can operate at both Layer 2 and Layer 3, but the Layer 3 LWAPP is far more popular.
Note: The APs and the WLCs exchange control messages over the wired backbone network.
The LWAPP Layer 2 functions include the following:
- 802.11 beacons and probe responses
- Packet control
- Packet acknowledgement and transmission
- Frame queuing and packet prioritization
- 802.11i MAC layer data encryption and decryption
The WLC Layer 2 functions include the following:
- 802.11 MAC management
- 802.11e resource reservation
- 802.11e authentication and key management
Layer 3 LWAP tunnels are used between APs and WLCs to transmit control messages, using UDP port 12223 for control and UDP port 12222 for data messages. Cisco LWAPP can operate in the following six modes:
- Local mode
- REAP (Remote Edge Access Point) mode
- Monitor
- Rogue detector (RD) mode
- Sniffer mode
- Bridge mode
Local mode is the default mode of operation of LWAPP. Every 180 seconds, the AP spends 60 ms on channels on which it does not operate. During the 60 ms time period, the AP performs noise and interference measurements and scans for intrusion detection events.
The REAP mode allows the LWAP to reside across a LAN link and still be able to communicate with the WLC and provide the functionality of a regular LWAP. REAP mode is not supported on all LWAP models.
Monitor mode is a special feature that allows LWAP-enabled APs to exclude themselves from dealing with data traffic between clients and the infrastructure. Instead, they act as dedicated sensors for location-based services, rogue AP detection, and intrusion detection systems. APs in monitor mode cannot serve clients because they continuously cycle through all available channels, listening for each channel for approximately 60 ms.
In RD mode, the LWAP monitors for rogue APs. The goal of rogue detection of APs is to see all the VLANs in the network because rogue APs can be connected to any of these VLANs. The switch sends all the rogue AP client MAC address lists to the RD AP, which forwards these to the WLC to compare them with the MAC addresses of legitimate clients. If MAC addresses match, the controller knows that the rogue AP dealing with those clients is on the wired network.
Sniffer mode allows the LWAP to capture and forward all the packets on a particular channel to a remote machine that is running packet capturing and analysis software. These packets include timestamps, packet size, and signal strength information.
The bridge mode typically operates on outdoor APs that function in a mesh topology. This cost-effective high-bandwidth wireless bridging connectivity mechanism includes point-to-point or point-to-multipoint bridging.
Wireless LAN Controllers
WLCs have the following three components:
- Wireless LAN
- Interfaces
- Ports
The wireless LAN is the SSID network name. Every wireless LAN is assigned to an interface in the WLC, and each wireless LAN is configured with policies for RF, QoS, and other wireless LAN attributes.
The WLC interfaces are logical connections that map to a VLAN on the wired network. Every interface is configured with a unique IP address, a default gateway, physical ports, VLAN tagging, and a DHCP server. WLCs support the following five interface types:
- The management interface, used for in-band management, connectivity to an AAA server, and Layer 2 discovery and association
- An optional service port interface for out-of-band management that is statically configured
- The AP manager interface, used for Layer 3 discovery and association (the static WLC IP address will be configured on this interface)
- Dynamic interfaces (these are the VLANs designated for wireless LAN clients data)
- Virtual interfaces, used for Layer 3 security authentication, DHCP relay support, and management of mobility features
The port is a physical connection to the neighboring switch or router; by default, each port is a .1Q trunk port. WLCs might have multiple ports that go into a single port-channel interface (link aggregation can be applied to these ports). Some WLCs also have a service port that is used for out-of-band management.
Note: Different WLC platforms can support up to several hundred APs.
Roaming and Mobility
One of the main features of a WLAN solution is the users’ ability to access network resources from different areas, including zones where it is difficult to install cables. Another reason for using WLANs would be organizational policies that allow guest access only wirelessly. Sometimes a wireless LAN solution is built as a transition network until the complete wired network is implemented.
Considering the scenarios mentioned above, end-users will most likely move from one location to another. The solution to this issue is offered by the roaming and mobility features that enable users to access the network from different locations.
Roaming occurs when wireless clients change their association from one LWAP to another without losing connectivity. Designers should scale the wireless network carefully to allow for the client roaming process. Wireless roaming can be divided into the following two categories (illustrated in Figure 10.8 below):
- Intra-controller roaming
- Inter-controller roaming (Layer 2 or Layer 3)
Figure 10.8 – WLAN Mobility
Intra-controller roaming occurs when a client moves its association from one AP to another access point controlled by the same WLC. At that moment, the WLC will update the client database with the new association and it will not change the client’s IP address.
Inter-controller roaming can operate in either Layer 2 or Layer 3. In Layer 2 inter-controller roaming, users move from AP to AP and from WLC to WLC, but they remain in the same subnet. Layer 3 inter-controller roaming is more difficult to implement and because users can move from AP to AP, from WLC to WLC, and from subnet to subnet. In this scenario, the WLCs must be configured with mobility groups to communicate and exchange information about the roaming user’s status.
A very important advantage of Layer 3 inter-controller roaming is that users can maintain their original IP address. The two wireless LAN controllers are connected through an IP connection. In this situation, the traffic is bridged to a different IP subnet. When the client associates to the new AP, the new WLC exchanges mobility information with the old WLC. The original client database is not moved to the new WLC. Instead, the old WLC will mark the client in its database entry (anchor entry) and this entry is copied to the new WLC database that will mark this entry as a foreign entry. The wireless client keeps its original IP address and it is re-authenticated as soon as a new security session is established.
Wireless LAN Controllers are assigned to mobility groups in order to exchange Mobility messages and tunnel data over the IP connection dynamically. Mobility groups use the following ports to exchange data:
- LWAPP control: UDP 12223
- LWAPP data: UDP 12222
- WLC exchange un-encrypt messages: UDP 16666
- WLC exchange encrypt messages: UDP 16667

