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

Configuring the Link Services PICs

The Multilink Protocol 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 Links Services PIC supports the following Multilink Protocol encapsulation types at the logical unit level:

Multilink Point-to-Point Protocol (MLPPP)
Multilink Frame Relay (MLFR FRF.15)

The Link Services PIC also supports the Multilink Frame Relay UNI and NNI (MLFR FRF.16) encapsulation type at the physical interface level.

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-virtual circuit (VC) basis. Each bundle can support multiple VCs. The physical connections must be E1, T1, channelized DS3 to DS1, channelized DS3 to DS0, channelized E1, channelized STM 1, or channelized IQ interfaces.

The default number of bundles per Link Services PIC is 16, ranging from ls-fpc/pic/port:0 to ls-fpc/pic/port:15.

To configure the number of bundles on a Link Services PIC, include the mlfr-uni-nni-bundles statement at the [edit chassis fpc slot-number pic pic-number] hierarchy level:



[edit chassis fpc slot-number pic pic-number]

mlfr-uni-nni-bundles number;

The maximum number of MLFR UNI NNI bundles each Link Services PIC can accommodate is 128. A link can associate with one link services bundle only. For more information, see the JUNOS Network Interfaces Configuration Guide.

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

Multiclass Extension to MLPPP (RFC 2686)

This extension enables multiple classes of service using MLPPP. For more information, see RFC 2686, The Multi-Class Extension to Multi-Link PPP. The JUNOS software PPP implementation does not support the negotiation of address field compression and protocol field compression PPP NCP options. The software always send a full 4-byte PPP header.

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