Cisco Unified Wireless

Network Architecture
Mg. Leonel Hernandez
Cisco UWN Architecture
1. WLAN Technologies
2. Cisco UWN Architecture Concepts
3. LWAP and CAPWAP
4. Roaming
5. Radio Management and RF Groups
6. WLAN Design
7. Lab: RAP and MAP topology
WLAN Technologies
• WLAN applications include inside-building access, LAN extension, outside
building-tobuilding communications, public access, and small office/home
office (SOHO) communications.
• The first standard for WLANs was IEEE 802.11, approved by the IEEE in
1997.
• The current specification is IEEE 802.11-1999, with many amendments
thereafter.
Cisco UWN

• With the explosion of wireless solutions in and out

of the enterprise, designers must create solutions
that provide mobility and business services while
maintaining network security.
• The Cisco UWN architecture combines elements of
wireless and wired networks to deliver scalable,
manageable, and secure WLANs. Cisco UWN
architecture is composed of five network elements:
Cisco UWN Components
Benefits of Cisco UWN
• Reduced total cost of ownership (TCO)
• Enhanced visibility and control
• Dynamic RF management
• WLAN security
• Unified wired and wireless network
• Enterprise mobility
• Enhanced productivity and collaboration
Cisco UWN Architecture
LWAPP
• Lightweight Access Point Protocol (LWAPP) is a draft Internet
Engineering Task Force (IETF) standard for control messaging for
setup, authentication, and operations between APs and WLAN
controllers (WLC).
• In the LWAPP RFC draft, LWAPP control messages can be
transported at Layer 2 tunnels or Layer 3 tunnels. Layer 2 LWAPP
tunnels were the first method developed in which the APs did not
require an IP address. The disadvantage of Layer 2 LWAPP was that
the WLC needed to be on every subnet on which the AP resides.
Layer 2 LWAPP is a deprecated solution for Cisco. Layer 3 LWAPP is
the preferred solution. In the configuration, Layer 2 or Layer 3
transport modes can be selected. When set Layer 3, the LWAPP
uses IP addresses to communicate with the access points; these IP
addresses are collected from a mandatory DHCP server. When set
to Layer 2, the LWAPP uses proprietary code to communicate with
the access points
LWAPP
• Layer 3 LWAPP tunnels are used between the LWAP
and the WLC. Messages from the WLC use User
Datagram Port (UDP) port 12223 for control and UDP
port 12222 for data messages. In this solution, APs
require an IP address, but the WLC does not need to
reside on the same segment
 CAPWAP
• Control and Provisioning for Wireless Access Point
(CAPWAP) is an IETF standard for control
messaging for setup, authentication, and operations
between APs and WLCs. In Controller Software 5.2,
Cisco LWAPs use CAPWAP communication
between the WLC and LWAPs. CAPWAP is similar
to LWAPP except for the following differences:
■ CAPWAP uses Datagram Transport Layer Security
(DTLS) for authentication and encryption to protect
traffic between APs and controllers. LWAPP uses AES.
■ CAPWAP has a dynamic maximum transmission unit
(MTU) discovery mechanism.
■ CAPWAP control messages run over UDP 5246.
■ CAPWAP data messages use UDP 5247.
• CAPWAP uses a Layer 3 tunnel between the LWAP
and the WLC. Figure shows the architecture. The
APs obtain an IP address via DHCP. On the AP side,
the control and data messages use an ephemeral
UDP port that is derived from a hash between the
AP MAC addresses. CAPWAP uses UDP port 5247
for data messages and UDP port 5246 for control
messages
AP Modes

