Juniper JUNOSE SOFTWARE 11.2.X - LINK LAYER CONFIGURATION GUIDE 7-7-2010 Configuration Manual page 358

JunosE 11.2.x Link Layer Configuration Guide
encapsulation mlppp
interface mlppp
member-interface
ppp fragmentation
326
host1(config-l2tp-dest-profile-host)#profile l2tp-profile
Use to configure MLPPP as the encapsulation method on an individual interface.
Use this command only within the context of an individual interface. Issuing this
command creates an MLPPP link interface, which can be configured as a member of
an MLPPP bundle.
Example
host1(config)#interface serial 2/0:1/1
host1(config-if)#encapsulation mlppp
Use the no version to disable MLPPP on an interface.
See encapsulation mlppp.
Use to create an MLPPP network interface, also known as an MLPPP bundle.
Example
host1(config-if)#interface mlppp group2
Use the no version to delete the MLPPP bundle. To delete an MLPPP bundle you must
first delete the IP interface, then delete the bundle members (link interfaces), and
finally delete the MLPPP bundle itself.
See interface mlppp.
Use to add an MLPPP link interface—also known as an MLPPP bundle member—to an
MLPPP bundle.
Example
host1(config-if)#member-interface serial 2/0:1/1
Use the no version to remove the specified interface from the MLPPP bundle.
See member-interface.
Use to enable fragmentation on an MLPPP link interface.
If fragmentation is enabled on the link, you can optionally specify the maximum
fragment size to be used on that link, in the range 128–65535 octets.
A link's maximum fragment size cannot exceed the MTU size on that link.
We recommend that all member links in an MLPPP bundle be assigned the same
fragment size.
Do not configure both MLPPP fragmentation and IP fragmentation of L2TP packets
(with the ip mtu command) on the same interface. Instead, you must choose only one
of the fragmentation configurations by setting it to the necessary value and set the
other fragmentation configuration to the maximum allowable value.
Copyright © 2010, Juniper Networks, Inc.