Scenario 2: Multiple Tcp Connections; Figure 5: Policer Behavior With A Single Tcp Connection; Figure 6: Policer Behavior With Background Traffic - Juniper EX9200 Features Manual

Scenario 2: Multiple TCP Connections

Related
Documentation
Copyright © 2016, Juniper Networks, Inc.

Figure 5: Policer Behavior with a Single TCP Connection

Traffic
Volume
Unused Bandwidth
The problem presented in this scenario is that some bandwidth is available, but it is not
being used by the traffic. The unused bandwidth shown in
of an overall data throughput that is lower than the configured bandwidth value. This
example is an extreme case because there is only a single TCP connection.
With multiple TCP connections or some background non-TCP-based traffic, there is less
unused bandwidth, as depicted in
bandwidth still exists if all the TCP connections experience a drop when the aggregated
traffic rate exceeds the configured bandwidth limit.
Figure 6: Policer Behavior with Background Traffic (Multiple TCP
Connections)
Traffic
Volume
Unused Bandwidth
Multiple
TCP Connections
To reduce the problem of unused bandwidth in your network, you can configure a burst
size.
Policer Implementation Overview on page 25
Determining Proper Burst Size for Traffic Policers on page 30
Chapter 5: Implementing Traffic Policers on EX 9200 Switches
Bandwidth Limit
Figure 6 on page 29. However, the same issue of unused
Bandwidth Limit
Background Traffic
Time
Figure 5 on page 29 is the result
Time
29