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.
This module contains conceptual information and configuration tasks for using Multilink PPP over dialer 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.
The dialer profiles implementation of dial-on-demand routing (DDR) is based on a separation between logical and physical interface configuration. Dialer profiles also allow the logical and physical configurations to be bound together dynamically on a per-call basis.
Dialer profiles are advantageous in the following situations:
Most routed protocols are supported; however, International Organization for Standardization Connectionless Network Service (ISO CLNS) is not supported.
If you decide to configure dialer profiles, you must disable validation of source addresses for the routed protocols you support.
Before using Multilink PPP over dialer 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 policies (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.
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 Dialer Interface Links.
Command or Action | Purpose | |
---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode.
|
|
Example: Router# configure terminal |
Enters global configuration mode. |
|
Example: Router(config)# interface dialer 1 |
Defines a dialer rotary group 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)# ip unnumbered ethernet 0 |
(Optional) Enables IP processing on a serial interface without assigning an explicit IP address to the interface.
|
|
Example: Router(config-if)# encapsulation ppp |
Sets the encapsulation method used by the interface.
|
|
Example: Router(config-if)# dialer pool 3 |
(Optional) Specifies which dialing pool to use to connect to a specific destination subnetwork.
|
|
Example: Router(config-if)# dialer in-band |
(Optional) Specifies that dial-on-demand routing (DDR) is to be supported. |
|
Example: Router(config-if)# service-policy output policy1 |
Attaches the previously created QoS traffic policy (policy map). 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 3 . The policy map evaluates and applies QoS features for traffic enteringthe interface.
|
|
Example: Router(config-if)# ppp authentication chap |
Enables at least one Point-to-Point Protocol (PPP) authentication protocol and specifies the order in which the protocols are selected on the interface.
|
|
Example: Router(config-if)# ppp chap hostname ISPCorp |
Creates a pool of dialup routers that all appear to be the same host when authenticating with Challenge Handshake Authentication Protocol (CHAP).
|
|
Example: Router(config-if)# ppp chap password 7 |
Enables a router calling a collection of routers that do not support this command (such as routers running older Cisco IOS software images) to configure a CHAP secret password to use in response to challenges from an unknown peer.
|
|
Example: Router(config-if)# ppp multilink |
Enables multilink on an 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. |
Command or Action | Purpose | |
---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode.
|
|
Example: Router# configure terminal |
Enters global configuration mode. |
|
Example: Router(config)# interface bri 1 |
Configures a BRI interface and enters interface configuration mode.
|
|
Example: Router(config-if)# dialer pool-member 3 |
(Optional) Configures a physical interface to be a member of a dialer profile dialing pool.
|
|
Example: Router(config-if)# dialer rotary-group 1 |
(Optional) Includes a specified interface in a dialer rotary group.
|
|
Example: Router(config-if)# ppp multilink |
Enables Multilink on an interface. |
|
Example: Router(config-if)# end |
(Optional) Exits interface configuration mode. |
The following is an example of configuring Multilink PPP over a dialer interface link:
Router> enable
Router# configure terminal
Router(config)# interface dialer 1
Router(config-if)# ip address 10.10.100.1 255.255.255.0
Router(config-if)# encapsulation ppp
Router(config-if)# dialer pool 3
Router(config-if)# service-policy output policy1
Router(config-if)# service-policy input policy1
Router(config-if)# ppp authentication chap
Router(config-if)# ppp chap hostname ISPCorp
Router(config-if)# ppp chap password 7
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 associating the dialer interface with a BRI:
Router> enable
Router# configure terminal
Router(config)# interface bri 1
Router(config-if)# dialer pool-member 3
Router(config-if)# ppp multilink
Router(config-if)# end
You can verify the Multilink PPP over dialer interface link 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.3 T 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 one member link.
Router# show ppp multilink
Dialer2, bundle name is 7206-2
Username is 7206-2
Endpoint discriminator is 7206-2
Bundle up for 00:00:10, 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, 0x0 sent sequence
Member links:1 (max not set, min not set)
BR2/0:1, since 00:00:09
To use Multilink PPP over Frame Relay, see the "Using Multilink PPP over Frame Relay" module.
To use Multilink PPP over ATM links, see the "Using Multilink PPP over ATM 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 Multilink PPP over dialer interface links.
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 |
Dialer profiles and DDR |
"Preparing to Configure DDR" module |
Multilink PPP configuration information |
"Configuring Media-Independent PPP and Multilink PPP" module |
Multilink PPP overview module |
"Reducing Latency and Jitter for Real-Time Traffic Using Multilink PPP" module |
Multilink PPP over Frame Relay |
"Using Multilink PPP over Frame Relay" module |
Multilink PPP over ATM links (including ATM interfaces and ATM PVCs) |
"Using Multilink PPP over ATM 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 Dialer 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 dialer 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 dialer interface links. |
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.