Cisco Cisco 2000 Series Wireless LAN Controller Livre blanc
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
requirements on the infrastructure, and in most typical deployments, there is no need to add extra capacity to
the infrastructure in order to accommodate Cisco Unified Wireless Architecture. As a summary of the traffic
study, these quick facts about the operation of LWAPP can be kept in mind:
the infrastructure in order to accommodate Cisco Unified Wireless Architecture. As a summary of the traffic
study, these quick facts about the operation of LWAPP can be kept in mind:
Although latency is an important consideration, this traffic−study presents throughput considerations
only. As a general guideline, the AP−to−WLC link must not exceed 100ms round−trip latency.
only. As a general guideline, the AP−to−WLC link must not exceed 100ms round−trip latency.
•
There are two separate channels for the operation of LWAPP:
LWAPP Data
♦
LWAPP Control traffic
♦
•
LWAPP operation is broken down into two broad categories:
one−time exchanges
♦
on−going exchanges
♦
•
A 20 minute sample that includes initial exchanges results in an average utilization statistic of 0.001
percent.
percent.
•
A 20 minute sample of on−going exchanges results in a maximum utilization statistic of 0.35
kilobits/second.
kilobits/second.
•
The LWAPP Data channel adds a header of 6 bytes to each 802.11 data packet. There is no additional
overhead for IP Fragments.
overhead for IP Fragments.
•
An hour−long sample presents this break−up of protocols and their respective percentages:
•
Figure 10: Protocol Comparison based on a 1−hour capture with low data traffic, IP Fragments and
majority LWAPP
majority LWAPP
Related Information
Lightweight AP (LAP) Registration to a Wireless LAN Controller (WLC)
•
LWAPP Fundamentals
•