• Local mode: This is the default mode of operation. In this mode, every
180 seconds the AP measures noise floor and interference, and scans
for IDS events. This scanning activity occurs on unused channels and
lasts for 60 milliseconds.
• Hybrid Remote Edge AP (H-REAP) mode: This mode enables an
LWAP to reside across a WAN link and still be able to communicate
with the WLC and provide the supported on Cisco 1130, 1140, 1240AB,
and 1250AG series LWAPs.
• Monitor mode: Monitor mode is a feature designed to allow specified
CAPWAP-enabled APs to exclude themselves from handling data
traffic between clients and the infrastructure. They instead act as
dedicated sensors for location-based services (LBS), rogue AP
detection, and intrusion detection (IDS). When APs are in Monitor
mode, they cannot serve clients and continuously cycle through all
configured channels, listening to each channel for approximately 60
ms.
 AP Modes (Cont)
■ Rogue detector mode: LWAPs that operate in Rogue Detector mode to monitor for
rogue APs. They do not transmit or contain rogue APs. The idea is that the rogue
detector (RD) should be able to see all the VLANs in the network, because rogue
APs can be connected to any of the VLANs in the network. (Therefore, we connect it
to a trunk port.) The LAN switch sends all the rogue AP/client MAC address lists to
the RD. The RD then forwards those to the WLC to compare with the MAC
addresses of clients that the WLC APs have heard over the air. If the MAC addresses
match, the WLC knows that the rogue AP to which those clients are connected is on
the wired network.
■ Sniffer mode: A CAPWAP that operates in Sniffer mode functions as a sniffer and
strength, packet size, and so on. The Sniffer feature can be enabled only if you run
AiroPeek, a third-party network analyzer software that supports decoding of data
packets.
■ Bridge mode: The Bridge mode feature on the Cisco 1130 and 1240 series
(typically indoor usage) and 1500 APs (typically outdoor mesh usage) provides cost-
effective, high-bandwidth wireless bridging connectivity. Applications supported are
point-to point bridging, point-to-multipoint bridging, point-to-point wireless access with
integrated wireless backhaul, and point-to-multipoint wireless access with integrated
wireless backhaul
AP Modes (Cont)

Figure 1 Figure 2
LWAPP Discovery of WLC
WLAN Authentication
Wireless clients first associate to an AP. Then wireless
clients need to authenticate with an authentication server
before the AP allows access to services. As shown in Figure,
the authentication server resides in the wired infrastructure. An
EAP/RADIUS tunnel occurs between the WLC and the
authentication server. Cisco’s Secure Access Control Server (ACS)
using EAP is an example of an authentication server
WLC Components

• WLANs are identified by unique SSID network names.

The LAN is a logical entity. Each WLAN is assigned to
an interface in the WLC. Each WLAN is configured with
radio policies, quality of service (QoS), and other
WLAN parameters. A WLC interface is a logical
connection that maps to a VLAN on the wired network.
Each interface is configured with a unique IP address,
default gateways, physical ports, VLAN tag, and DHCP
server.
 WLC Interfaces Types
• Management interface (static,
configured at setup, mandatory)
is used for in-band
• Service-port interface (static,
configured at setup, optional) is
used for out-of-band
management. It is an optional
interface that is statically
configured.
• AP manager interface (static,
configured at setup, mandatory
except for 5508 WLC) is used
for Layer 3 discovery and
association. It has the source IP
address of the AP that is
statically configured.
• Dynamic interface (dynamic) is
analogous to VLANs and is
designated for WLAN client
data.
• Virtual interface (static,
configured at setup, mandatory)
is used for Layer 3 security
authentication, DHCP relay
support, and mobility
management.
Roaming

• The primary reason to have wireless networks is roaming: the

ability to access network resources from common areas and in
areas where it is difficult to run cabling. End clients might want to
move from one location to another. Mobility allows users to access
the network from several locations. Roaming occurs when the
wireless client changes association from one AP to another. The
challenge is to scale the wireless network to allow client roaming
that is seamless and secure. Roaming can be intracontroller or
intercontroller.
 Intracontroller Roaming

Intracontroller roaming, shown in Figure,

occurs when a client moves association
from one AP to another AP that is joined to
the same WLC. The WLC updates the
client
database with the new associated AP and
does not change the client’s IP address. If
required,
clients are reauthenticated, and a new
security association is established. The
client database remains on the same WLC
 Layer 2 Intercontroller Roaming

