The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Multilink PPP is a method used to reduce latency and jitter for real-time traffic. This module contains conceptual information and configuration tasks for using Multilink PPP over Frame Relay.
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.
Only one link per multilink bundle is supported.
Only Voice over IP (VoIP) is supported; Voice over Frame Relay (VoFR) is not supported.
Only one PVC is supported per virtual template.
To handle congestion, a shape policy in an MLP over Frame Relay should be configured via a map class and attached to the PVC.
Before using Multilink PPP over Frame Relay, FRTS must be enabled.
Note |
On the Cisco 7200 and lower series of routers, the frame-relay traffic-shaping command is used to enable FRTS. On the Cisco 7500 and higher series of routers, the Modular Quality of Service (QoS) Command-Line Interface (CLI) (MQC) is used to enable FRTS. For more information about MQC, see the "MQC and Multilink PPP over Frame Relay" section. |
FRTS is a Cisco traffic shaping mechanism. A traffic shaping mechanism allows you to regulate (that is, "shape") the packet flow on a network. When you shape traffic, you control the speed of traffic leaving an interface. This way, you can match the flow of the traffic to the speed of the interface and avoid bottlenecks on the network.
Cisco has long provided support for forward explicit congestion notification (FECN) for DECnet and OSI, and backward explicit congestion notification (BECN) for Systems Network Architecture (SNA) traffic using Logical Link Control, type 2 (LLC2) encapsulation via RFC 1490 and discard eligible (DE) bit support. FRTS builds upon this existing Frame Relay support with additional capabilities that improve the scalability and performance of a Frame Relay network, increasing the density of virtual circuits (VCs) and improving response time.
FRTS can eliminate bottlenecks in Frame Relay networks that have high-speed connections at the central site and low-speed connections at branch sites. You can configure rate enforcement--a peak rate configured to limit outbound traffic--to limit the rate at which data is sent on the VC at the central site.
Before using Multilink PPP over Frame Relay, a policy map must be created. (See the "Prerequisites" section.) Policy maps are created using the Modular Quality of Service (QoS) Command-Line Interface (CLI) (MQC).
A virtual template interface is logical interface configured with generic configuration information for a specific purpose or configuration common to specific users, plus router-dependent information. The template takes the form of a list of Cisco IOS interface commands that are applied to virtual access interfaces, as needed.
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.
While the first two procedures are listed as optional, you must choose one or the other according to the Cisco router that you are using in your network.
These steps apply if you are using the Cisco 7500 series router or the Cisco 7600 series router only. If you are using another series of Cisco router, do not complete these steps. Instead, advance to Configuring Multilink PPP over Frame Relay on a Multilink Group Interface.
Before proceeding with this task, you must create a policy map. The policy map contains the configuration parameters used to apply a specific QoS features such as distributed LLQ (dLLQ) to the network traffic. To create a policy map and configure the appropriate QoS feature, use the MQC. See the MQC and Multilink PPP over Frame Relay.
Command or Action | Purpose | |||
---|---|---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode. |
||
|
Example: Router# configure terminal |
Enters global configuration mode. |
||
|
Example: Router(config)# interface virtual-template 1 |
Creates a virtual template and enters interface configuration mode. |
||
|
Example: Router(config-if)# bandwidth 32 |
Sets the bandwidth value for an interface.
|
||
|
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. |
||
|
Example: Router(config-if)# service-policy output policy1 |
Attaches the previously created QoS traffic policy (policy map). See the "Prerequisites" section on page 4 . The policy map evaluates and applies QoS features for traffic leaving the interface. |
||
|
Example: Router(config-if)# service-policy input policy1 |
Attaches the previously created QoS traffic policy (policy map). See the "Prerequisites" section on page 4 . The policy map evaluates and applies QoS features for traffic entering the interface. |
||
|
Example: Router(config-if)# ppp multilink |
Enables MLP on the interface. |
||
|
Example: 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.
|
||
|
Example: Router(config-if)# ppp multilink interleave |
Enables interleaving of packets among the fragments of larger packets on a multilink bundle. |
||
|
Example: Router(config-if)# end |
(Optional) Exits interface configuration mode. |
If you are using the Cisco 7500 series router or the Cisco 7600 series router, do not complete these steps. Instead, complete the steps in Configuring Multilink PPP over Frame Relay on a Virtual Template Interface.
Before proceeding with this task, you must create a policy map. The policy map contains the configuration parameters used to apply a specific QoS features such as distributed LLQ (dLLQ) to the network traffic. To create a policy map and configure the appropriate QoS feature, use the MQC. See the MQC and Multilink PPP over Frame Relay.
Command or Action | Purpose | |
---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode. |
|
Example: Router# configure terminal |
Enters global configuration mode. |
|
Example: Router(config)# interface multilink 1 |
Creates a multilink bundle and enters interface configuration mode. |
|
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. |
|
Example: Router(config-if)# service-policy output policy1 |
Attaches the previously created QoS traffic policy (policy map). See the "Prerequisites" section on page 6 . The policy map evaluates and applies QoS features for traffic leaving the interface. |
|
Example: Router(config-if)# service-policy input policy1 |
Attaches the previously created QoS traffic policy (policy map). See the "Prerequisites" section on page 6 . The policy map evaluates and applies QoS features for traffic entering the interface. |
|
Example: Router(config-if)# ppp multilink fragment delay 20 |
Specifies a maximum size in units of time for packet fragments on a multilink bundle. |
|
Example: Router(config-if)# ppp multilink interleave |
Enables interleaving of packets among the fragments of larger packets on a multilink bundle. |
|
Example: Router(config-if)# end |
(Optional) Exits interface configuration mode. |
After configuring Multilink PPP over Frame Relay on a multilink group interface, the next step is to associate the virtual template interface with the multilink group by completing the steps in the following section.
If you are using a Cisco 7500 series router or a Cisco 7600 series router, advance to Associating the Virtual Template Interface with a Frame Relay PVC to continue.
Command or Action | Purpose | |
---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode. |
|
Example: Router# show frame-relay pvc |
(Optional) Displays statistics about permanent virtual circuits (PVCs) for Frame Relay interfaces. |
|
Example: Router# show interfaces |
(Optional) Displays statistics for all interfaces configured on the router or access server. |
|
Example: Router# show ppp multilink |
(Optional) Displays bundle information for multilink bundles. |
|
Example: Router# show policy-map interface serial0/0 |
(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 PVC on the interface. |
|
Example: Router# exit |
(Optional) Exits privileged EXEC mode. |
The following is an example of configuring Multilink PPP over Frame Relay on a virtual template interface:
Router> enable
Router# configure terminal
Router(config)# interface virtual-template 1
Router(config-if)# bandwidth 32
Router(config-if)# ip address 10.10.100.1 255.255.255.0
Router(config-if)# service-policy output policy1
Router(config-if)# service-policy input policy1
Router(config-if)# ppp multilink
Router(config-if)# ppp multilink fragment delay 20
Router(config-if)# ppp multilink interleave
Router(config-if)# end
The following is an example of configuring Multilink PPP over Frame Relay on a multilink group interface:
Router> enable
Router# configure terminal
Router(config)# interface multilink 1
Router(config-if)# ip address 10.10.100.1 255.255.255.0
Router(config-if)# service-policy output policy1
Router(config-if)# service-policy input policy1
Router(config-if)# ppp multilink fragment delay 20
Router(config-if)# ppp multilink interleave
Router(config-if)# end
The following is an example of associating the virtual template interface with the multilink group:
Router> enable
Router# configure terminal
Router(config)# interface virtual-template 1
Router(config-if)# no ip address
Router(config-if)# ppp multilink group 1
Router(config-if)# end
The following is an example of associating the virtual template interface with a Frame Relay PVC:
Router> enable
Router# configure terminal
Router(config)# interface serial1/0/0/1:0
Router(config-if)# frame-relay interface-dlci 100 ppp virtual-template1
Router(config-fr-dlci)# class frdlci
Router(config-fr-dlci)# end
You can verify the Multilink with PPP over Frame Relay configuration by using one or more of the following show commands:
The following section provides sample output of the show ppp multilink command only. For sample output of the other commands, see the appropriate Cisco IOS Release 12.3T command reference publication.
The following is an example of the show ppp multilink 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
Multilink1, bundle name is 7206-2
Endpoint discriminator is 7206-2
Bundle up for 00:00:15, 1/255 load
Receive buffer limit 12000 bytes, frag timeout 3428 ms
0/0 fragments/bytes in reassembly list
1 lost fragments, 1 reordered
0/0 discarded fragments/bytes, 0 lost received
0x3 received sequence, 0x3 sent sequence
Member links:1 active, 1 inactive (max not set, min not set)
Vi2, since 00:00:15, 105 weight, 93 frag size
Vt1 (inactive)
To use Multilink PPP over ATM links, see the "Using Multilink PPP over ATM Links" module.
To use Multilink PPP over dialer interface links, see the "Using Multilink PPP over Dialer Interface Links" module.
To use Multilink PPP over serial interface links, see the "Using Multilink PPP over Serial Interface Links" module.
The following sections provide references related to using Multilink PPP over Frame Relay.
Related Topic |
Document Title |
---|---|
QoS commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples |
Cisco IOS Quality of Service Solutions Command Reference |
LLQ, WFQ, CBWFQ, PQ, CQ, FIFO and other queueing mechanisms |
"Configuring Weighted Fair Queueing" module |
MQC |
"Applying QoS Features Using the MQC" module |
FRTS |
"MQC-Based Frame Relay Traffic Shaping" module |
Multilink PPP configurations |
"Configuring Media-Independent PPP and Multilink PPP" module |
Virtual template interfaces |
"Configuring Virtual Template Interfaces" module |
Multilink PPP overview module |
"Reducing Latency and Jitter for Real-Time Traffic Using Multilink PPP" module |
Multilink PPP over ATM links (including ATM interfaces and ATM PVCs) |
"Using Multilink PPP over ATM Links" module |
Multilink PPP over dialer interface links |
"Using Multilink PPP over Dialer Interface Links" module |
Multilink PPP over serial interface links |
"Using Multilink PPP over Serial Interface Links" module |
Standard |
Title |
---|---|
No new or modified standards are supported, and support for existing standards has not been modified. |
-- |
MIB |
MIBs Link |
---|---|
No new or modified MIBs are supported, and support for existing MIBs has not been modified.
|
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFC |
Title |
---|---|
RFC 1990 |
The PPP Multilink Protocol (MP) |
RFC 2686 |
Multiclass Extension to Multilink PPP (MCML) |
Description |
Link |
---|---|
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. |
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 Frame Relay |
Feature Name |
Software Releases |
Feature Configuration Information |
---|---|---|
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 Frame Relay. |
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 Frame Relay. |
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: 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. (1110R)
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.