Fragmentation by Forwarding Class Overview
For Multiservices and Services Physical
Interface Card (PIC) link services IQ (LSQ) and virtual
LSQ redundancy (rlsq-) interfaces, you can specify fragmentation
properties for specific forwarding classes. Traffic on each forwarding
class can be either multilink fragmented or interleaved. By default,
traffic in all forwarding classes is fragmented.
If you do not configure fragmentation properties for particular forwarding classes in multilink
Point-to-Point Protocol (MLPPP) interfaces, the fragmentation threshold you set at the
[edit interfaces interface-name unit
logical-unit-number fragment-threshold] hierarchy
level is used for all forwarding classes within the MLPPP interface. If you do not set a
maximum fragment size anywhere in the configuration, packets are still fragmented if
they exceed the smallest maximum transmission unit (MTU) of all the links in the
bundle.
To configure fragmentation by forwarding class, include
the following statements at the [edit class-of-service] hierarchy level:
[edit class-of-service] fragmentation-maps { map-name { forwarding-class class-name { drop-timeout milliseconds; fragment-threshold bytes; multilink-class number; no-fragmentation; } } } interfaces { interface-name { unit logical-unit-number { fragmentation-map map-name; } } }