Dynamic MLPPP over L2TP Example

The following example configures MLPPP fragmentation and reassembly for a dynamic MLPPP interface over L2TP over a Gigabit Ethernet interface.

encapsulation mlppp

• 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.

interface 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.

member-interface

• 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.

ppp fragmentation

• 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.
• 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.

ppp multilink enable

• 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.

ppp reassembly

• 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.

profile

• 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.

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.