You can associate a parameter definition with a byte adjustment application to adjust the shaping rates for ADSL and VDSL traffic on E-series routers.
The byte adjustment differs for interfaces with cell shaping mode and frame shaping mode. For ADSL traffic, JUNOSe software supports a byte adjustment application (qos-byte-adjustment) to adjust rates for cell shaping mode. For VDSL traffic, JUNOSe software supports a frame byte-adjustment application (qos-frame-byte-adjustment) to adjust rates for frame shaping mode.
Frame is the default shaping mode for Ethernet interfaces on E-series routers. To configure the cell shaping mode, issue the qos-shaping-mode command or by specifying the qos-cell-mode application with a parameter definition.
Managing the bandwidth of downstream ATM traffic to Ethernet interfaces is difficult because of the different layer 2 encapsulations. To reduce the number of packet drops in the Ethernet network, you can use the byte adjustment applications to account for the different encapsulations.
To adjust the shaping rates to account for different layer 2 encapsulations as well as the ATM cell pad, header, and trailer on interfaces, apply a parameter with the cell byte-adjustment application (qos-byte-adjustment).
When you apply a parameter with the qos-byte-adjustment application to an interface with frame shaping mode, you adjust shaping rates to account for different layer 2 encapsulations only.
The system counts the bytes transmitted to track the shaping rate. Instead of counting the actual packet size, the system uses the CPE packet size. You can configure the byte adjustment so that the shaping rate matches the CPE bandwidth.
By default, the byte adjustment is set to 0. If the overhead between the access node and CPE is 0, you do not need to configure the byte adjustment value.
Figure 65 displays an example of an Ethernet encapsulation and an ATM encapsulation.
Figure 65: Byte Adjustment Calculation for Ethernet and ATM Encapsulations
Table 30 lists the header lengths for the Ethernet encapsulation, which represents the CPE protocol overhead. The hierarchy is PPPoE over S-VLAN over Ethernet.
Table 30: Header Lengths for Ethernet Encapsulation
Table 31 lists the header lengths for the ATM encapsulation, which represents the B-RAS protocol overhead. The interface stack is PPPoA over ATM 1483 with LLC Mux. The ATM AAL5 trailer is considered cell tax and is not part of the byte adjustment calculation.
Table 31: Header Lengths for ATM Encapsulation
|
Header |
Number of Bytes |
|---|---|
|
ATM AAL5 LLC |
4 bytes |
|
PPP |
2 bytes (2-protocol id) |
| Total |
6 bytes |
The byte adjustment calculation for these encapsulations is:
Packet fragmentation can occur at a DSLAM because of the associated segment header that is added for VDSL2 in frame mode. Because the segment header is not included in the ANCP rate report, the forwarding rate on an E-series router can be higher than the DSLAM rate, which can result in packet loss.
You can use a QoS parameter expression with the frame byte-adjustment application to reduce the forwarding rate so that it matches the rate at the DSLAM. To adjust rates for interfaces with frame shaping mode, apply the frame byte-adjustment application (qos-frame-byte-adjustment).
When you apply a parameter with the qos-byte-adjustment application to an interface with frame shaping mode, you adjust shaping rates to account for different layer 2 encapsulations only.
You can create parameter instances for the cell byte-adjustment application and the frame byte-adjustment application on the same system. The system performs the byte adjustment calculation based on the shaping mode specified. The byte adjustment can have both a positive and negative value.
Table 32 lists the final byte adjustment value that the system uses depending on the configured shaping mode and the value that you configured for the byte adjustment applications.
Table 32: Byte Adjustment Values for Frame and Cell Shaping Modes
 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |