Configuring Fragmentation by Forwarding Class

For Adaptive Services (AS) PIC link services IQ interfaces (lsq) only, 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 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. For MLFR FRF.16 interfaces, the fragmentation threshold you set at the [edit interfaces interface-name mlfr-uni-nni-bundle-options fragment-threshold] hierarchy level is used for all forwarding classes within the MLFR FRF.16 interface. If you do not set a maximum fragment size anywhere in the configuration, packets are still fragmented if they exceed the smallest MTU of all the links in the bundle.

To configure fragmentation by forwarding class, you can include the following statements at the [edit class-of-service] hierarchy level of the configuration:

class-of-service {

    fragmentation-maps {

        map-name {

            forwarding-class class-name {

                fragment-threshold bytes;

                multilink-class number;

                no-fragmentation;

            }

        }

    }

    interfaces {

        interface-name {

            unit logical-unit-number {

                fragmentation-map map-name;

            }

        }

    }

}

This chapter discusses the following topics:

• Configuring Fragmentation by Forwarding Class
• Associating a Fragmentation Map with a Multilink PPP Interface or MLFR FRF.16 DLCI