This module contains conceptual information and configuration tasks for using Multilink PPP over serial interface links. Multilink PPP is a method used to reduce latency and jitter for real-time traffic.
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to
www.cisco.com/go/cfn. An account on Cisco.com is not required.
Prerequisites for Using Multilink PPP over Serial Interface Links
Knowledge
Be familiar with the concepts in the "Reducing Latency and Jitter for Real-Time Traffic Using Multilink PPP" module.
Enable Queueing Mechanism
Multilink uses first-in first out (FIFO) queuing for queueing and interleaving packets. Other queueing mechanisms such as low latency queueing (LLQ), weighted fair queueing (WFQ), and class-based weighted fair queueing (CBWFQ) can be used. If you want to use one of these alternative mechanisms, enable it before configuring multilink.
Restrictions for Using Multilink PPP over Serial Interface Links
Number of Links per Multilink Bundle
If a multilink bundle has one link or packet order is not important for interleaved packets, use Link Fragmentation and Interleaving (LFI) without multiclass. Use LFI with multiclass if a multilink bundle has multiple links.
VoIP Support
Only Voice over IP (VoIP) is supported.
Queueing Mechanisms Not Supported
Many of the legacy queueing mechanisms are not supported by multilink. These mechanisms include:
Fair queueing on a virtual template interface
Weighted random early detection (WRED) on a virtual template interface
Custom queueing
Priority queueing
Note
Fair queueing, WRED, and priority queueing can be configured in a traffic policy using the Modular Quality of Service (QoS) Command-Line Interface (CLI) (MQC).
Information About Using Multilink PPP over Serial Interface Links
Before using Multilink PPP over serial interface links, a traffic policy (also known as a policy map) must be created. (See the "Prerequisites" section on page 3
.) Policy maps are created using the Modular Quality of Service (QoS) Command-Line Interface (CLI) (MQC).
The MQC is a CLI structure that allows users to create traffic polices (policy maps) and attach these policy maps to interfaces. A policy map contains a traffic class and one or more QoS features. A traffic class is used to classify traffic. The QoS features in the traffic policy determine how to treat the classified traffic.
Multilink Group Interfaces
A multilink group interface is a collection of interfaces bundled together in the multilink PPP configuration. With a multilink group interface, you can bundle interfaces into logical multilink groups.
How to Configure Multilink PPP over Serial Interface Links
Configuring Multilink PPP over Serial Interface Links on a Multilink Group Interface
Before You Begin
Before proceeding with this task, you must create a policy map. The policy map contains the configuration parameters used to apply the specific quality of service feature to the network traffic. To create a policy map, use the MQC. See the MQC and Multilink PPP over Serial Interface Links.
Creates a multilink bundle and enters interface configuration mode.
Enter the multilink bundle number.
Step 4
ipaddressip-addressmask [secondary]
Example:
Router(config-if)# ip address 10.10.100.1 255.255.255.0
Sets a primary IP address for an interface. This command can also set the optional secondary IP address for an interface.
Enter the primary IP address (and, optionally, the secondary IP address).
Step 5
service-policyoutputpolicy-map-name
Example:
Router(config-if)# service-policy output policy1
Attaches the previously created QoS traffic policy (policy map). See the "Prerequisites" section on page 3
. The policy map evaluates and applies QoS features for traffic leaving the interface.
Enter the policy map name.
Step 6
service-policyinputpolicy-map-name
Example:
Router(config-if)# service-policy input policy1
Attaches the previously created QoS traffic policy (policy map). See the "Prerequisites" section on page 3
. The policy map evaluates and applies QoS features for traffic enteringthe interface.
Router(config-if)# ppp multilink fragment delay 20
Specifies a maximum size in units of time for packet fragments on a Multilink PPP (MLP) bundle.
Enter the maximum amount of time, in milliseconds.
Step 8
pppmultilinkinterleave
Example:
Router(config-if)# ppp multilink interleave
Enables interleaving of packets among the fragments of larger packets on a multilink bundle.
Step 9
pppmultilinkmulticlass
Example:
Router(config-if)# ppp multilink multiclass
(Optional) Enables Multiclass Multilink PPP (MCMP) on an interface.
Note
Use this command only if there are multiple links in the multilink bundle.
Step 10
end
Example:
Router(config-if)# end
(Optional) Exits interface configuration mode.
Associating the Serial Interface with the Multilink Group
SUMMARY STEPS
1.enable
2.configureterminal
3.interfaceserialslot/port:timeslot
4.nofair-queue
5.encapsulationppp
6.pppmultilink
7.pppmultilinkgroupgroup-number
8.end
DETAILED STEPS
Command or Action
Purpose
Step 1
enable
Example:
Router> enable
Enables privileged EXEC mode.
Enter your password if prompted.
Step 2
configureterminal
Example:
Router# configure terminal
Enters global configuration mode.
Step 3
interfaceserialslot/port:timeslot
Example:
Router# interface serial 4/1:23
Example:
Specifies a serial interface created on a channelized E1 or channelized T1 controller (for ISDN PRI, channel-associated signaling, or robbed-bit signaling), and enters interface configuration mode.
Enter the slot number and port number where the channelized E1 or T1 controller is located.
Step 4
nofair-queue
Example:
Router(config-if)# no fair-queue
Disables WFQ (or DWFQ for VIP-enabled routers).
Step 5
encapsulationppp
Example:
Router(config-if)# encapsulation ppp
Sets the serial interface encapsulation method used by the interface.
Step 6
pppmultilink
Example:
Router(config-if)# ppp multilink
Enables Multilink on an interface.
Step 7
pppmultilinkgroupgroup-number
Example:
Router(config-if)# ppp multilink group 1
Restricts a physical link to joining only a designated multilink group interface.
Enter the multilink group number.
Step 8
end
Example:
Router(config-if)# end
(Optional) Exits interface configuration mode.
Verifying the Multilink PPP over Serial Interface Link Configuration
(Optional) Displays the packet statistics of all classes that are configured for all service policies either on the specified interface or subinterface or on a specific permanent virtual circuit (PVC) on the interface.
Step 5
exit
Example:
Router# exit
(Optional) Exits privileged EXEC mode.
Configuration Examples for Using Multilink PPP over Serial Interface Links
Configuring Multilink PPP over Serial Interface Links on a Multilink Group Interface Example
The following is an example of configuring Multilink PPP over serial interface links on a multilink group interface:
Router> enable
Router# configureterminal
Router(config)# interfacemultilink1
Router(config-if)# ip address 10.10.100.1 255.255.255.0
Router(config-if)# service-policyoutputpolicy1
Router(config-if)# service-policyinputpolicy1
Router(config-if)# pppmultilinkfragmentdelay20
Router(config-if)# pppmultilinkinterleave
Router(config-if)# pppmultilinkmulticlass
Router(config-if)# end
Associating the Serial Interface with the Multilink Group Example
The following is an example of associating the serial interface serial4/1 with the multilink group:
Router> enable
Router# configureterminal
Router(config)# interfaceserial4/1:23
Router(config-if)# nofair-queue
Router(config-if)# encapsulationppp
Router(config-if)# pppmultilink
Router(config-if)# pppmultilinkgroup1
Router(config-if)# end
Verifying the Multilink PPP over Serial Interface Link Configuration Example
You can verify the Multilink PPP over serial interface links configuration by using one or more of the following show commands:
showinterfaces
showpppmultilink
showpolicy-mapinterface
The following section provides sample output of the showpppmultilink command only. For sample output of the other commands, see the appropriate Cisco IOS Release 12.3 T command reference publication.
show ppp multilink Command Output Example
The following is an example of the showpppmultilink command output. In this example, one multilink bundle called 7206-2 is on the system. This bundle has two member links: one active link and one inactive link.
Router# show ppp multilink
Multilink2, bundle name is 7206-2
Endpoint discriminator is 7206-2
Bundle up for 00:00:09, 1/255 load
Receive buffer limit 12000 bytes, frag timeout 1500 ms
0/0 fragments/bytes in reassembly list
0 lost fragments, 0 reordered
0/0 discarded fragments/bytes, 0 lost received
0x0 received sequence, 0x3 sent sequence
Member links:1 active, 1 inactive (max not set, min not set)
Se3/2, since 00:00:10, 240 weight, 232 frag size
Se3/3 (inactive)
Where to Go Next
To use Multilink PPP over ATM links, see the "Using Multilink PPP over ATM Links" module.
To use Multilink PPP over Frame Relay, see the "Using Multilink PPP over Frame Relay" module.
To use Multilink PPP over dialer interface links, see the "Using Multilink PPP over Dialer Interface Links" module.
Additional References
The following sections provide references related to Multilink PPP over serial interface links:
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password.
Feature Information for Using Multilink PPP over Serial Interface Links
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to
www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 1 Feature Information for Using Multilink PPP over Serial Interface Links
Feature Name
Software Releases
Feature Configuration Information
Distributed Link Fragmentation and Interleaving Over Leased Lines
12.2(8)T
The Distributed Link Fragmentation and Interleaving over Leased Lines feature extends distributed link fragmentation and interleaving functionality to leased lines.
This feature was extensively rewritten from the perspective of using Multilink PPP for link fragmentation and interleaving over serial interface links.
Distributed Link Fragmentation and Interleaving for Frame Relay and ATM Interfaces on Cisco 7500 Series Routers
12.2(4)T
The Distributed Link Fragmentation and Interleaving (dLFI) for Frame Relay and ATM Interfaces on Cisco 7500 Series Routers feature extends link fragmentation and interleaving functionality to VIP-enabled Cisco 7500 series routers.
This feature was extensively rewritten from the perspective of using Multilink PPP for link fragmentation and interleaving over serial interface links.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at
www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.