Intercontroller roaming occurs

when a client moves association
from one AP to another when the
client traffic is bridged to the same IP
subnet. Figure shows Layer 2
intercontroller
roaming. Traffic remains of the same
IP subnet, and no IP address changes
to the client occur. The client database
is moved from WLC1 to WLC2. The
client is reauthenticated, and a new
security session is established
Layer 3 Intercontroller Roaming
• With Layer 3 intercontroller roaming, shown in Figure, a client
moves association from one AP to another AP that is joined to a
different WLC that is on a different IP subnet than the first WLC.
Then the traffic is bridged onto a different IP subnet. When the
client associates to AP2, WLC2 then exchanges mobility
messages with WLC1. The original client database is not moved
to WLC 2. Instead, WLC1 marks the client with an “Anchor” entry
in its database. The database entry is copied to WLC2’s
database and is marked as a “Foreign” entry. The wireless client
maintains its original IP address and is reauthenticated. A new
security session is then established. Client traffic then routes in
an asymmetric manner. Traffic from the client is forwarded by the
Foreign WLC, but traffic to the client arrives at the Anchor WLC,
which forwards it through an Ethernet-in-IP (EtherIP) tunnel to
the Foreign WLC. The Foreign WLC forwards the data traffic to
the client.
Layer 3 Intercontroller Roaming
WLAN Design Controller Redundancy
Design: Deterministic vs. Dynamic
• WLCs can be configured for dynamic or deterministic
redundancy. For deterministic redundancy, the AP is configured
with a primary, secondary, and tertiary controller. This requires
more upfront planning but allows better predictability and faster
failover times.
• Deterministic redundancy is the recommended best practice.
N+1, N+N, and N+N+1 are examples of deterministic
redundancy. Advantages of deterministic redundancy include
■ Predictability
■ Network stability
■ Flexible and powerful redundancy design options
■ Faster failover times
■ Fallback option in case of failover
• The disadvantage of deterministic controller redundancy is that it
requires more upfront planning and configuration.
WLAN Design Controller Redundancy
Design: Deterministic vs. Dynamic
• Dynamic controller redundancy uses CAPWAP to load
balance APs across WLCs. CAPWAP populates APs
with a backup WLC. This solution works better when
WLCs are in a centralized cluster. The disadvantages
are longer failover times and unpredictable operation.
• An example is adjacent APs registering with differing
WLCs. Advantages of Dynamic controller redundancy
include
■ Easy to deploy and configure
■ Access Points dynamically load balance
• Disadvantages include longer failover times,
unpredictable operation, more intercontroller roaming,
and no fallback option in the event of controller failure.
WLC Redundancy (N+1)
WLC Redundancy (N+N)
WLC Redundancy (N+N+1)
WLC Redundancy - Resume
Radio Management and RF Groups
• The limit of available channels in the ISM frequencies used by the
IEEE 802.11b/g/n standard presents challenges to the network
designer. There are three nonoverlapping channels (channels 1, 6,
and 11). The recommended best practice is to limit the number of
data devices connected to each AP to 20, or no more than 7
concurrent voice over WLAN (VoWLAN) calls using G.711 or 8
concurrent VoWLAN calls using G.729. Additional APs should be
added as user population grows to maintain this ratio of data and
voice per AP.
• Cisco Radio Resource Management (RRM) is a method to
manage AP RF channel and power configuration. Cisco WLCs use
the RRM algorithm to automatically configure, optimize, and self-
heal. Cisco RRM functions are as follows:
Radio Management
■ Radio resource monitoring: are sent to the WLC, which can
detect rouge APs, clients, and interfering Aps
■ Dynamic channel assignment: WLCs automatically assign
channels to avoid interference.
■ Interference detection and avoidance: As Cisco LWAPs monitor
all channels, interference is detected by a predefined threshold (10
percent by default). Interference can be generated by rogue APs,
microwaves, cordless telephones, Bluetooth devices, neighboring
WLANs, or other electronic devices.
■ Dynamic transmit power control: The WLCs automatically
adjust power levels.
■ Coverage hole detection and correction: WLCs may adjust the
power output of APs if clients report that a low received signal
strength indication (RSSI) level is detected.
■ Client and network load balancing: Clients can be influenced to
associate withcertain APs to maintain network balance.
RF Groups
• An RF group is a cluster of WLC devices that coordinate their RRM
calculations. When the WLCs are placed in an RF group, the RRM
calculation can scale from a single WLC to multiple floors, buildings, or
even the campus. As shown in Figure, APs send neighbor messages to
other APs. If the neighbor message is above –80 dBm, the controllers
form an RF group. The WLCs elect an RF group leader to analyze the RF
data. The RF group leader exchanges messages with the RF group
members using UDP port 12114 for 802.11b/g/n and UDP port 12115 for
802.11a. RF groups are formed with the following process:
1. APs send out neighbor messages over the air. The message includes an
encrypted shared secret that is configured in the WLC and pushed to each
AP.
2. APs sharing the same secret are able to validate messages from each
other. Neighbor messages need to be over –80dBm to form a RF group.
3. The members in the RF group elect an RF group leader to maintain a
“master” power and channel scheme for the RF group. The RF group leader
analyzes real-time radio data collected by the system and calculates the
master power and channel plan.
RF Groups
RF Site Surveys
• Similar to performing an assessment for a wired
network design, RF site surveys are done to determine
design parameters for WLANs and customer
requirements. RF site surveys help determine the
coverage areas and check for RF interference. This
helps determine the appropriate placement of wireless
APs. Steps:
1. Devices to support, sites where wireless devices will
be located
2. Obtain a facility diagram to identify the potential RF
obstacles
3. Visually inspect the facility to look for potential
barriers to the propagation of RF signals, such as
metal racks, elevator shafts, and stairwells
RF Site Surveys (Cont)
4. Identify user areas that may be intensively used, such as
conference rooms, and areas that are not heavily used, such as
stairwells.
5. Determine preliminary AP locations, which need power, wired
network access, cell coverage and overlap, channel selection,
mounting locations, and antennas.
6. Perform the actual survey by using an AP to survey the location
and received RF strength based on the targeted AP placement.
Consider the effects of electrical machinery. Microwave ovens and
elevators might distort the radio signal from the APs.
7. Document the findings by recording the target AP locations, log
signal readings, and data rates at outer boundaries. Information
included in the report includes the following:
■ Detail customer requirements; describe and diagram AP coverage.
■ Parts list, including APs, antennas, accessories, and network
components.
■ Describe tools used and methods used for the survey.
 Wireless Mesh for Outdoor Wireless
• Traditionally, outdoor wireless
solutions have been limited to
point-to-point and point-to
multipoint bridging between
buildings. With these solutions,
each AP is wired to the
network. The Cisco wireless
mesh networking solution,
shown in Figure, eliminates the
need to wire each AP and
allows users to roam from one
area to another without having
to reconnect.
Wireless Mesh for Outdoor Wireless (Cont)
Wireless Mesh for Outdoor Wireless (Cont)
• Mesh Design Recommendations: The following are Cisco
recommendations (and considerations) for mesh design:
■ There is a < 10-ms latency per hop. Typically 2 ms to 3
ms.
■ For outdoor deployment, four or fewer hops are
recommended for best performance. A maximum of eight
hops is supported.
■ For indoor deployment, one hop is supported.
■ For best performance, 20 MAP nodes per RAP is
recommended. Up to 32 MAPs is supported per RAP.
■ Throughput: one hop =14 Mbps, two hops = 7 Mbps,
three hops = 3 Mbps, four hops = 1 Mbps.
Campus Design Considerations
• When designing for the Cisco Unified Wireless Network, you need to be able
to determine how many LWAPs to place and how they will be managed with
the WLCs. Table summarizes campus design considerations.