Configuring Fragmentation And Reassembly For Mlppp Bundles - Juniper JUNOSE SOFTWARE 11.2.X - LINK LAYER CONFIGURATION GUIDE 7-7-2010 Configuration Manual

ppp multilink enable
ppp reassembly
profile

Configuring Fragmentation and Reassembly for MLPPP Bundles

Copyright © 2010, Juniper Networks, Inc.
Example
host1(config-if)#ppp fragmentation 128
Use the no version to disable fragmentation on the link and restore the default fragment
size, which is the link's MTU.
See ppp fragmentation.
Use in a profile to enable the creation of dynamic MLPPP interfaces.
Example
host1(config-profile)#ppp multilink enable
Use the no version to reject any incoming requests to create dynamic MLPPP interfaces.
See ppp multilink enable.
Use to enable reassembly on an MLPPP link interface.
If reassembly is enabled on the link, you can optionally specify the administrative MRRU
for the link, in the range 64–65535 octets. The administrative MRRU is the maximum
allowable size of the PPP packet payload that the router can receive.
A link's MRRU must be greater than or equal to the local MRU on that link.
We recommend that all member links in an MLPPP bundle be assigned the same
reassembly setting: enabled or disabled.
Example
host1(config-if)#ppp reassembly 1590
Use the no version to disable reassembly on the link and restore the default value,
which is the local MRU on the link.
See ppp reassembly.
Use to create a profile for a dynamic interface.
You specify a profile name of up to 80 characters.
Example
host1(config)#profile dynmlppp1
Use the no version to remove a profile.
See profile.
If you issue the ppp fragmentation command or the ppp reassembly command in the
context of an MLPPP bundle, the command affects all the current member links in the
Chapter 9: Configuring Multilink PPP
327