Multi-Vc Mlp Over Atm-Based Lfi; Feature History For Multi-Vc Mlp Over Atm-Based Lfi; Fragment Size Calculation For Multi-Vc Mlp Over Atm-Based Lfi - Cisco 10000 Series Configuration Manual

Chapter 16 Fragmenting and Interleaving Real-Time and Nonreal-Time Packets

Multi-VC MLP Over ATM-Based LFI

Multi-VC MLP over ATM-based LFI uses the fragmentation and interleaving capability of MLP to
integrate real-time and nonreal-time packets together on the same link. MLP defines the mechanisms to
fragment, reassemble, and sequence large datagrams across multiple logical data links. MLP uses the
fragmentation and packet sequencing specifications defined in RFC 1990 to implement link
fragmentation and interleaving at the bundle level. Multi-VC MLP over ATM-based LFI supports up to
10 member links per MLP bundle, one of which is LFI-enabled.
MLP encapsulates real-time packets as PPP over ATM (PPPoA) and sends the packets to a priority
transmit queue to enable the router to transmit the real-time packets earlier than other packet flows. The
router interleaves the real-time packets between the fragments of the larger, nonreal-time packet over a
single point-to-point link to the remote address. Upon receipt, the receiving fragmentation peer
processes the real-time packets as PPPoA packets.
MLP fragments the large data packets to a size small enough to satisfy the delay requirements of
real-time traffic. MLP encapsulates the packets as MLP packets and sends the packets to a first-in
first-out (FIFO) queue to enable the router to transmit the fragments at the same time over multiple
point-to-point links to the same remote address. Upon receipt, the receiving fragmentation peer
reassembles the fragments to the original packet and then processes it as PPPoA. The underlying PPP
encapsulation conforms to RFC 1661.
MLP fragments all outbound MLP packets with a payload that is larger than the specified fragment size.
The smallest fragment size depends on the AAL5 encapsulation type and whether or not protocol
compression is enabled. For more information, see the
ATM-Based LFI" section on page
When configuring Multi-VC MLP over ATM-based LFI, you must configure a virtual template interface
for the MLP bundle. However, the virtual template does not need to be unique for each bundle—multiple
MLP bundles can share the same virtual template.

Feature History for Multi-VC MLP Over ATM-Based LFI

Cisco IOS Release
Release 12.2(27)SBB The Multi-VC MLP over ATM-based LFI feature was
Release 12.2(31)SB2

Fragment Size Calculation for Multi-VC MLP Over ATM-Based LFI

For Multi-VC MLP over ATM-based LFI, the ideal fragment size should allow the fragments to fit into
an exact multiple of ATM cells.
Single-VC and Multi-VC MLP over ATM-based LFI. As shown in the table, the minimum fragment size
depends on the AAL5 encapsulation type used and whether or not protocol compression is enabled.
For more information, see the
page
OL-7433-09
Description
introduced on the router for the PRE2.
This feature was introduced on the PRE3 and the valid
multilink interface values changed from 1 to 9999
(Release 12.2(28)SB and later) to from 1 to 9999 and
65,536 to 2,147,483,647.
"Fragment Size Calculation for MLP Over ATM-Based LFI" section on
16-15.
Multilink PPP-Based Link Fragmentation and Interleaving
"Fragment Size Calculation for MLP Over
16-15.
Table 16-2 on page 16-15
Cisco 10000 Series Router Quality of Service Configuration Guide
Required PRE
PRE2
PRE3
lists the minimum fragment sizes for
16-19