Network support: An overview of traffic shaping

What is traffic shaping?

Traffic shaping is a method of limiting the bandwidth going through an interface. Typically, traffic shaping will have a committed information rate (CIR) measured in bits/second (bps). For example, if you purchase a 100Mbps circuit, the CIR is 100,000,000 bps. With traffic shaping, any traffic that exceeds the average bit rate will be buffered, the size of the buffer is referred to as queue-limit in Cisco terms, but other vendors may call it something else. With traffic policing, any traffic that exceeds the average bit rate will be dropped or re-marked for discard eligibility, depending on how the policer is configured. Most Metro Ethernet providers will configure their policers to drop the traffic that exceeds the policer rate.

The average traffic shaping rate is achieved by sending small chunks of data at defined intervals. For example, say you are a baseball pitcher who can throw 10 baseballs per second (Bbps). You can achieve this rate in more than one way. If you throw 2 baseballs every 200ms (milliseconds), that will achieve 10 Bbps. Intervals of 200ms means there will be 5 intervals in one second (1000ms/200ms). Two baseballs times 5 intervals = 10 Bbps. Another way of achieving the same rate is to throw 5 baseballs every 500ms. This leaves us with 2 intervals in one second (1000ms/500ms). Five baseballs times 2 intervals = 10 Bbps.

In the first example our Tc = 200ms, our Bc = 2 baseballs and our CIR was 10 Bbps

In the second example our Tc = 500ms, our Bc = 5 baseballs and our CIR was 10 Bbps
 

• Tc = Time between throwing baseballs
• Bc = number of baseballs thrown
• CIR = average number of baseballs over one second
   

The rate at which the pitcher throws baseballs is important to the catcher. The catcher can only catch 2 baseballs every 200ms, if 5 baseballs are thrown to the catcher every 500ms, the catcher will likely drop baseballs. In our analogy the catcher is the policer controlled by the local Metro Ethernet provider and the pitcher is the shaper at the CE WAN interface, which is either controlled by the end user or Lumen (if you purchased managed equipment).

• Adding traffic shaping with the default burst sizes is better than not having traffic shaping
• When it comes to traffic shaping there is no one size fits all, the burst sizes and queue-limit may need to be tweaked to obtain the best performance
• Some vendors will represent the burst sizes in different formats (bytes vs. bits)

Do I need traffic shaping?

• Yes: When purchasing Metro Ethernet service
• Yes: When the purchased CIR is less than port speed
  
• No: If you have a DS1, DS3, or OCx circuit
  
• No: If the purchased CIR is equal to the port speed
   

Who needs to configure traffic shaping?

If you are providing your own CPE, then you would need to configure traffic shaping on your WAN interface facing Lumen. If you purchased a managed CPE device from Lumen, then we would configure traffic shaping for you on the managed CPE.

Where should I apply traffic shaping?

Metro Ethernet providers will police traffic ingress at the User Network Interface (UNI). The UNI is also known as the demarcation between the CPE and the Metro Ethernet provider. Traffic shaping should be applied egress at the CPE-WAN interface.

Why is traffic shaping important?

The IPERF results below show the importance of traffic shaping. The last line (in bold) shows the average rate over the full test, each line in the middle represents the rate at one-second intervals. The column on the left shows the rate fluctuating around 7–10Mbps. These poor results and fluctuation are due to drops in a policer, this is because TCP will react to the packet loss and slow down as a result. The column on the right shows a more steady rate around 43–44Mbps. This is the result after adding 50Mbps traffic shaping which resolved the policer drops.

Missing or misconfigured traffic shaping can degrade any application (voice, video, data, etc).