[Contents] [Prev] [Next] [Index] [Report an Error]

Configure Multilink and Link Services Interfaces

The Multilink Protocol (MP) enables you to split, recombine, and sequence datagrams across multiple logical data links. The goal of multilink operation is to coordinate multiple independent links between a fixed pair of systems, providing a virtual link with greater bandwidth than any of the members.

The JUNOS software supports two MP-based services PICs: the Multilink Services PIC and the Link Services PIC. These two PICs support the following MP encapsulation types at the logical unit level:

In addition, the Link Services PIC supports the Multilink Frame Relay User-to-Network Interface (UNI) and the Network-to-Network Interface (NNI) (MLFR FRF.16) encapsulation type at the physical interface level. It also supports tunnel services; for more information, see Configure Tunnel Interfaces.

MLPPP and MLFR (FRF.15) are supported on interface types ml-fpc/pic/port and ls-fpc/pic/port. For MLFR (FRF.15), multiple permanent virtual circuits (PVCs) are combined into one aggregated virtual circuit (AVC). This provides fragmentation over multiple PVCs on one end and reassembly of the AVC on the other end.

MLFR (FRF.16) is supported on a channelized interface, ls-fpc/pic/port:channel, which denotes a single MLFR (FRF.16) bundle. For MLFR (FRF.16), multiple links are combined to form one logical link. Packet fragmentation and reassembly occur on a per-VC basis. Each bundle can support multiple VCs. Link Services PICs can support up to 256 DLCIs per MLFR (FRF.16) bundle. The physical connections must be E1, T1, Channelized DS-3 to DS-1, Channelized DS-3 to DS-0, Channelized E1, Channelized STM-1, or Channelized QPP interfaces. When you bundle channelized interfaces using the Link Services interface, the channelized interfaces require M-series Enhanced FPCs.

The standards for MLPPP, MLFR FRF.15, and MLFR FRF.16 are defined in the following specifications:

To configure multilink and link services interface properties, include the ml-fpc/pic/port or ls-fpc/pic/port:channel statement at the [edit interfaces] hierarchy level: 

[edit interfaces]

(ml-fpc/pic/port | ls-fpc/pic/port) {

    unit logical-unit-number {

        dlci dlci-identifier;

        drop-timeout milliseconds;

        encapsulation type;

        fragment-threshold bytes;

        interleave-fragments;

        minimum-links number;

        mrru bytes;

        multicast-dlci dlci-identifier;

        short-sequence;

        family family {

            address address {

                destination address;

            }

            bundle (ml-fpc/pic/port | ls-fpc/pic/port);

            }

        }

    }

}








 The Multilink Services PIC is not compatible with the M40e, M160, or T-series platforms.


 The Link Services PIC is not compatible with the M160 or T-series platforms.

To configure link services physical interface properties, include the mlfr-uni-nni-bundle-options statement at the [edit interfaces ls-fpc/pic/port:channel] hierarchy level:

[edit interfaces ls-fpc/pic/port:channel]

encapsulation type;

mlfr-uni-nni-bundle-options {

    acknowledge-retries number;

    acknowledge-timer milliseconds;

    action-red-differential-delay (disable-tx | remove-link);

    drop-timeout milliseconds;

    fragment-threshold bytes;

    hello-timer milliseconds;

    lmi-type (ansi | itu);

    minimum-links number;

    mrru bytes;

    n391 number;

    n392 number;

    n393 number;

    red-differential-delay milliseconds;

    t391 number;

    t392 number;

    yellow-differential-delay milliseconds;

}

This chapter is organized as follows:

For examples of multilink and link services interface configuration, see the following sections:

[Contents] [Prev] [Next] [Index] [Report an Error]