Configuring Drop Timeout Interval for Fragmentation by Forwarding Class
For LSQ interfaces configured for multiclass
MLPPP, you can change the drop timeout interval that the interface
waits for fragment resequencing by forwarding class. This feature
is mutually exclusive with the no-fragmentation statement
configured for a forwarding class.
You can also disable the fragment resequencing function altogether
by forwarding class. You do this by setting the drop-timeout interval to 0.
The drop-timeout interval can also be set at the
bundle level. When the drop-timeout interval is set to
0 at the bundle level, none of the individual
classes forward fragmented packets. Sequencing is ignored also, and
packets are forwarded in the order in which they were received. The drop-timeout interval value configured at the bundle level
overrides the values configured at the class level.
This example configures a logical unit on an LSQ interface with a fragmentation map setting different drop timeout values for each forwarding class:
Best effort (BE)—The value of 0 means that no resequencing of fragments takes place for BE traffic.
Expedited Forwarding (EF)—The value of 800 ms means that the multiclass MLPPP waits 800 ms for fragment to arrive on the link for EF traffic.
Assured Forwarding (AF)—The absence of the timeout statements means that the default timeouts of 500 ms for links at T1 and higher speeds and 1500 ms for lower speeds are in effect for AF traffic.
Network Control (NC)—The value of 100 ms means that the multiclass MLPPP waits 100 ms for fragment to arrive on the link for NC traffic.
To configure the drop timeout interval: