Mlp-based link fragmentation and interleaving, Configuring mlp bundles and member links – Cisco 10000 User Manual
Page 442
19-24
Cisco 10000 Series Router Software Configuration Guide
OL-2226-23
Chapter 19 Configuring Multilink Point-to-Point Protocol Connections
MLP-Based Link Fragmentation and Interleaving
•
QoS on interfaces towards the CPE and the tunnel is not supported.
•
Only single-member MLPoE bundles are supported (with LFI support). The maximum number of
single-member MLPoE bundles that can be supported is 10240.
MLP-Based Link Fragmentation and Interleaving
MLP supports link fragmentation and interleaving (LFI). The MLP fragmentation mechanism multilink
encapsulates large nonreal-time packets and fragments them into a small enough size to satisfy the delay
requirements of real-time traffic. Smaller real-time packets are not multilink encapsulated. Instead, the
MLP interleaving mechanism provides a special transmit queue (priority queue) for these delay-sensitive
packets to allow the packets to be sent earlier than other packet flows. Real-time packets remain intact
and MLP interleaving mechanisms send the real-time packets between fragments of the larger non-
real-time packets.
For more information about link fragmentation and interleaving, see the “Fragmenting and Interleaving
Real-Time and Nonreal-Time Packets” chapter in the Cisco 10000 Series Router Quality of Service
Configuration Guide.
Note
In PRE1, Cisco 10000 series routers support fragmentation only on single link bundles when configured
for LFI, using the ppp multilink interleave command. However, for multiple link bundles, the router
does not support fragmentation and interleaving. You can turn off fragmentation by using the no ppp
multilink fragmentation command on the Cisco 10000 router and the peer end.
Configuring MLP Bundles and Member Links
shows the components you must define when configuring MLP (without link fragmentation
and interleaving) on specific interface types.
To configure MLP bundles and member links, perform the following configuration tasks:
•
Creating an MLP Bundle Interface, page 19-25
•
Enabling MLP on a Virtual Template, page 19-26
•
Adding a Serial Member Link to an MLP Bundle, page 19-27
•
Adding an ATM Member Link to an MLP Bundle, page 19-29
The following configuration tasks are optional:
•
Moving a Member Link to a Different MLP Bundle, page 19-32
•
Removing a Member Link from an MLP Bundle, page 19-33
Table 19-7
Requirements for Configuring MLP
Type
MLP Bundle
Member Links
Virtual Template
Service Policy
MLP over Serial
Required
Required
Not required
Not required
Single-VC MLP over ATM
Required
Required
Required
Required
1
1.
A service policy is required only when configuring MLP-based link fragmentation and interleaving (LFI) for Single-VC or
Multi-VC MLP over ATM. For MLP-based LFI, a service policy with a priority queue defined must be attached to the
multilink interface. The VC does not require a service policy.
Multi-VC MLP over ATM
Required
Required
Required
Required
1