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.
Prerequisites for Using Multilink PPP over Dialer Interface Links
Be familiar with the concepts in the "Reducing Latency and Jitter for Real-Time Traffic Using Multilink PPP" module.
Multilink uses first-in first out (FIFO) queuing for queuing and interleaving packets. Other queuing mechanisms such as low latency queuing (LLQ), weighted fair queuing (WFQ), and class-based weighted fair queuing (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 Dialer Interface Links
Route/switch processing (RSP) is not recommended when using Multilink PPP over dialer interface links.
Information About Using Multilink PPP over Dialer Interface Links
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:
When you want to share an interface (ISDN, asynchronous, or synchronous serial) to place or receive calls.
When you want to change any configuration on a per-user basis.
When you want to maximize ISDN channel usage using the Dynamic Multiple Encapsulations feature to configure various encapsulation types and per-user configurations on the same ISDN B channel at different times according to the type of call.
When you want to bridge to many destinations, and for avoiding split horizon problems.
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.
MQC and Multilink PPP over Dialer Interface Links
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.
How to Configure Multilink PPP over Dialer Interface Links
Configuring Multilink PPP over Dialer Interface Links
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 Dialer Interface Links.
Defines a dialer rotary group and enters interface configuration mode.
Enter the dialer rotary group 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
ipunnumberedtypenumber
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.
Enter the type and number of another interface on which the router has an assigned IP address. It cannot be another unnumbered interface.
Step 6
encapsulationencapsulation-type
Example:
Router(config-if)# encapsulation ppp
Sets the encapsulation method used by the interface.
Enter the encapsulation method. For this feature, enter ppp.
Step 7
dialerpoolnumber
Example:
Router(config-if)# dialer pool 3
(Optional) Specifies which dialing pool to use to connect to a specific destination subnetwork.
Enter the dialing pool number.
Step 8
dialerin-band [no-parity | odd-parity]
Example:
Router(config-if)# dialer in-band
(Optional) Specifies that dial-on-demand routing (DDR) is to be supported.
Step 9
service-policyoutputpolicy-map-name
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.
Enter the policy map name.
Step 10
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.
Enables at least one Point-to-Point Protocol (PPP) authentication protocol and specifies the order in which the protocols are selected on the interface.
Enter the PPP authentication protocol to be used.
Step 12
pppchaphostnamehostname
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).
Enter the name sent in the CHAP challenge.
Step 13
pppchappasswordsecret
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.
Enter the secret password used to compute the response value for any CHAP challenge from an unknown peer.
Example Configuring Multilink PPP over Dialer Interface Links
The following is an example of configuring Multilink PPP over a dialer interface link:
Router> enable
Router# configureterminal
Router(config)# interfacedialer1
Router(config-if)# ip address 10.10.100.1 255.255.255.0
Router(config-if)# encapsulationppp
Router(config-if)# dialerpool3
Router(config-if)# service-policyoutputpolicy1
Router(config-if)# service-policyinputpolicy1
Router(config-if)# pppauthenticationchap
Router(config-if)# pppchaphostnameISPCorp
Router(config-if)# pppchappassword7
Router(config-if)# pppmultilink
Router(config-if)# pppmultilinkfragmentdelay20
Router(config-if)# pppmultilinkinterleave
Router(config-if)# end
Example Associating the Dialer Interface with a BRI
The following is an example of associating the dialer interface with a BRI:
Router> enable
Router# configureterminal
Router(config)# interfacebri1
Router(config-if)# dialerpool-member3
Router(config-if)# pppmultilink
Router(config-if)# end
Example Verifying the Multilink PPP over Dialer Interface Link Configuration
You can verify the Multilink PPP over dialer interface link configuration by using one or more of the following show commands:
showinterfaces
showpppmultilink
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 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
Where to Go Next
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.
Additional References
The following sections provide references related to Multilink PPP over dialer 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 Dialer 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 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 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.