Cisco Cisco Aironet 350 Mini-PCI Wireless LAN Client Adapter Guia Do Desenho
2-30
Enterprise Mobility 4.1 Design Guide
OL-14435-01
Chapter 2 Cisco Unified Wireless Technology and Architecture
Design Considerations
Figure 2-17
Layer 3 Connected WLC
Traffic Load and Wired Network Performance
When deploying a Unified Wireless solution, questions often arise concerning:
•
LWAPP traffic impact/load across the wired backbone.
•
Minimum performance requirements to support a Unified Wireless deployment.
•
Relative benefits of a distributed versus centralized WLC deployment in the context of traffic load
on the network.
on the network.
In examining the impact of the LWAPP traffic in relation to overall network traffic volume, there are
three main points to consider:
three main points to consider:
•
The volume of LWAPP control traffic—The volume of traffic associated with LWAPP control can
vary depending on the actual state of the network. That is to say, it is usually higher during a
software upgrade or WLC reboot situations. With that said, traffic studies have found that the
average load LWAPP control traffic places on the network is approximately 0.35 Kb/sec. In most
campuses, this would be considered negligible, and would be of no consequence when considering
a centralized deployment model over a distributed one.
vary depending on the actual state of the network. That is to say, it is usually higher during a
software upgrade or WLC reboot situations. With that said, traffic studies have found that the
average load LWAPP control traffic places on the network is approximately 0.35 Kb/sec. In most
campuses, this would be considered negligible, and would be of no consequence when considering
a centralized deployment model over a distributed one.
•
The overhead introduced by tunneling—A Layer 3 LWAPP tunnel adds 44 bytes to a typical IP
packet to and from a WLAN client. Given that average packets sizes found on typical enterprises are
approximately 300 bytes, this represents an overhead of approximately 15 percent. In most
campuses, this overhead would be considered negligible, and again would be of no consequence
when considering a centralized deployment model over a distributed one.
packet to and from a WLAN client. Given that average packets sizes found on typical enterprises are
approximately 300 bytes, this represents an overhead of approximately 15 percent. In most
campuses, this overhead would be considered negligible, and again would be of no consequence
when considering a centralized deployment model over a distributed one.
Clients
Voice
Data
Voice
Data
190711
Layer 3
LWAPP
LWAPP