-
Cisco IOS Dial Technologies Command Reference, Release 12.3 T
-
Introduction
-
Dial Technologies Commands: A through cas-group
-
Dial Technologies Commands: channel through cpp
-
Dial Technologies Commands: debounce through dial-tdm
-
Dial Technologies Commands: disconnect through group
-
Dial Technologies Commands: initiate through ipx
-
Dial Technologies Commands: isdn through isdn x25
-
Dial Technologies Commands: L
-
Dial Technologies Commands: M
-
Dial Technologies Commands: name through pptp
-
Dial Technologies Commands: pri through rotary
-
Dial Technologies Commands: script through show dial
-
Dial Technologies Commands: show dsc through show line
-
Dial Technologies Commands: show modem through show nbf
-
Dial Technologies Commands: show port through show resource
-
Dial Technologies Commands: show sessions through show vtemplate
-
Dial Technologies Commands: shutdown through x25 map
-
Table Of Contents
dialer idle-timeout (interface)
dialer idle-timeout (template)
dialer string (dialer profiles)
dialer wait-for-carrier-time (interface)
dialer wait-for-carrier-time (map-class)
dial-shelf split backplane-ds0
debounce-time rai
To configure a timer that prevents E1 or STM-1 trunk lines from being torn down in response to brief line outages, use the debounce-time rai command in controller configuration mode. To restore the default timer value, use the no form of this command.
debounce-time rai milliseconds
no debounce-time rai milliseconds
Syntax Description
Command Default
The default value for the timer is used:
•
E1 lines on the AS5800—500 ms
•
•
Command Modes
Controller configuration
Command History
Usage Guidelines
Use the debounce-time rai command to configure a timer that allows Awaiting Info (I) calls to ignore brief trunk outages. When a Receive Alarm Indication (RAI) signal is received, the access server will wait the configured interval before tearing down the line.
Examples
The following example configures an E1 controller to wait for 5250 ms before tearing down an E1 trunk line:
Router(config)# controller e1 1/0/0Router(config-controller)# debounce-time rai 5250Related Commands
controller
Configures a T1, E1, or J1 controller and enters controller configuration mode.
default (VPDN)
To remove or reset a virtual private dialup network (VPDN) group or a VPDN subgroup configuration to its default value, use the default command in VPDN group, VPDN subgroup, or VPDN template configuration mode.
default command
Syntax Description
command
The command to be removed or reset from the VPDN group or VPDN subgroup configuration. Table 5 lists some of the commands that can be issued with the default command.
Command Default
No default behavior or values.
Command Modes
VPDN group configuration
VPDN subgroup configuration
VPDN template configurationCommand History
Usage Guidelines
Use the default command to remove or reset a specific command configuration in a VPDN group, VPDN subgroup, or VPDN template configuration. Issuing default command is the same as issuing the no form of the command specified with the command argument.
Table 5 lists some of the commands that can be removed or reset using the default command, and the configuration modes that the default command must be issued in. Some commands may not be available unless a particular configuration is present on the router.
For a complete list of the commands available for use with the default command, use the default ? command in the desired configuration mode.
Some commands have required keywords or arguments that must be included in the default command statement. You may issue default command ? to determine what keywords and arguments are required. For complete command syntax, see the command documentation in the Cisco IOS Dial Technologies Command Reference.
Examples
The following example shows the running configuration of a tunnel server VPDN group configured to accept Layer 2 Forwarding (L2F) dial-in calls and to place Layer 2 Tunnel Protocol (L2TP) dial-out calls:
Router# show running-config!vpdn-group group1accept-dialinprotocol l2fvirtual-template 1request-dialoutprotocol l2tppool-member 1terminate-from hostname myhostinitiate-to ip 10.3.2.1local name router32l2f ignore-mid-sequencel2tp ip udp checksum!If you issue the default virtual-template command in accept-dialin VPDN subgroup configuration mode, the virtual-template command configuration is removed from the VPDN subgroup:
Router(config-vpdn-req-out)# default virtual-template!Router# show running-config!vpdn-group group1accept-dialinprotocol l2frequest-dialoutprotocol l2tppool-member 1terminate-from hostname myhostinitiate-to ip 10.3.2.1local name router32l2f ignore-mid-sequencel2tp ip udp checksum!If you issue the default accept-dialin command in VPDN group configuration mode, the accept-dialin VPDN subgroup configuration is removed from the VPDN group along with all configurations that require an accept-dialin VPDN subgroup:
Router(config-vpdn)# default accept-dialin!Router# show running-config!vpdn-group group1request dialoutprotocol l2tppool-member 1local name router32initiate-to ip 10.3.2.1l2tp ip udp checksumThe following example enters VPDN template configuration mode and uses the command line help system to find the commands available to use with the default command:
Router(config)# vpdn-template 1Router(config-vpdn-templ)# default ?description Description for this VPDN groupgroup Items grouped for all attached vpdn-groupsip IP settings for tunnell2f L2F specific commandsl2tp L2TP specific commandslocal Local informationpptp PPTP specific commandsredirect Call redirection optionsrelay Relay options configurationvpn VPN ID/VRF nameThe following example uses the command line help system to show that a value must be entered for the number argument when the default session-limit command is issued in VPDN group configuration mode:
Router(config-vpdn)# default session-limit ?<0-32767> Max number of sessionsRelated Commands
description (interface)
To add a description to an interface configuration, use the description command in interface configuration mode. To remove the description, use the no form of this command.
description string
no description
Syntax Description
Defaults
No description is added.
Command Modes
Interface configuration
Command History
Usage Guidelines
The description command is meant solely as a comment to be put in the configuration to help you remember what certain interfaces are used for. The description appears in the output of the following EXEC commands: more nvram:startup-config, show interfaces, and more system:running-config.
Examples
The following example shows how to add a description for a T1 interface:
interface serial 0description Fractional T1 line to Mountain View -- 128 kbpsRelated Commands
description (VPDN group)
To add a description to a virtual private dialup network (VPDN) group, use the description command in VPDN group or VPDN template configuration mode. To remove the description, use the no form of this command.
description string
no description
Syntax Description
Command Default
No description is associated with the VPDN group.
Command Modes
VPDN group configuration
VPDN template configurationCommand History
Examples
The following example shows how to enter a description for a VPDN group:
vpdn-group 333description This is a VPDN group at location 333request-dialinprotocol l2tpdomain cisco2.comexitinitiate-to ip 10.0.0.63local name cisco.comRelated Commands
vpdn-group
Creates a VPDN group and enters VPDN group configuration mode.
vpdn-template
Creates a VPDN template and enters VPDN template configuration mode.
dialer
To specify the dialer interface that an accept-dialout virtual private dialup network (VPDN) subgroup will use to dial out calls, use the dialer command in accept-dialout configuration mode. To remove the dialer interface from the accept-dialout VPDN subgroup, use the no form of this command.
dialer dialer-interface
no dialer
Syntax Description
Defaults
Disabled
Command Modes
Accept-dialout configuration
Command History
Usage Guidelines
You must first enable Layer 2 Tunneling Protocol (L2TP) on the accept-dialout VPDN subgroup by using the protocol l2tp command before you can enable the dialer command. Removing the protocol command will remove the dialer command from the accept-dialout subgroup.
You can only specify one dialer per accept dialout group. Configuring a second dialer command will replace the first dialer command.
Examples
The following example creates an accept-dialout VPDN subgroup that uses dialer interface 2:
VPDN-group 1accept dialoutprotocol l2tpdialer 2terminate-from hostname ceriseRelated Commands
dialer callback-secure
To enable callback security, use the dialer callback-secure command in interface configuration mode. To disable callback security, use the no form of this command.
dialer callback-secure
no dialer callback-secure
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command affects those users that are not authorized to be called back through configuration of the dialer callback-server command. If the username (the host-name argument in the dialer map command) is not authorized for callback, the call will be disconnected if the dialer callback-secure command is configured.
Examples
The following partial example configures BRI0 with the commands required to make it function as the callback server on the shared network. Callback security is enabled on BRI0, such that any user other than user1 will be disconnected and not called back.
interface BRI0ip address 172.19.1.9 255.255.255.0encapsulation pppdialer callback-securedialer enable-timeout 2dialer map ip 172.19.1.8 name user1 class dial1 81012345678901dialer-group 1ppp callback acceptppp authentication chap!map-class dialer dial1dialer callback-server usernameRelated Commands
dialer callback-server
To enable an interface to make return calls when callback is successfully negotiated, use the dialer callback-server command in interface configuration mode. To disable return calls, use the no form of this command.
dialer callback-server [username | dialstring]
no dialer callback-server
Syntax Description
username
(Optional) Looks up the authenticated host name in a dialer map command. This is the default.
dialstring
(Optional) Identifies the return call during callback negotiation.
Defaults
Disabled. The default keyword is username.
Command Modes
Interface configuration
Command History
Examples
The following partial example configures BRI 0 to function as the callback server on the shared network:
interface BRI0ip address 172.19.1.9 255.255.255.0encapsulation pppdialer callback-securedialer enable-timeout 2dialer map ip 172.19.1.8 name atlanta class dial1 81012345678901dialer-group 1ppp callback acceptppp authentication chap!map-class dialer dial1dialer callback-server usernameRelated Commands
dialer called
To configure dial-on-demand routing (DDR) to perform DNIS-plus-ISDN-subaddress binding for dialer profile interfaces, use the dialer called command in dial-on-demand routing configuration mode. To disable DNIS-plus-ISDN-subaddress binding, use the no form of this command.
dialer called DNIS:subaddress
no dialer called DNIS:subaddress
Syntax Description
DNIS:subaddress
Dialed Number Identification Service or the called party number, a colon, and the ISDN subaddress.
Defaults
No default behavior or values.
Command Modes
Dial-on-demand routing configuration
Command History
Usage Guidelines
If you have more than one DNIS-plus-ISDN-subaddress number to configure under the same dialer profile interface, you can configure multiple dialer called commands.
The parser accepts a dialer called command with a DNIS and without the subaddress; however, the call will fail. For a successful call, enter the DNIS, a colon, and the ISDN subaddress after the dialer called command.
Examples
The following example configures a dialer profile for a receiver with DNIS 12345 and ISDN subaddress 6789:
dialer called 12345:6789Related Commands
dialer caller
Configures caller ID screening and, optionally, enables ISDN caller ID callback for legacy DDR or the dialer profiles DDR feature.
dialer caller
To configure caller ID screening for a dialer rotary group interface or to bind an incoming call to a particular dialer profile, and, optionally, to enable ISDN caller ID callback, use the dialer caller command in interface configuration mode. To disable this feature, use the no form of this command.
dialer caller number [callback]
no dialer caller number [callback]
Syntax Description
Defaults
Caller ID screening, call binding, and ISDN caller ID callback are disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
On a dialer rotary group interface, this command configures the Cisco IOS software to accept calls from the specified number or, used with the callback keyword, to reject incoming calls from the specified number but to initiate callback to the number.
When the optional callback keyword is used, the initial call is rejected (hence, not subject to tolls) and callback is initiated to the calling number.
When x's are used in the callback number, dialer caller screening is based on a best match system that uses the number of x's as a criterion. To make callback calls only to specified numbers or ranges of numbers but to accept any other incoming calls, make sure that the number of x's in any configuration line that uses the callback keyword is less than the number of x's in any configuration line that does not use the keyword.
For example, if you use at most four x's in the configuration lines with the callback keyword, then to accept calls from other numbers use at least five x's in a configuration line that does not use the callback keyword.
Note
For dialer profiles, this command helps bind a dialer profile to—and thus configure—the interface used for a call. The dialer command acts as a binding command by associating an incoming call with a specified dialer profile if the caller ID presented by the call matches the dialer caller value.
Note
Examples
In the following example, callback calls will be made only to numbers in the 555 and 556 exchanges, but any other number can call in:
dialer caller 408555xxxx callbackdialer caller 408556xxxx callbackdialer caller xxxxxRelated Commands
dialer clid group
To create a Calling Line Identification (CLID) group in the resource pool and assign it a name, use the dialer clid group command in global configuration mode. To remove a CLID group from the resource pool, use the no form of this command.
dialer clid group clid-group-name
no dialer clid group clid-group-name
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the dialer clid group command to create a CLID group and assign it a name. The CLID group name must be the same as the name used when configuring the customer profile.
Customer profiles are configured with a DNIS and/or CLID group and call type. The DNIS and/or CLID and call type of the incoming call is used to find the appropriate customer profile.
Examples
The following example shows the command to configure a CLID group named "zot." After you enter this command, the router prompt changes to the CLID configuration mode, Router(config-clid-group)#.
Router(config)# dialer clid group zotRelated Commands
number
Adds a DNIS number to a dialer DNIS group.
resource-pool call treatment discriminator
Configures a CLID group in a discriminator.
dialer congestion-threshold
To specify congestion threshold in connected links, use the dialer congestion-threshold command in interface configuration mode. To disable this function, use the no form of this command.
dialer congestion-threshold links
no dialer congestion-threshold
Syntax Description
Defaults
The default number of connected links is 64,000.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is used to force the dialer to search for another uncongested system (the alternate network access server) in a stack group to dial out using Stack Group Bidding Protocol (SGBP).
Examples
The following example sets the congestion threshold to five connected links on the Dialer interface 0:
interface Dialer0dialer aaadialer congestion-threshold 5Related Commands
dialer reserved-links
Reserves links for dial-in and dial-out.
sgbp dial-bids
Allows the stack group to bid for dial-out connection.
dialer dnis group
To create a DNIS group, use the dialer dnis group command in global configuration mode. To remove a specific Dialed Number Identification Service (DNIS) group from the running configuration, use the no form of this command.
dialer dnis group name
no dialer dnis group name
Syntax Description
Defaults
A dialer DNIS group named default.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the dialer dnis group global configuration command to create a DNIS group. This command enables you to create and populate a DNIS group, which is then added to a profile (customer or discriminator) by using the dnis group command within that profile's configuration mode.
Examples
The following example shows a specific DNIS group named modem-group1 being created with the options available for further configuration:
dialer dnis group modem-group1Dialer Called Configuration Commands:call-type set call-type overridedefault Set a command to its defaultsexit Exit from dialer configuration modehelp Description of the interactive help systemno Negate a command or set its defaultsnumber Enter number in dnis groupIn the following example, a customer profile called isp_1 is created, a DNIS group called dnis_isp_1 is associated with the customer profile, and DNIS numbers 1234 and 5678 are assigned to the DNIS group. Only DNIS numbers 1234 and 5678 are allocated physical resources by the isp_1 customer profile, which counts and manages the resources for these two DNIS numbers and ignores all other DNIS numbers:
resource-pool profile customer isp_1dnis group dnis_isp_1 exitdialer dnis group dnis_isp_1number 1234number 5678Related Commands
dnis group
Includes a group of DNIS numbers in a customer profile.
resource-pool profile
Creates a resource group for RPM.
dialer dns
To obtain a user profile name on a remote network using reverse Domain Name System (DNS), use the dialer dns command in interface configuration mode. To disable this function, use the no form of this command.
dialer dns
no dialer dns
Syntax Description
This command has no arguments or keywords.
Defaults
The reverse DNS function is disabled by default.
Command Modes
Interface configuration of a dialer rotary group leader
Command History
Usage Guidelines
This command allows the dialer to use reverse DNS to get a profile name for accessing the authentication, authorization, and accounting (AAA) server. This command is not required when using named static routes.
Examples
The following example shows how to allow the dialer to use reverse DNS for name lookup:
interface dialer 0dialer aaadialer dnsRelated Commands
dialer dtr
To enable dial-on-demand routing (DDR) on an interface and specify that the serial line is connected by non-V.25bis modems using Electronic Industries Association (EIA) signaling only—specifically, the data terminal ready (DTR) signal—use the dialer dtr command in interface configuration mode. To disable DDR for the interface, use the no form of this command.
dialer dtr
no dialer dtr
Syntax Description
This command has no arguments or keywords.
Defaults
DTR dialing is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
A serial interface configured for DTR dialing can place calls only; it cannot accept them.
When a local interface is configured for DTR dialing, the remote interface (that will be receiving the calls) can be configured for in-band dialing or not configured for anything but encapsulation, depending on the desired behavior. If the remote interface is expected to terminate a call when no traffic is transmitted for some time, it must be configured for in-band dialing (along with access lists and a dummy dialer string). If the remote interface is purely passive, no configuration is necessary.
Rotary groups cannot be configured for DTR dialing.
The dialer map and dialer string commands have no effect on DTR dialers.
Examples
The following example enables DDR and specifies DTR dialing on an interface:
Router(config-if)# dialer dtrRelated Commands
dialer enable-timeout
To set the length of time an interface stays down after a call has completed or failed and before it is available to dial again, use the dialer enable-timeout command in interface configuration mode. To return to the default value, use the no form of this command.
dialer enable-timeout seconds
no dialer enable-timeout
Syntax Description
Defaults
15 seconds
Command Modes
Interface configuration
Command History
Usage Guidelines
The dialer enable-timeout command can be configured as a line down timer, to keep asynchronous interface lines down for a certain period of time, and as a callback timer for both synchronous and asynchronous interfaces.
If your phone lines are often busy or down, you may need to enforce a certain period of time before the system repeats an attempt to make a connection with a remote site. Configuring this timeout can prevent outgoing lines and switching equipment from being needlessly overloaded. In this application, the dialer enable-timeout command applies to both inbound and outbound calls on asynchronous interfaces only.
When the dialer enable-timeout command is configured on an ISDN interface, its only effect is to set a callback timer, because it is not possible (nor advisable) to keep an ISDN interface disconnected.
Examples
The following example shows how to specify a timeout period of 30 seconds on asynchronous interface 1 before attempting another connection:
interface async 1dialer enable-timeout 30The following example shows how to configure a BRI interface for legacy dial-on-demand routing (DDR) and ISDN caller ID callback:
interface bri 0description Connected to NTT 81012345678901ip address 10.1.1.7 255.255.255.0no ip mroute-cacheencapsulation pppisdn caller 81012345678902 callbackdialer enable-timeout 2dialer map ip 10.1.1.8 name spanky 81012345678902dialer-group 1ppp authentication chapThe following examples show how to configure a PPP callback server and client.
PPP Callback Server
The PPP callback server is configured on an ISDN BRI interface and requires an enable timeout period and a map class to be defined.
interface bri 0ip address 10.1.1.7 255.255.255.0encapsulation pppdialer callback-securedialer enable-timeout 2dialer map ip 10.1.1.8 name atlanta class dial1 81012345678901dialer-group 1ppp callback acceptppp authentication chapPPP Callback Client
The PPP callback client is also configured on an ISDN BRI interface, but does not require an enable timeout period or a map class to be defined.
map-class dialer dial1dialer callback-server usernameinterface bri 0ip address 10.1.1.8 255.255.255.0encapsulation pppdialer map ip 10.1.1.7 name dallas 81012345678902dialer-group 1ppp callback requestppp authentication chapdialer fast-idle (interface)
To specify the amount of time that a line for which there is contention will stay idle before it is disconnected and the competing call is placed, use the dialer fast-idle command in interface configuration mode. To return to the default value, use the no form of this command.
dialer fast-idle seconds
no dialer fast-idle
Syntax Description
seconds
Idle time, in seconds, that must occur on an interface before the line is disconnected. Acceptable values are positive, nonzero integers.
Defaults
20 seconds
Command Modes
Interface configuration
Command History
Usage Guidelines
The dialer fast idle timer is activated if there is contention for a line. The dialer fast idle timer is activated if a line is busy, a packet for a different next hop address is received, and the busy line is required to send the competing packet.
If the line becomes idle for configured length of time, the current call is disconnected immediately and the new call is placed.
If the line has not yet been idle as long as the fast idle timeout period, the packet is dropped because there is no way to get through to the destination. After the packet is dropped, the fast idle timer remains active and the current call is disconnected as soon as it has been idle for as long as the fast idle timeout.
The fast idle timer will be restarted if, in the meanwhile, another packet is transmitted to the currently connected destination and it is classified as interesting.
This command applies to inbound and outbound calls.
Combining this command with the dialer idle-timeout command allows you to configure lines to stay up for a longer period of time when there is no contention, but to be reused more quickly when there are not enough lines for the current demand.
Examples
The following example specifies a fast idle timeout of 35 seconds on asynchronous interface 1:
interface async 1dialer fast-idle 35Related Commands
dialer fast-idle (map-class)
To specify the fast idle timer value to use when placing a call to any telephone number associated with a specified class, use the dialer fast-idle command in map-class dialer configuration mode. To reset the dialer fast-idle timer to the default, use the no form of this command.
dialer fast-idle seconds
no dialer fast-idle
Syntax Description
Defaults
Defaults to the fast idle timer value that is set for the interface.
Command Modes
Map-class dialer configuration
Command History
Usage Guidelines
This fast idle timer is associated only with the map class, not the entire interface.
Examples
The following example specifies a dialer fast idle time of 10 seconds:
dialer string 4156884540 class Eng! This map-class ensures that these calls use an ISDN speed of 56 kbps and a! fast-idle time of 10 seconds.map-class dialer Engisdn speed 56dialer fast-idle 10dialer wait-for-carrier-time 30Related Commands
dialer-group
To control access by configuring an interface to belong to a specific dialing group, use the dialer-group command in interface configuration mode. To remove an interface from the specified dialer access group, use the no form of this command.
dialer-group group-number
no dialer-group
Syntax Description
Defaults
No access is predefined.
Command Modes
Interface configuration
Command History
Usage Guidelines
An interface can be associated with a single dialer access group only; multiple dialer-group assignment is not allowed. A second dialer access group assignment will override the first. A dialer access group is defined with the dialer-group command. The dialer-list command associates an access list with a dialer access group.
Packets that match the dialer group specified trigger a connection request.
Examples
The following example specifies dialer access group number 1.
The destination address of the packet is evaluated against the access list specified in the associated dialer-list command. If it passes, either a call is initiated (if no connection has already been established) or the idle timer is reset (if a call is currently connected).
interface async 1dialer-group 1access-list 101 deny igrp 0.0.0.0 255.255.255.255 255.255.255.255 0.0.0.0access-list 101 permit ip 0.0.0.0 255.255.255.255 0.0.0.0 255.255.255.255dialer-list 1 protocol ip list 101Related Commands
dialer-list protocol (Dial)
Defines a DDR dialer list to control dialing by protocol or by a combination of protocol and an access list.
dialer-group (template)
To control access by configuring a virtual access interface to belong to a specific dialing group, use the dialer-group command in template configuration mode. To remove an interface from the specified dialer access group, use the no form of this command.
dialer-group dialer-list-number
no dialer-group
Syntax Description
Defaults
No access is predefined.
Command Modes
Template configuration
Command History
Usage Guidelines
An interface can be associated with only a single dialer access group; multiple dialer-group assignment is not allowed. A second dialer access group assignment will override the first. A dialer access group is defined with the dialer-group template configuration command. The dialer-list command associates an access list with a dialer access group. For Cisco IOS Release 12.2(4)T, the number of dialer groups that can be configured was increased from 10 to 128.
Packets that match the dialer group specified trigger a connection request.
Examples
The following example specifies dialer access group number 1. The destination address of the packet is evaluated against the access list specified in the associated dialer-list command. If it passes, either a call is initiated (if no connection has already been established) or the idle timer is reset (if a call is currently connected).
template template1dialer-group 1Related Commands
dialer-list protocol
Defines a dialer list to control dialing by protocol or by a combination of protocol and an access list.
dialer hold-queue
To allow interesting outgoing packets to be queued until a modem connection is established, use the dialer hold-queue command in interface configuration mode. To disable the hold queue, use the no form of this command.
dialer hold-queue packets timeout seconds
no dialer hold-queue [packets]
Syntax Description
Defaults
The outgoing packet queue is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
A dialer hold queue can be configured on any type of dialer, including in-band synchronous, asynchronous, data terminal ready (DTR), and ISDN dialers. Rotary groups can be configured with a dialer hold queue. If a rotary group is configured with a hold queue, all members of the group will be configured with a dialer hold queue and no individual member's hold queue can be altered.
If no hold queue is configured, packets are dropped during the time required to establish a connection. Setting packets to 0 using the dialer hold-queue command is equivalent to using the no dialer hold-queue command.
Examples
The following command configures a dialer hold queue to hold 10 packets:
Router(config-if)# dialer hold-queue 10 timeout 60Related Commands
dialer-group
Controls access by configuring an interface to belong to a specific dialing group.
dialer idle-timeout (interface)
To specify the duration of idle time before a line is disconnected, use the dialer idle-timeout command in interface configuration mode. To reset the idle timeout to the default, use the no form of this command.
dialer idle-timeout seconds [inbound | either]
no dialer idle-timeout
Syntax Description
Defaults
Direction: outbound
Idle time: 120 seconds
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
12.1(1)T
The following keywords were added:
•
•
Usage Guidelines
This command is used on lines for which there is no contention. When contention occurs, the dialer fast-idle command is activated. For example, when a busy line is requested to send another packet to a different destination than it is currently connected to, line contention occurs and the dialer fast-idle command is activated.
By default, this command applies to inbound and outbound calls. For example, if a receiving system needs to make outgoing calls, you might configure it with a short idle timeout.
Only packets that match the dialer group reset the idle timer.
Use the dialer idle-timeout command to set a very high idle timer when Multilink PPP is configured and you want a multilink bundle to be connected indefinitely. (The dialer-load threshold 1 command no longer keeps a multilink bundle of n links connected indefinitely and the dialer-load threshold command no longer keeps a multilink bundle of two links connected indefinitely.)
Examples
The following example specifies an idle timeout of 3 minutes (180 seconds) on asynchronous interface 1. Because the inbound keyword is included, only inbound traffic that matches the dialer group will reset the idle timer.
interface async 1dialer idle-timeout 180 inboundRelated Commands
dialer idle-timeout (template)
To set the dialer idle timeout period in a virtual template interface, use the dialer idle-timeout command in template configuration mode. To change the dialer idle timeout, use the no form of this command.
dialer idle-timeout seconds [inbound | either]
no dialer idle-timeout seconds [inbound | either]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Template configuration
Command History
Usage Guidelines
The dialer idle-timeout command allows the dialer idle timeout period to be specified in an RPM customer profile and applied on a per-dialed number identification service (DNIS) basis. The dialer idle timer configuration set in this command will override dialer idle timer configurations for dialer, group asynchronous, and virtual template interfaces, unless a per-user configuration is received from an authentication, authorization, and accounting (AAA) per-user interface configuration. In this case, the settings from the AAA per-user interface configuration take precedence over the local interface configuration.
The dialer idle-timeout command works well with Multilink PPP (MLP) and Multichassis Multilink PPP (MMP) when the master bundle interface is not a virtual access (projected) interface. For virtual access interfaces where the dialer idle timer cannot be used, you can classify traffic that resets the PPP idle timer using the ip idle-group commands.
Examples
The following example sets the idle timeout period in an RPM customer profile template to 45 seconds:
template template 1dialer idle-timeout 45The following example sets the idle timeout period in an RPM customer profile template to 60 seconds and resets the idle timer based on either inbound or outbound traffic:
template template 1dialer idle-timeout 60 eitherThe following example sets the idle timeout period in an RPM customer profile template to 100 seconds and resets the idle timer based only on inbound traffic:
template template 1dialer idle-timeout 100 inboundRelated Commands
dialer in-band
To specify that dial-on-demand routing (DDR) is to be supported, use the dialer in-band command in interface configuration mode. To disable DDR for the interface, use the no form of this command.
dialer in-band [no-parity | odd-parity]
no dialer in-band
Syntax Description
Defaults
Disabled. By default, no parity is applied to the dialer string.
Command Modes
Interface configuration
Command History
Usage Guidelines
The dialer in-band command specifies that chat scripts will be used on asynchronous interfaces and V.25bis will be used on synchronous interfaces. The parity keywords do not apply to asynchronous interfaces. The parity setting applies to the dialer string that is sent out to the modem. If you do not specify a parity, or if you specify no parity, no parity is applied to the output number. If odd parity is configured, the dialed number will have odd parity (7-bit ASCII characters with the eighth bit as the parity bit.) If an interface only accepts calls and does not place calls, the dialer in-band interface configuration command is the only command needed to configure it. If an interface is configured in this manner, with no dialer rotary groups, the idle timer never disconnects the line. It is up to the remote end (the end that placed the call) to disconnect the line based on idle time.
Examples
The following example specifies DDR for asynchronous interface 1:
interface async 1dialer in-bandRelated Commands
dialer isdn
To specify the bit rate used on the B channel associated with a specified map class and to specify whether to set up semipermanent connections for this map class, use the dialer isdn command in map-class dialer configuration mode. To remove the speed and connection settings, use the no form of this command.
dialer isdn [speed speed] [spc]
no dialer isdn [speed speed] [spc]
Syntax Description
Defaults
Bit rate is 64 kbps. Semipermanent connections are not set up.
Command Modes
Map-class dialer configuration
Command History
Usage Guidelines
This command is valid for ISDN interfaces only.
Examples
The following example configures a speed of 56 kbps and no semipermanent connections for the Eng map class:
dialer string 4156884540 class Eng! This map-class ensures that these calls use an ISDN speed of 56 kbps and that! no semipermanent connection is set up.map-class dialer Engdialer isdn speed 56Related Commands
dialer wait-for-carrier-time (map-class)
Specifies the length of time to wait for a carrier when dialing out to the dial string associated with a specified map class.
dialer isdn short-hold
To configure the router to disconnect a call at the end of the current charging period if the line has been idle for at least the specified minimum period, use the dialer isdn short-hold command in map-class dialer configuration mode. To reset the ISDN short-hold timer to the default period, use the no form of this command.
dialer isdn short-hold seconds
no dialer isdn short-hold
Syntax Description
Defaults
Disabled; the router uses a static idle timeout. When this command is enabled, the default short-hold timeout is 120 seconds.
Command Modes
Map-class dialer configuration
Command History
Usage Guidelines
This command is used for configuring ISDN Advice of Charge (AOC) on Cisco routers.
Use the dialer isdn short-hold command if you subscribe to an ISDN AOC during-call service provided by the local ISDN network and want to use this option. The router uses the frequency at which the network sends the AOC-D message to determine the charging period. If the line has been idle for the short-hold timeout, the call disconnects at the end of the charging period. If the line has not been idle for at least that long, the call is maintained into the next charging period.
Examples
The following partial example configures the dialer map class Deutschland with a static idle timeout for outgoing calls. The static idle timer is to be used if for any reason the network does not provide charging information. It also configures a short-hold timeout to allow the router to determine dynamically whether to disconnect or continue the call at the end of the charging period.
dialer map-class Deutschlanddialer idle-timeout 150dialer isdn short-hold 120Related Commands
dialer-list protocol (Dial)
To define a dial-on-demand routing (DDR) dialer list for dialing by protocol or by a combination of a protocol and a previously defined access list, use the dialer-list protocol command in global configuration mode. To delete a dialer list, use the no form of this command.
dialer-list dialer-group protocol protocol-name {permit | deny | list access-list-number | access-group}
no dialer-list dialer-group [protocol protocol-name [list access-list-number | access-group]]
Syntax Description
dialer-group
Number of a dialer access group identified in any dialer-group interface or template configuration command. Up to 128 dialer groups can be configured.
protocol-name
One of the following protocol keywords: appletalk, bridge, clns, clns_es, clns_is, decnet, decnet_router-L1, decnet_router-L2, decnet_node, ip, ipx, or ipv6.
permit
Permits access to an entire protocol.
deny
Denies access to an entire protocol.
list
Specifies that an access list will be used for defining a granularity finer than an entire protocol.
access-list-number
Access list numbers specified in any DECnet, IP, or Novell IPX standard or extended access lists, including Novell IPX extended service access point (SAP) access lists and bridging types. See Table 6 for the supported access list types and numbers.
access-group
Filter list name used in the clns filter-set and clns access-group commands.
Defaults
No dialer lists are defined.
Command Modes
Global configuration
Command History
Usage Guidelines
The various no forms of this command have the following effects:
•
•
•
The dialer-list protocol command permits or denies access to an entire protocol.
The dialer-list protocol command with the optional list keyword provides finer permission granularity and also supports protocols that were not previously supported. This command also applies protocol access lists to dialer access groups to control dialing using DDR. The dialer access groups are defined with the dialer-group command.
Table 6 lists the access list types and numbers that the dialer-list protocol command supports. The table does not include International Organization for Standardization Connectionless Network Service (ISO CLNS) because that protocol uses filter names instead of predefined access list numbers.
Examples
Dialing occurs when an interesting packet (one that matches access list specifications) needs to be output on an interface. Using the standard access list method, packets can be classified as interesting or uninteresting. The following example classifies all other IP packets as interesting and permits them to initiate calls:
access-list 101 permit ip 10.0.0.0 255.255.255.255 10.0.0.0 255.255.255.255Then the following command places list 101 into dialer access group 1:
dialer-list 1 protocol ip list 101In the following example, DECnet access lists allow any DECnet packets with source area 10 and destination area 20 to trigger calls:
access-list 301 permit 10.0 0.1023 10.0 0.1023access-list 301 permit 10.0 0.1023 20.0 0.1023Then the following command places access list 301 into dialer access group 1:
dialer-list 1 protocol decnet list 301In the following example, a CLNS filter is defined and then the filter is placed in dialer access group 1:
clns filter-set ddrline permit 47.0004.0001....!dialer-list 1 protocol clns list ddrlineThe following example configures an IPv6 access list named list2 and places the access list in dialer access group 1:
ipv6 access-list list2 deny fec0:0:0:2::/64 anyipv6 access-list list2 permit any any!dialer-list 1 protocol ipv6 list list2Related Commands
dialer load-threshold
To configure bandwidth on demand by setting the maximum load before the dialer places another call to a destination, use the dialer load-threshold command in interface configuration mode. To disable the setting, use the no form of this command.
dialer load-threshold load [outbound | inbound | either]
no dialer load-threshold
Syntax Description
Defaults
No maximum load is predefined.
Command Modes
Interface configuration
Command History
Usage Guidelines
When the cumulative load of all UP links (a number n) exceeds the load threshold the dialer adds an extra link and when the cumulative load of all UP links minus one (n - 1) is at or below load threshold then the dialer can bring down that one link. The dialer will make additional calls or drop links as necessary but will never interrupt an existing call to another destination.
The load argument is the calculated weighted average load value for the interface; 1 is unloaded and 255 is fully loaded. The load is calculated by the system dynamically, based on bandwidth. You can set the bandwidth for an interface in kilobits per second, using the bandwidth command.
The load calculation determines how much of the total bandwidth you are using. A load value of 255 means that you are using one hundred percent of the bandwidth. The load number is required.
See the description of the bandwidth command earlier in this guide for more information.
When multilink PPP is configured, the dialer load-threshold 1 command no longer keeps a multilink bundle of n links connected indefinitely and the dialer-load threshold 2 command no longer keeps a multilink bundle of 2 links connected indefinitely. If you want a multilink bundle to be connected indefinitely, you must set a high idle timer or make all traffic interesting.
When two connected routers are configured to dial out, only one router should have the dialer max-call or dialer pool-member max-links command configured. Otherwise, if both routers dial simultaneously, each will reject the incoming call when it exceeds the setting for the max-links argument. If the maximum number of calls configured is one and dialing out is synchronized, no connection will come up or it will take many retries before the connection stays up. To prevent this problem, one of the following configurations is recommended:
•
•
•
Note
Examples
In the following example, if the load to a particular destination on an interface in dialer rotary group 5 exceeds interface load 200, the dialer will initiate another call to the destination:
interface dialer 5 dialer load-threshold 200Related Commands
dialer map
To configure a serial or ISDN interface to call multiple sites or to receive calls from multiple sites, use the dialer map command in interface configuration mode. Several options for using this command are possible; see the following description and the "Examples" section. To delete a particular dialer map entry, use the no form of this command.
Complete Syntax
dialer map protocol-keyword protocol-next-hop-address [broadcast | class dialer-map-class-name | modem-script modem-regular-expression | vrf vrf-name | name host-name | spc | speed 56 | speed 64 | system-script system-regular-expression | dial-string[:isdn-subaddress]]
no dialer map protocol-keyword protocol-next-hop-address [broadcast | class dialer-map-class-name | modem-script modem-regular-expression | vrf vrf-name | name host-name | spc | speed 56 | speed 64 | system-script system-regular-expression | dial-string[:isdn-subaddress]]
Dialer Map for an Asynchronous Interface
To configure an asynchronous interface to place a call to a single site that requires a system script or that has no assigned modem script, or to multiple sites on a single line, on multiple lines, or on a dialer rotary group, use the following form of the dialer map interface configuration command:
dialer map protocol-keyword protocol-next-hop-address [name host-name] [broadcast] [modem-script modem-regular-expression] [system-script system-regular-expression] [dial-string]
no dialer map protocol-keyword protocol-next-hop-address [name host-name] [broadcast] [modem-script modem-regular-expression] [system-script system-regular-expression] [dial-string]
Dialer Map for ISDN Interface and ISDN AOC Short-Hold Idle Timeout
To configure an ISDN interface to place a call to multiple sites, to authenticate calls from multiple sites, and to identify the class name that configures the ISDN Advice of Charge (AOC) short-hold idle timeout, use the following form of the dialer map interface configuration command:
dialer map protocol-keyword protocol-next-hop-address [name host-name] [speed 56 | speed 64] [broadcast] class dialer-map-class-name [dial-string[:isdn-subaddress]]
no dialer map protocol-keyword protocol-next-hop-address [name host-name] [speed 56 | speed 64] [broadcast] class dialer-map-class-name [dial-string[:isdn-subaddress]]
Dialer Map for German and Australian SPC
The following command syntax is used only in Germany for circuits between an ISDN BRI and a 1TR6 ISDN switch, and in Australia for circuits between an ISDN PRI and a TS-014 switch. To set up network addressing on an ISDN BRI interface to support semipermanent connection between customer equipment and the exchange, use the following form of the dialer map interface configuration command:
dialer map protocol-keyword protocol-next-hop-address [name host-name] [spc] [speed 56 | speed 64] [broadcast] dial-string[:isdn-subaddress]
no dialer map protocol-keyword protocol-next-hop-address [name host-name] [spc] [speed 56 | speed 64] [broadcast] dial-string[:isdn-subaddress]]
Dialer Map for MPLS VPN
To configure a serial or ISDN interface to support an IP-based VPN routing and forwarding instance (VFR)-aware dialer map for a Multiprotocol Label Switching (MPLS) VPN, use the following form of the dialer map interface configuration command:
dialer map ip protocol-next-hop-address vrf vrf-name name host-name dial-string
no dialer map ip protocol-next-hop-address vrf vrf-name name host-name dial-string
Dialer Map for Bridging
To configure a serial or ISDN interface to support bridging, use the following form of the dialer map interface configuration command:
dialer map bridge [name host-name] [broadcast] [dial-string[:isdn-subaddress]]
no dialer map bridge [name host-name] [broadcast] [dial-string[:isdn-subaddress]]
Syntax Description
Defaults
For all forms of the command, no dialer map is configured. The default speed is 64 kbps. No scripts are defined for placing calls.
Command Modes
Interface configuration
Command History
Usage Guidelines
Usage Guidelines for Asynchronous Interfaces
Configure a dialer map command for each remote destination for an asynchronous interface. Specify chat scripts for a physical interface that is not part of a dialer rotary group when no chat script is specified for the line, or when a system chat script is required to log in to the remote system. However, you need not specify a system script under the following conditions:
•
•
If you adhere to the chat script naming convention suggested in the description of the chat-script command, use the form modem-script *modulation-type in the dialer map command; for example, *-v32bis. This form allows you to specify the modulation type that is best for the system you are calling, and allows the modem type for the line to be specified by the script dialer command.
The period (.) is a wildcard that matches any character, and the asterisk (*) indicates that the preceding character can be duplicated multiple times. For more information about regular expressions, refer to the "Regular Expressions" appendix in the Cisco IOS Dial Technologies Configuration Guide.
If a modem script is specified in the dialer map interface configuration command and a modem script is specified in the script dialer line configuration command, the first chat script that matches both is used. If no script matches both, an error message is logged and the connection is not established. If there is no modem chat script specified for the line, the first chat script (that is, the one specified in the chat-script global configuration command) that matches the regular expression of the modem script is used. If there is a system script specified in the dialer map interface configuration command, the first chat script to match the regular expression is used.
The modem-script and system-script keywords and corresponding arguments are optional. They are ignored on synchronous interfaces.
If you have named your chat script according to the type of modem and modulation (for example, codex-v32 or telebit v32), your regular expression could be codex-.* in the script dialer line configuration command, and *-v32bis in the modem script specified in the dialer map command for a system to which you want to connect using V.32bis modulation.
The modem lines (specified by the regular-expression argument in the script dialer line configuration command) would be set to one of the following regular expressions to match patterns, depending on the kind of modem you have:
•
•
•
Usage Guidelines for Synchronous Interfaces
Use the dialer map command with the name keyword but without the dial string in configurations in which remote sites are calling a central site, but the central site is not calling the remote site. With this command, the local device will authenticate the remote site using Challenge Handshake Authentication Protocol (CHAP) or Password Authentication Protocol (PAP), which will send the remote site's host name to the central site. The central site will then use this name to authenticate the caller, and will use the next hop address to send packets to the remote site. Because no dialer string is specified, the central site cannot call the remote router.
Usage Guidelines for ISDN Interfaces and ISDN AOC
Use the dialer map command with the name keyword in configurations in which remote sites are calling a central site, but the central site is not calling the remote site. With this command, the local device will authenticate the remote site using CHAP or PAP, which will send the remote site host name to the central site. The central site will then use this name to authenticate the caller, and will use the next hop address to send packets to the remote site. Because no dialer string is specified, the central site cannot call the remote router.
For ISDN interfaces only, you can specify an optional speed parameter for dialer map commands if you also specify a dial string. This option informs the ISDN software whether it should place a call at 56 or 64 kbps. If you omit the ISDN speed parameter, the default is 64 kbps.
For routers with ISDN interfaces, if CLI is provided, the host-name field may contain the number that calling line ID provides.
When the network provides ISDN AOC information, use the dialer map command with the class keyword for outgoing calls. Use the map-class dialer global command to identify the class name, the dialer idle-timeout command to define a static idle timeout period for outgoing calls to the class, and the dialer isdn short-hold command to define the minimum idle time to wait before disconnecting calls at the end of the charging period.
Usage Guidelines for MPLS VPN
Beginning with Cisco IOS Release 12.2(8)T, dialer software became capable of being "VRF-aware for MPLS VPN," meaning that it can distinguish between two destinations with the same IP address using information stored in a VRF. When the dialer map command is configured with the vrf keyword in an MPLS VPN, the dialer software looks up a map for the next hop address using the next hop address and the VRF name configured. Once dial-out takes place and authentication is complete, a virtual profile interface is created. The VRF is installed on the virtual profile interface using the following per-user authentication, authorization, and accounting (AAA) interface command:
cisco-avpair "lcp:interface-config=ip vrf forwarding vrf-name"
Data transfer occurs as defined by the virtual profile dialer. When an IP route for a particular VRF points to the dialer (configured using the ip route global configuration command), the dialer uses the VFR-aware dialer map to get the dial string and IP address, and to bring up the connection. Once the user is authenticated, a virtual access interface is created and the user details are downloaded from the AAA server, and finally, the appropriate IP VRF command is applied on the virtual access interface.
Examples
Asynchronous Interface Examples
The following example sets the dialer speed at 56 kbps to call a remote site at 172.19.2.5:
interface async 1encapsulation pppppp authentication chapdialer map ip 172.19.2.5 speed 56The following example shows a dialing chat script and a login chat script. The dialer in-band command enables dial-on-demand routing (DDR) on asynchronous interface 10, and the dialer map command looks for the specified dialing and the login scripts, then uses those scripts to dial the string 95550190.
chat-script dial ABORT ERROR "" "AT Z" OK "ATDT \T" TIMEOUT 30 CONNECT \cchat-script login ABORT invalid TIMEOUT 15 name: billw word: wewpass ">" "slip default"interface async 10dialer in-banddialer map ip 10.55.0.1 modem-script dial system-script login 95550190In the following example, the remote site is calling the central site, and the central site is calling the remote site. The central router uses the name ZZZ to authenticate the remote router when connection is made, and uses the dialer string 14155550134 to call the remote router if it is not currently connected.
interface async 1dialer map ip 172.19.2.5 name ZZZ 14155550134In the following example, a remote site is calling a central site, but the central site is not calling the remote site. The local device will authenticate the site that is calling in using CHAP. CHAP causes the remote site name, YYY, to be sent to the site it is calling. The central site will then use this name to authenticate the remote site.
interface async 1encapsulation pppppp authentication chapdialer map ip 172.19.2.5 name YYYISDN AOC Short-Hold Idle Timeout Example
In the following legacy DDR example, a BRI interface is configured with dialer map classes to use for outgoing calls, and a dialer idle timeout period to use for all incoming calls. All of the map classes are configured with dialer idle timeout periods that override the interface static dialer idle timeout for outgoing calls. Two map classes are also configured for an ISDN AOC short-hold idle timeout.
hostname A!username IA password 7 1533121F0725username IB password 7 110A1016262D29username IC password 7 1533121F072508isdn switch-type basic-net3!interface bri 0ip address 10.0.0.35 255.0.0.0encapsulation pppdialer idle-timeout 150dialer map ip 10.0.0.33 name IA class One 06966600050dialer map ip 10.0.0.40 name IB class Two 778578dialer map ip 10.0.0.45 name IC class Three 778579ppp authentication chap!map-class dialer Threedialer idle-timeout 300dialer isdn short-hold 10!map-class dialer Onedialer idle-timeout 300!map-class dialer Twodialer idle-timeout 300dialer isdn short-hold 10SPC Example
The following example configures the interface for semipermanent connections in Germany; the IP address and the phone number are provided:
dialer map ip 192.168.48.2 spc 49305550155:3789MPLS VPN Example
Note
virtual-profile virtual-template 1virtual-profile aaa!interface virtual-template 1ip unnumbered loopback0ppp authentication chapppp multilink...interface dialer 1dialer map ip 10.9.9.9 vrf new_vrf name new_name 5550145dialer map ip 10.9.9.9 vrf branch_vrf name branch_name 5550156ppp authentication chapppp multilink...ip route vrf vrfgreen_vrf 10.9.9.9 255.255.255.255 dialer1ip route vrf vrfyellow_vrf 10.9.9.9 255.255.255.255 dialer1Related Commands
dialer map snapshot
To define a dialer map for Cisco's snapshot routing protocol on a client router connected to a dial-on-demand routing (DDR) interface, use the dialer map snapshot command in interface configuration mode. To delete one or more previously defined snapshot routing dialer maps, use the no form of this command.
dialer map snapshot sequence-number dial-string
no dialer map snapshot [sequence-number]
Syntax Description
Defaults
No snapshot routing dialer map is defined.
Command Modes
Interface configuration
Command History
Usage Guidelines
Enter a command for each remote snapshot server router the client router should call during an active period.
Use the no dialer map snapshot form of this command to remove all previously defined snapshot dialer maps on the client router; use the no dialer map snapshot sequence-number form of this command to delete a specified dialer map.
Examples
The following examples define snapshot dialer maps on a client router:
dialer map snapshot 12 4151231234dialer map snapshot 13 4151231245The following example removes one of the previously defined snapshot routing dialer maps on the client router:
no dialer map snapshot 13Related Commands
dialer max-call
To specify the maximum number of calls to a remote destination that can be up at any one time for a dialer profile, use the dialer max-call command in interface configuration mode.
dialer max-call number
Syntax Description
Defaults
No maximum number of calls is specified.
Command Modes
Interface configuration
Command History
Usage Guidelines
The dialer max-calls command is used to specify the maximum number of calls for the dialer interface. This command applies to dialer interfaces only.
This command can be configured only if a dialer profile is enabled using the dialer pool command. The dialer max-call command cannot be used with legacy dial-on-demand routing (DDR).
When two connected routers are configured to dial out, only one router should have the dialer max-call or dialer pool-member max-links command configured. Otherwise, if both routers dial simultaneously, each will reject the incoming call when it exceeds the setting for the max-links argument. If the maximum number of calls configured is one and dialing out is synchronized, no connection will come up or it will take many retries before the connection stays up. To prevent this problem, one of the following configurations is recommended:
•
•
•
Examples
The following example sets a maximum of six calls:
dialer max-call 6Related Commands
dialer order
To specify the dialing order when multiple dial strings are configured, use the dialer order command in interface configuration mode. To change or remove the dialing order, use the no form of this command.
dialer order [sequential | round-robin | last-successful]
no dialer order [sequential | round-robin | last-successful]
Syntax Description
Defaults
Dial order is sequential.
Command Modes
Interface configuration
Command History
Usage Guidelines
The dialer order command keywords can be configured on a per-interface basis. The configuration rules are as follows:
•
•
You can use the dialer order command in configurations that apply to both legacy dialers and dialer profiles. The command is also compatible with the following dialer features and protocols:
•
•
•
•
•
•
Examples
The following legacy dialer configuration shows how to set the dialing software to try the telephone number of the last successful call when starting a new call, rather than the first telephone number in the list (555-4004):
interface Serial0/0ip address 10.2.1.130 255.255.255.0encapsulation pppdialer in-banddialer map ip 10.2.1.131 name jones1 modem-script scr-3 5554004dialer map ip 10.2.1.131 name jones1 modem-script scr-3 5554005dialer map ip 10.2.1.131 name jones1 modem-script scr-3 5554006dialer-group 1dialer order last-successfulIf in a previous attempt to dial network 10.2.1.131 the telephone number 555-4006 was successful, because the dial order is set to last-successful, the next attempt to dial network 10.2.1.131 will start again with the 555-4006 telephone number.
The following dialer profile configuration shows how to set the dialing software to try the telephone number that occurs after the most recently used dial string when starting a new call, rather than the first telephone number in the list (1904):
interface Dialer0ip address 10.1.1.130 255.255.255.0encapsulation pppdialer pool 1dialer string 1904dialer string 1905dialer string 1906dialer string 1907dialer-group 1dialer order round-robinIf in a previous attempt to dial network 10.1.1.130 the telephone number 1906 was successful, because the dial order is set to round-robin, the next attempt to dial network 10.1.1.130 will start with the 1907 telephone number.
Related Commands
dialer outgoing
To configure the dialer map class for a Network Specific Facilities (NSF) dialing plan to support outgoing calls, use the dialer outgoing command in map-class dialer configuration mode.
dialer outgoing class-name
Syntax Description
class-name
Keyword for a specified AT&T Primary-4ESS NSF dialing plan. The following keywords are supported: sdn, megacomm, and accunet.
Defaults
This command is disabled; no class name is provided.
Command Modes
Map-class dialer configuration
Command History
Usage Guidelines
Use this command only to define a dialer map class for an NSF call-by-call service offered by AT&T on Primary-4ESS ISDN switches. This command is not used for other vendors and switch types.
Examples
The following partial example shows a class called sdn to support the Software Defined Network (SDN) dialing plan. For a more complete example using all the related commands, see the map-class dialer command.
dialer outgoing sdnRelated Commands
dialer persistent
To force a dialer interface to be connected at all times, even in the absence of interesting traffic, use the dialer persistent command in interface configuration mode. To disable this option, use the no form of this command.
dialer persistent [delay [initial] seconds | max-attempts number]
no dialer persistent
Syntax Description
Defaults
No persistent connections are established. The default delay and initial delay interval is 1 second. There is no default or limit to the number of reconnection attempts.
Command Modes
Interface configuration
Command History
12.2(4)T
This command was introduced.
12.2(11)T
This feature was implemented on Cisco access server platforms.
Usage Guidelines
Do not use the dialer redial command when a dialer profile has been configured with the dialer persistent command. Both these configuration commands prompt the router to dial out, so it is desirable to configure only one of them.
Do not use the dialer idle-timeout interface configuration command when a dialer profile has been configured with the dialer persistent command. Doing so has no effect on the idle timer, which is overridden by the dialer idle-timeout command as dialer idle-timeout 0.
You can use the clear interface EXEC command on the dialer interface to clear unsuccessful dial attempts on a line without interesting traffic; the dialer software continues attempting to bring up the connection as persistent. To disconnect a persistent connection and prevent the software from attempting more dialing, use the shutdown interface configuration command.
Once a connection has been brought up as persistent, it cannot be torn down due to a fast-idle timeout.
Examples
The following example shows how to configure a dialer interface for dialer persistent:
!interface dialer 0ip address 10.1.1.2 255.255.255.0encapsulation pppdialer string 5550189dialer pool 1dialer-group 1dialer persistent delay initial 20!access-list 101 permit icmp any anyaccess-list 101 deny ip any anydialer-list 1 protocol ip list 101Related Commands
dialer pool
To specify, for a dialer interface, which dialing pool to use to connect to a specific destination subnetwork, use the dialer pool command in interface configuration mode. To remove the dialing pool assignment, use the no form of this command.
dialer pool number
no dialer pool number
Syntax Description
Defaults
Disabled; no default number is specified.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to dialer interfaces only.
Examples
The following example shows a dialer interface configuration that is linked to the physical interface configuration shown for BRI 1 in the dialer pool-member command section. Dialer interface 1 uses dialer pool 3, of which BRI 1 is a member.
! This is a dialer profile for reaching remote subnetwork 10.1.1.1.interface Dialer1ip address 10.1.1.1 255.255.255.0encapsulation pppdialer remote-name Smalluserdialer string 4540dialer pool 3dialer-group 1The following example might accompany the previous dialer profile configuration example. Physical interface BRI 1 has a reserved channel in dialer pool 3. That channel is inactive until BRI 1 uses it to place calls.
interface BRI1encapsulation pppdialer pool-member 1 priority 50dialer pool-member 2 priority 50! BRI 1 has a reserved channel in dialer pool 3; the channel remains inactive! until BRI 1 uses it to place calls.dialer pool-member 3 min-link 1ppp authentication chapRelated Commands
dialer pool-member
To configure a physical interface to be a member of a dialer profile dialing pool, use the dialer pool-member command in interface configuration mode. To remove the configuration, use the no form of this command.
dialer pool-member number [priority priority] [min-link minimum] [max-link maximum]
no dialer pool-member number
Syntax Description
Command Default
The interface is not a member of a dialer profile dialing pool.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to asynchronous serial, synchronous serial, BRI, and PRI physical interfaces only. It does not apply to dialer interfaces.
The common number used in the dialer pool command and in the dialer pool-member command links the physical interface and dialer interface configurations.
The min-link keyword and value are used primarily for dial backup.
The Cisco IOS software provides the dialer max-links interface configuration command and the max-link keyword with the dialer pool-member command to specify a maximum number of links. When two linked systems are configured to dial out, only one system needs to have the maximum number of links configured. Otherwise, if both systems dial simultaneously, each will reject the incoming call when it exceeds the specified maximum links. If maximum links is configured to 1 and the dialing out is synchronized, no connection will come up or it will take many retries before a connection stays up. Some suggestions for correcting this behavior follow:
•
•
•
Examples
The following example for a 23-channel ISDN PRI T1 interface shows that only one channel is available for incoming calls and 22 channels are reserved for outgoing calls:
dialer pool-member 1 min-link 22 max-link 23The following sample report from the debug dialer EXEC command indicates that once one incoming call has been received, the next incoming call is denied:
Incoming call id 0x3 rejected, exceeded max calls...Incoming call id 0x3 rejected, exceededThe following example reserves 19 channels for an incoming call on a 23-channel ISDN PRI T1 interface:
dialer pool-member 1 min-link 5 max-link 24The following example shows the configuration of one ISDN BRI interface to be a member of dialer pool 2 with priority 100:
interface BRI2encapsulation pppdialer pool-member 2 priority 100ppp authentication chapIn the following example, BRI physical interface configuration BRI 1 has one reserved channel in dialer pool 3. That channel is inactive until BRI 1 uses it to place calls.
interface BRI1encapsulation pppdialer pool-member 1 priority 50dialer pool-member 2 priority 50!BRI 1 has a reserved channel in dialer pool 3; the channel remains inactive!until BRI 1 uses it to place calls.dialer pool-member 3 min-link 1ppp authentication chapRelated Commands
dialer pool
Specifies for a dialer interface, which dialing pool to use to connect to a specific destination subnetwork.
dialer priority
To set the priority of an interface in a dialer rotary group, use the dialer priority command in interface configuration mode. To revert to the default setting, use the no form of this command.
dialer priority number
no dialer priority
Syntax Description
number
Priority of an interface in a dialer rotary group; the highest number indicates the highest priority. This is a number from 0 through 255. The default value is 0, the lowest priority.
Defaults
No priority is predefined. When priority is defined, the default value is 0.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is meaningful only for interfaces that are part of dialer rotary groups.
The value 0 indicates the lowest priority, and 255 indicates the highest priority. The dialer priority command controls which interfaces within a dialer rotary group will be used first. Higher priority interfaces (configured with higher n value) are used first.
The dialer priority command gives you the ability to tell the dialer rotary group which free interface (and, by extension for asynchronous interfaces, which modem) to use first. This command applies to outgoing calls only.
For example, a router or access server might have a selection of many modems, some of which are better performers than others. You might have a 19.2-kbps, two 4800-bps, three 1200-bps, and one 300-bps modem on interfaces in one dialer rotary group. You do not want the router or access server to make the call on the 300-baud modem if any of the faster modems are free. You want to use the highest-performance modems first, and the slowest modems last.
Examples
In the following example, asynchronous interface 3 will be used after interfaces with higher priority and before interfaces with lower priority:
interface async 3 dialer priority 5Related Commands
dialer reserved-links
Includes a specified interface in a dialer rotary group.
interface dialer
Defines a dialer rotary group.
dialer redial
To configure redial after failed outbound dial attempts, use the dialer redial command in interface configuration mode. To disable redial, use the no form of this command.
dialer redial interval interval-time attempts redials [re-enable disable-time]
no dialer redial
Syntax Description
Defaults
Redial timer disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command to customize the number of redial attempts to be made, the interval between redial attempts, and the amount of time the interface will be disabled if all redial attempts fail. Setting attempts 0 prevents redial attempts without inactivating the re-enable option. The re-enable option can be applied to both serial dialers and dialer profile interfaces.
When a logical dialer interface such as a dialer profile or a dialer rotary group is used, redial attempts may occur on a different physical dialer on each attempt. The physical dialer selection algorithm may be customized using the dialer rotor interface configuration command.
Do not use the dialer redial command when a dialer profile has been configured with the dialer persistent command. Both these configuration commands prompt the router to dial out, so it is desirable to configure only one of them.
Examples
The following example configures the dialer to make five redial attempts with an interval of 10 seconds between attempts. If all redial attempts fail, the interface will be disabled for 50 minutes.
dialer redial interval 10 attempts 5 re-enable 3000Related Commands
dialer remote-name
To specify the authentication name of the remote router on the destination subnetwork for a dialer interface, use the dialer remote-name command in interface configuration mode. To remove the specified name, use the no form of this command.
dialer remote-name user-name
no dialer remote-name
Syntax Description
user-name
Case-sensitive character string identifying the remote device; maximum length is 255 characters.
Command Default
No remote name is specified.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies only to dialer interfaces.
Only one remote name can be associated with a dialer interface at a time. You may change the name associated with the dialer interface by reissuing the dialer remote-name command. Issuing the no dialer remote-name command removes the remote name configuration.
When using Challenge Handshake Authentication Protocol (CHAP) or Password Authentication Protocol (PAP) authentication, user-name is the name of the remote device that is authenticating.
Examples
The following partial example sets the name of the remote host to yourhost:
interface dialer 1dialer remote-name yourhostRelated Commands
dialer reserved-links
To reserve links for dial-in and dial-out, use the dialer reserved-links command in interface configuration mode. To clear the link, use the no form of this command.
dialer reserved-links {dialin-link | dialout-link}
no dialer reserved-links
Syntax Description
Defaults
By default, no links are reserved.
Command Modes
Interface configuration
Command History
Examples
The following example sets dial in reserved links to 1 and dialout reserved links to 0 on the Dialer0 interface:
interface Dialer0dialer aaadialer reserved-links 1 0Related Commands
dialer congestion-threshold
Specifies congestion threshold in connected links.
sgbp dial-bids
Allows the stack group to bid for dialout connection.
dialer rotary-group
To include a specified interface in a dialer rotary group, use the dialer rotary-group command in interface configuration mode. To remove the specified interface, use the no form of this command.
dialer rotary-group interface-number
no dialer rotary-group interface-number
Syntax Description
Defaults
No interfaces are included in a dialer rotary group.
Command Modes
Interface configuration
Command History
Examples
The following example places asynchronous interfaces 1 and 2 into dialer rotary group 1, defined by the interface dialer 1 command:
hostname central-site! PPP encapsulation is enabled for interface dialer 1.interface dialer 1encapsulation pppdialer in-bandip address 172.18.2.1 255.255.255.0ip address 172.16.4.1 255.255.255.0 secondary!! The first dialer map command allows the central site and remote site YYY ! to call each other and allows the central site to authenticate site YYY ! when it calls in. The second dialer map command, with no dialer string, ! allows the central site to authenticate remote site ZZZ when it calls in, but ! the central site cannot call remote site ZZZ (no phone number).dialer map ip 172.18.2.5 name YYY 14155553434dialer map ip 172.16.4.5 name ZZZ!! The DTR pulse signals for three seconds on the interfaces in dialer ! group 1. This holds the DTR low so the modem can recognize that DTR has been ! dropped.pulse-time 3!! Interfaces async 1 and async 2 are placed in dialer rotary group 1. ! All of the interface configuration commands (the encapsulation and dialer ! map commands shown earlier in this example) applied to interface ! dialer 1 apply to the physical interfaces assigned to the dialer group.!interface async 1dialer rotary-group 1interface async 2dialer rotary-group 1Related Commands
dialer rotor
To specify the method for identifying the outbound line to be used for ISDN or asynchronous dial-on-demand routing (DDR) calls, use the dialer rotor command in interface configuration mode. To remove the specified method, use the no form of this command.
dialer rotor {priority | best}
no dialer rotor {priority | best}
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command allows the router to skip outbound ISDN BRI and asynchronous lines that have problems. This command would not be useful for ISDN PRI, unless your local telephone service provider has problems keeping your lines properly configured.
Related Commands
dialer string
To specify the string (telephone number) to be called for interfaces calling a single site, use the dialer string command in interface configuration mode. To delete the dialer string specified for the interface, use the no form of this command.
dialer string dial-string[:isdn-subaddress]
no dialer string
Syntax Description
dial-string
String of characters to be sent to a DCE device.
:isdn-subaddress
(Optional) ISDN subaddress.
Defaults
No strings are predefined.
Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command on an asynchronous interface, you must define a modem chat script for the associated line by using the script dialer command. A script must be used to implement dialing.
Dialers configured as in-band pass the string to the external dialing device. Specify one dialer string command per interface.
To specify multiple strings, use the dialer map command. In general, you include a dialer string or dialer map command if you intend to use a specific interface to initiate a DDR call.
Note
The string of characters specified for the dial-string argument is the default number used under the following conditions:
•
•
ITU-T V.25bis Options
On synchronous interfaces, depending on the type of modem you are using, International Telecommunication Union Telecommunication (ITU-T) Standardization Sector V.25bis options might be supported as dial-string parameters of the dialer string command. Supported options are listed in Table 7. The functions of the parameters are nation specific, and they may have different implementations in your country. These options apply only if you have enabled DDR with the dialer in-band command. Refer to the operation manual for your modem for a list of supported options.
Note
Examples
The following example specifies a dial-on-demand routing (DDR) telephone number to be tone-dialed on interface async 1 using the dialer string command:
interface async 1dialer string T14085553434Related Commands
dialer string (dialer profiles)
To specify the string (telephone number) to be used when placing a call from an interface, use the dialer string command in interface configuration mode. To delete the telephone number specified for the interface, use the no form of this command.
dialer string dial-string [class class-name]
no dialer string
Syntax Description
dial-string
Telephone number to be sent to a DCE device.
class class-name
(Optional) Dialer map class associated with this telephone number.
Defaults
No telephone numbers and class names are predefined.
Command Modes
Interface configuration
Command History
Usage Guidelines
When you use dialer profiles for DDR, use the dialer string class form of this command to define a map class for a specific dialer profile.
Dialer profiles make it unnecessary to use dialer maps to configure DDR.
Note
Examples
The following example specifies that the dial string 4159991234 be used in calls to destinations defined by the map class sf:
dialer string 4159991234 class sfRelated Commands
dialer string (legacy DDR)
To specify the destination string (telephone number) to be called for interfaces calling a single site, use the dialer string command in interface configuration mode. To delete the dialer string specified for the interface, use the no form of this command.
dialer string dial-string[:isdn-subaddress]
no dialer string
Syntax Description
dial-string
String of characters to be sent to a DCE device.
:isdn-subaddress
(Optional) ISDN subaddress preceded by a colon.
Defaults
No strings are predefined.
Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command on an asynchronous interface, you must define a modem chat script for the associated line by using the script dialer command. A script must be used to implement dialing.
Dialers configured as in-band pass the string to the external dialing device. Specify one dialer string command per interface.
In general, you include a dialer string command if you intend to use a specific interface to initiate a dial-on-demand routing (DDR) call.
Note
The string of characters specified for the dial-string argument is the default number used under the following conditions:
•
•
ITU-T V.25bis Options
On synchronous interfaces, depending on the type of modem you are using, International Telecommunication Union Telecommunication (ITU-T) Standardization Sector V.25bis options might be supported as dial-string parameters of the dialer string command. Supported options are listed in Table 7. The functions of the parameters are nation specific, and they may have different implementations in your country. These options apply only if you have enabled DDR with the dialer in-band command. Refer to the operation manual for your modem for a list of supported options.
Note
Examples
The following example specifies a DDR telephone number to be tone-dialed on asynchronous interface 1 using the dialer string command:
interface async 1dialer string T14085553434Related Commands
dialer string trunkgroup
To specify a dial-out telephone number and dial-out trunk group name for a static configuration on a network access server (NAS), use the dialer string trunkgoup command in interface configuration mode. To delete the static, dial-out trunk group configuration, use the no form of this command.
dialer string dial-string trunkgroup trunkgroup-label
no dialer string dial-string trunkgroup trunkgroup-label
Syntax Description
dial-string
String of characters to be dialed.
trunkgroup-label
A predefined dial-out trunk group name.
Defaults
No trunk groups are defined.
Command Modes
Interface configuration
Command History
Usage Guidelines
A dialer string command, in general, enables a specific interface for initiating a dial-on-demand routing (DDR) call.
The dialer string trunkgroup command enables use of a dial-out trunk group, which directs an outbound synchronous or asynchronous call to be initiated by DDR on a specific channel of an ISDN circuit. The channel (also called a digital service 0 or DS0 link), is a member of a defined dial-out trunk group. Individual DS0s from various signaling circuits can be aggregated into a dial-out trunk group.
The dial-out trunk group configured by the dialer string trunkgroup command must be part of a static configuration on an NAS. See the "Related Commands" section for commands that allow other nonstatic configurations of dial-out trunk groups.
Examples
The following example enables use of dial-out trunk group TG1 on dialer interface 0 as part of a static NAS configuration:
interface dialer 0dialer string 5551212 trunkgroup TG1Related Commands
dialer voice-call
To configure the dialer map class for a Network Specific Facilities (NSF) dialing plan to support outgoing voice calls, use the dialer voice-call command in map-class dialer configuration mode.
dialer voice-call
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Map-class dialer configuration
Command History
Examples
The following partial example defines a dialer map class to support the SDN dialing plan and to support outgoing voice calls. For a more complete example using all the related commands, see the map-class dialer command.
map-class dialer sdnplandialer voice-calldialer outgoing sdnRelated Commands
dialer vpdn
To enable a dialer profile or dial-on-demand routing (DDR) dialer to use Layer 2 Tunnel Protocol (L2TP) dialout, use the dialer vpdn command in interface configuration mode. To disable L2TP dialout on a dialer profile or DDR dialer, use the no form of this command.
dialer vpdn
no dialer vpdn
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
The dialer vpdn command must be configured on the LNSs dialer interface to enable L2TP dialout. This command enables the dialer to place a VPDN call.
Examples
The following example shows how to configure the dialer interface and VPDN group on an LNS for L2TP dialout:
interface Dialer2ip address 172.16.2.3 255.255.255.128encapsulation pppdialer remote-name reubendialer string 5551234dialer vpdndialer pool 1dialer-group 1ppp authentication chapvpdn-group 1request-dialoutprotocol l2tppool-member 1initiate-to ip 172.21.9.4Related Commands
dialer aaa
Allows a dialer to access the AAA server for dialing information.
request-dialout
Enables an LNS to request VPDN dial-out calls by using L2TP.
dialer wait-for-carrier-time (interface)
To specify the length of time the interface waits for a carrier, use the dialer wait-for-carrier-time command in interface configuration mode. To reset the carrier wait time value to the default, use the no form of this command.
dialer wait-for-carrier-time seconds
no dialer wait-for-carrier-time
Syntax Description
seconds
Number of seconds that the interface waits for the carrier to come up when a call is placed. Acceptable values are positive, nonzero integers.
Defaults
30 seconds
Command Modes
Interface configuration
Command History
Usage Guidelines
On asynchronous interfaces, the dialer wait-for-carrier-time command sets the total time allowed for the chat script to run.
If a carrier signal is not detected in this amount of time, the interface is disabled until the enable timeout occurs (configured with the dialer enable-timeout command).
Do not use this command for BRI and leased-line interfaces.
Examples
The following example specifies a carrier wait time of 45 seconds on asynchronous interface 1:
interface async 1dialer wait-for-carrier-time 45Related Commands
dialer enable-timeout
Sets the length of time an interface stays down after a call has completed or failed and before the interface is available to dial again.
dialer wait-for-carrier-time (map-class)
To specify the length of time to wait for a carrier when dialing out to the dial string associated with a specified map class, use the dialer wait-for-carrier-time command in map-class dialer configuration mode. To reset the carrier wait time value to the default, use the no form of this command.
dialer wait-for-carrier-time seconds
no dialer wait-for-carrier-time
Syntax Description
seconds
Number of seconds that the interface waits for the carrier to come up when a call is placed. Acceptable values are positive, nonzero integers. The default is 30 seconds.
Defaults
30 seconds
Command Modes
Map-class dialer configuration
Command History
Usage Guidelines
You can define different dialer map classes with different wait-for-carrier times to suit the different types of lines and interfaces. For example, you must define a longer wait time for a map class used by serial interfaces than for one used by ISDN interfaces.
Do not use this command for BRI and leased-line interfaces.
Examples
The following example specifies a carrier wait time of 20 seconds for the class "Eng" on interface Dialer2:
interface Dialer2ip address 10.2.2.2 255.255.255.0encapsulation pppdialer remote-name Mediumuserdialer string 5264540 class Engdialer wait-for-carrier-time 20dialer load-threshold 50 eitherdialer pool 1dialer-group 2dialer wait-for-line-protocol
To set a maximum time the dialer will wait for a line protocol after establishing a physical connection before considering the call unsuccessful, use the dialer wait-for-line-protocol command in interface configuration mode. To disable this function, use the no form of this command.
dialer wait-for-line-protocol wait-time
no dialer wait-for-line-protocol
Syntax Description
wait-time
Time, in seconds, that the dialer will wait for the line protocol to come up after the physical layer connection has been established. The time can range from 1 to 2147483 seconds.
Defaults
Timer is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is supported only with encapsulation PPP.
By default the Cisco IOS software considers a dial-out attempt successful if a connection is established to the physical layer (Layer 1 of the Open System Interconnection reference model). The dialer wait-for-line-protocol command can be used to configure a router to wait a specific amount of time for a line protocol to come up once a physical layer connection has been established. If the call is dropped before the timer has elapsed, the call will be considered a failure. Redial will be triggered if the redial options have been configured with the dialer redial interface configuration command. The dialer failure statistics for the physical interface will be updated, which may influence the selection of a physical dialer for the next dial attempt. The physical dialer selection algorithm may be customized using the dialer rotor interface configuration command.
Note
Examples
The following example configures the dialer to wait 10 seconds for a line protocol after making a physical connection:
dialer wait-for-line-protocol 10Related Commands
dialer watch-disable
Note
To set a delay time to the backup interface, use the dialer watch-disable command in interface configuration mode. To disable this feature, use the no form of this command.
dialer watch-disable timeout
no dialer watch-disable
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
11.3
This command was introduced.
12.3(11)T
This command was replaced by the dialer watch-list delay command.
Usage Guidelines
This command is used to add a delay time to the backup interface. The delay time delays the time it takes for the backup interface to disconnect after the primary interface recovers.
Examples
The following example forces a 6-second delay to the backup interface once the primary interface recovers:
interface bri0ip address 10.1.1.2 255.255.255.0encapsulation pppdialer map ip 10.3.1.1 255.255.255.0 name mymap 5550134dialer-group 1dialer watch-group 1dialer watch-disable 6Related Commands
show dialer dnis
Displays general diagnostic information for ISDN BRI interfaces configured for DDR.
dialer watch-group
To enable dial-on-demand routing (DDR) backup on an interface using Dialer Watch, configure the interface using the dialer watch-group command in interface configuration mode. To disable this feature, use the no form of this command.
dialer watch-group group-number
no dialer watch-group group-number
Syntax Description
group-number
Group number assigned that will point to a globally defined list of IP addresses to watch. The valid range is 1 to 255.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the dialer watch-group command on the secondary interface you want to enable DDR backup.
The dialer watch group number points to a globally defined list (the dialer watch-list command) that contains the IP addresses to be watched. If you use the dialer watch-group command you must also use the dialer watch-list command.
You must configure the standard commands required to enable the router to perform DDR in addition to the Dialer Watch commands. Refer to the Cisco IOS Dial Technologies Configuration Guide and the Cisco IOS Dial Technologies Command Reference for additional information.
The dialer watch-group and dialer watch-list commands can be added in any order.
Examples
The following example configures BRI interface 0 as the backup interface:
interface bri0ip address 10.1.1.2 255.255.255.0encapsulation pppdialer watch-group 1Related Commands
dialer watch-list
Adds the list of IP addresses to be monitored for Dialer Watch.
dialer watch-list
To specify a list of watched routes of IP addresses or optionally, IP address and VPN routing and forwarding (VRF) instance pairs to be monitored by Dialer Watch, or to configure the router to dial the backup link if the primary link fails during initial startup, use the dialer watch-list command in global configuration mode. To disable these features, use the no form of this command.
dialer watch-list group-number {ip ip-address address-mask [vrf vrf-name] | delay route-check initial seconds}
no dialer watch-list group-number {ip ip-address address-mask [vrf vrf-name] | delay route-check initial seconds}
Syntax Description
Defaults
The dialer watch-list command is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to add all IP addresses or networks that you want monitored. There is no software limit to the number of IP addresses that can be added to a group.
Use this command with the dialer watch-group interface configuration command. The group-number value must match the group number set in the dialer watch-group interface configuration command. For example, if you use dialer watch-group 1, you must also use dialer watch-list 1.
The dialer watch-list and dialer watch-group commands can be added in any order.
Address matching is exact; therefore, you must apply the specific IP address and mask range for the networks that you want monitored. Use the show ip route command to verify that the route you are watching exists in the routing table. The route configured for the dialer watch-list command must match the one in the routing table exactly. This matching includes verifying that both the network and the masks are identical. You must configure the standard commands required to enable the router to perform dial-on-demand routing (DDR) in addition to configuring the Dialer Watch commands. Refer to the Cisco IOS Dial Technologies Configuration Guide and the Cisco IOS Dial Technologies Command Reference for additional information.
Enabling the delay route-check initial keywords enables the router to check whether the primary route is up after the initial startup of the router is complete and the timer (in seconds) expires. Without this command, the Dialer Watch feature is triggered only when the primary route is removed from the routing table. If the primary link fails to come up during initial startup of the router, the route is never added to the routing table and hence cannot be watched. Therefore, using the delay route-check initial keywords enables the Dialer Watch feature to dial the backup link in the event of a primary link failure during the initial startup of the router.
Enabling the vrf vrf-name keyword and argument configures the corresponding VRF table to be used to detect when the watched route for the VRF has gone down. A VRF is a per-VPN routing information repository that defines the virtual private network (VPN) membership of a customer site attached to a network access server. A VRF consists of an IP routing table, a derived Cisco Express Forwarding (CEF) table, a set of interfaces that use the forwarding table, and a set of rules and routing protocol parameters that control the information that is included in the routing table. A separate set of routing and CEF tables is maintained for each VPN customer.
It is important to note that the VRF might have overlapping address space, as follows: At the provider edge (PE) router, each customer edge (CE) router will have a corresponding VRF associated with it. Further, two CE routers might be using the same address space, so that the corresponding VRFs at the PE router will have overlapping address space. For this reason, when using the vrf vrf-name keyword and argument, configure the watched route as an IP address-VRF name pair, where the IP address is the watched IP address and the VRF name is the routing and forwarding instance to which the IP address belongs. Configuring the Dialer Watch feature with only the IP address does not ensure that the correct CE route will be dialed when a watched route goes down. Configuring Dialer Watch with an IP address and VRF name pair ensures that the VRF table corresponding to the routing and forwarding instance to which the IP address belongs is found and the correct CE is dialed.
You can define one watch route that watches the same IP address, but belongs to a different VRF, in a single watch list.
Examples
The following example specifies a pair of watched routes in a legacy dialer configuration. In this configuration, watch lists 1 and 2 are both watching the same IP address, but belong to different VRFs.
interface BRI3/0ip address 10.0.2.2 255.255.255.0encapsulation pppdialer map 10.1.2.0 vrf v1 3xxxxxxdialer map 10.1.2.0 vrf v2 4xxxxxxdialer-group 1dialer watch-group 1dialer watch-group 2isdn switch-type nttppp authentication chap!dialer watch-list 1 ip 10.2.1.0 255.255.255.0 vrf v1dialer watch-list 2 ip 10.2.1.0 255.255.255.0 vrf v2The following example specifies a pair of watched routes in a dialer rotary group configuration. In this configuration, watch lists 1 and 2 are both watching the same IP address, but belong to different VRFs.
interface BRI3/0no ip addressencapsulation pppdialer rotary-group 1isdn switch-type nttppp authentication chap!interface Dialer1ip address 10.0.2.2 255.255.255.0encapsulation pppdialer remote-name c3640-Bdialer map 10.1.2.0 vrf v1 3xxxxxxdialer map 10.1.2.0 vrf v2 4xxxxxxdialer watch-group 1dialer watch-group 2dialer-group 1ppp authentication chap!dialer watch-list 1 ip 10.2.1.0 255.255.255.0 vrf v1dialer watch-list 2 ip 10.2.1.0 255.255.255.0 vrf v2dialer watch-list 1 delay disconnect 30The following example specifies a pair of watched routes in a dialer profile configuration. In this configuration, watch lists 1 and 2 are both watching the same IP address, but belong to different VRFs.
interface BRI3/0no ip addressencapsulation pppdialer pool-member 1isdn switch-type nttppp authentication chap!interface Dialer1ip vrf forwarding v1ip address 10.0.2.2 255.255.255.0encapsulation pppdialer pool 1dialer remote-name c3640-Bdialer watch-disable 30dialer string 03xxxxxxx1dialer caller 03xxxxxxx1 callbackdialer watch-group 1dialer-group 1ppp authentication chap!interface Dialer2ip vrf forwarding v2ip address 10.0.2.2 255.255.255.0encapsulation pppdialer pool 1dialer remote-name c3640-Bdialer string 04xxxxxxx1dialer caller 04xxxxxxx1 callbackdialer watch-group 2dialer-group 1ppp authentication chap!dialer watch-list 1 ip 10.2.1.0 255.255.255.0 vrf v1dialer watch-list 2 ip 10.2.1.0 255.255.255.0 vrf v2dialer watch-list 1 delay disconnect 30dialer watch-list 2 delay disconnect 30The following example lists IP addresses to be watched and forms a group of networks to monitor:
dialer watch-list 1 ip 10.1.1.0 255.255.255.0dialer watch-list 1 ip 10.31.1.0 255.255.255.0dialer watch-list 1 ip 10.12.1.0 255.255.255.0The following partial example shows how to ensure that the router will check that the primary route is up after initial startup of the router is complete:
! Create backup link and enable process switchinginterface BRI0/0ip address 10.13.1.1 255.255.255.0encapsulation pppno ip route-cache...! Enable dialer watch on this backup interface.! Watch the route specified with the dialer watch-list 1 command.! Apply interesting traffic defined in dialer list 1.! Apply crypto map on backup interface.dialer watch-group 1dialer-group 1isdn switch-type basic-ts013no peer neighbor-routeno cdp enableppp authentication chapcrypto map cisco...! Access control list (ACL) 101 is the IPSec traffic used in match address.! ACL 110 is for the dialer list to mark all IP traffic uninteresting.! The dialer watch will trigger the ISDN backup when the route is lost.access-list 101 permit ip host 10.11.11.11 host 10.11.22.22access-list 110 deny ip any anydialer watch-list 1 ip 192.168.0.222 255.255.255.255! These commands define the routes to be watched! and check whether the primary route is up after the initial startup of the! router is complete.! The exact route (including subnet mask) must exist in the routing table.! The dialer watch-group 1 command applies this list to the backup interface.dialer watch-list 1 delay route-check initial 10dialer-list 1 protocol ip list 110! Interesting traffic is defined by ACL 110.! The ACL is applied to BRI0/0 using dialer group 1.Related Commands
dialer watch-group
Enables DDR backup on an interface using Dialer Watch.
show ip route
Displays all static IP routes, or those installed using the AAA route download function.
dialer watch-list delay
To configure the router to delay before connecting or disconnecting a secondary link for a route monitored by Dialer Watch, use the dialer watch-list delay command in global configuration mode. To disable these delays, use the no form of this command.
dialer watch-list group-number delay {connect connect-time | disconnect disconnect-time}
no dialer watch-list group-number delay {connect connect-time | disconnect disconnect-time}
Syntax Description
Defaults
No delay is configured.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to configure a delay before connecting or disconnecting a secondary link for a route monitored by Dialer Watch. This command will not work unless dial-on-demand routing (DDR) is configured and Dialer Watch has been enabled.
Examples
The following example configures the router to wait 10 seconds before verifying that the primary link is still down and dialing a secondary link:
dialer watch-list 1 ip 10.1.1.0 255.255.255.0dialer watch-list 1 delay connect 10The following example configures the router to wait 10 seconds to disconnect a secondary link once the primary link has been reestablished:
dialer watch-list 1 ip 10.1.1.0 255.255.255.0dialer watch-list 1 delay disconnect 10Related Commands
dialer watch-group
Enables DDR backup on an interface using Dialer Watch.
dialer watch-list
Adds the list of IP addresses to be monitored for Dialer Watch.
dial-peer cor custom
To specify that named class of restrictions (COR) apply to dial peers, use the dial-peer cor custom command in global configuration mode.
dial-peer cor custom
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or keywords.
Command Modes
Global configuration
Command History
Usage Guidelines
You must use the dial-peer cor custom command and the name command to define the names of capabilities before you can specify COR rules and apply them to specific dial peers.
Examples of possible names might include the following: call1900, call527, call9, and call911.
Note
Examples
The following example defines two COR names:
dial-peer cor customname 900blackholename CatchAllRelated Commands
dial-peer cor list
To define a class of restrictions (COR) list name, use the dial-peer cor list command in global configuration mode. To remove a previously defined COR list name, use the no form of this command.
dial-peer cor list list-name
no dial-peer cor list list-name
Syntax Description
Defaults
No default behavior or keywords.
Command Modes
Global configuration
Command History
Usage Guidelines
A COR list defines a capability set that is used in the COR checking between incoming and outgoing dial peers.
Examples
The following example adds two members to the COR list named list1:
dial-peer cor list list1member 900blockmember 800_callRelated Commands
dial-shelf split backplane-ds0
To connect two router shelves to a dial shelf, use the dial-shelf split backplane-ds0 command in global configuration mode. To remove the connection, use the no form of this command.
dial-shelf split backplane-ds0 {predefined-option | userdefined option}
no dial-shelf split backplane-ds0
Syntax Description
predefined-option
Predefined backplane DS-0 pairs. See Table 7 for a list of these options.
userdefined option
Number of backplane DS-0 interfaces used by the router shelf that you define, in the range 128 to 2048.
Defaults
Option pair 6
Command Modes
Global configuration
Command History
Usage Guidelines
The options for this command come in pairs and vary according to the desired configuration. You will need to log in to each router shelf and separately configure the routers for the intended load. In most circumstances, it is recommended that the predefined options remain selected. These options are designed to be matched pairs, as seen in Table 7. You can select the userdefined keyword and define your own split, if needed.
Table 7 lists the predefined options.
dial-shelf split backplane ds-0 Predefined Options
1
1344
—
672
—
2016
2
1152
4
888
3
2040
3
1288
—
644
7
1932
4
1150
2
897
1
2047
51
960
—
960
—
1920
6
Default (no option entered)
1/2 of current input
—
Default (no option entered)
1/2 of current input
—
—
7
1024
—
1024
—
2048
1 This option is used to revert to the default for an environment that uses six E1 lines.
The dial-shelf split slot command must be defined for the dial-shelf split backplane-ds0 command to be active.
Even if your system is already using a split dial shelf configuration, configuring one router shelf to handle two T3 trunks and the other router to handle the third trunk requires you to take the entire access server out of service. Busyout all connections before attempting to reconfigure. The configuration must be changed to set up one pool of TDM resources that can be used by either DMM cards or UPC and a second pool of two streams that contains TDM resources that can be used only by UPCs.
You may have more trunk capacity than 2048 calls. It is your decision how to provision the trunks so the backplane capacity is not exceeded. If more calls come in than backplane DS0 capacity for that half of the split, the call will be rejected and an error message printed for each call. This cannot be detected while a new configuration is being built because the router cannot tell which T1 trunks are provisioned and which are not. The user may want some trunks in hot standby.
The DMM, HMM, and VoIP cards can use only 1792 DS0 of the available 2048 backplane DS0. The UPC and trunk cards can use the full 2048 backplane DS0.
The show tdm splitbackplane command shows the resources in two groups, the first 1792 accessible to all cards, and the remaining 256 accessible only to UPC and trunk cards.
Examples
The following example shows how to configure two router shelves. Refer to Table 7 to interpret the options specified.
Configure router shelf 1 to run two CT3 interfaces with channel-associated signaling (CAS) and the ability to answer 1344 calls:
dial-shelf split backplane-ds0 2ct3casConfigure router shelf 2 to run one CT3 interface with CAS on the second router shelf and the ability to answer 672 calls:
dial-shelf split backplane-ds0 1ct3casThe total calls configured for the system are 2036 (1344 plus 672).
Related Commands
dial-shelf split slots
To configure split dial shelves, use the dial-shelf split slots command in global configuration mode. To change the router shelf to normal mode, if a router is in split mode and the other router shelf has already relinquished control of all dial shelf slots or is switched off, use the no form of this command.
dial-shelf split slots slot-numbers
no dial-shelf split slots
Syntax Description
Defaults
No default behavior or keywords.
Command Modes
Global configuration
Command History
Usage Guidelines
You allocate the slots in the dial shelf between the two router shelves to achieve the desired configuration. The two router shelves are both configured to run in split mode by means of the dial-shelf split slots command. While a router is in split mode, additional slots can be added to the set that the router owns by re-entering the dial-shelf split slots command listing the new slots. The effect of entering two or more dial-shelf split slots commands with different slot numbers is cumulative.
Slots must be explicitly removed from the list of router-owned slots with the dial-shelf split slots remove command.
A single router can also be configured in split mode, but with no slots owned, by using the dial-shelf split slots none command.
When you configure a Cisco AS5800 system to operate in split mode, it is the same as having two Cisco AS5800 systems with each having a separate set of feature boards assigned to its router; they just happen to be sharing a single dial shelf. Modem pooling, for example, is the same as if you had two separate Cisco AS5800 systems. Router shelf 1 has a modem pool that consists of all the modem cards that reside in slots owned by router shelf 1. The same situation applies to router shelf 2.
Examples
The following example would configure the router shelf to own slots 0 through 2 and 6 through 8.
dial-shelf split slots 0 1 2 6 7 8In this example, the other router shelf could be configured to own the other slots: 3, 4, 5, 9, 10, and 11.
Related Commands
dial-shelf split slots none
To configure the router in dial shelf split mode but with no slots owned, use the dial-shelf split slots none command in global configuration mode.
dial-shelf split slots none
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or keywords.
Command Modes
Global configuration
Command History
Usage Guidelines
The dial-shelf split slots none command is useful for configuring a single router in split mode, but with no slots owned.
Examples
The following example changes dial shelf slot ownership. The router will no longer have ownership of any dial shelf slots.
dial-shelf split slots noneRelated Commands
dial-shelf split slots remove
To remove slots configured in split mode, use the dial-shelf split slots remove command in global configuration mode.
dial-shelf split slots remove slot-numbers
Syntax Description
slot-numbers
List of the dial shelf slot numbers to be removed ,separated by spaces, in the range 0 to 11.
Defaults
No default behavior or keywords.
Command Modes
Global configuration
Command History
Usage Guidelines
To move a slot from the control of one router shelf to the others, the router releasing the slot should be modified first by entering the dial-shelf split slots remove command, specifying the slot numbers to be released. The released slots can then be added to the slot set of the other router by re-entering the dial-shelf split slots command including the new slot numbers.
The router shelf that is losing the slot frees any resources and clears any state associated with the card in the slot it is relinquishing. The dial shelf controller (DSC) reconfigures its hub to ignore traffic from that slot, and if there is a card in the slot it will be reset. This ensures that the card frees up any TDM resource it might be using and allows it to restart under control of the router shelf that is subsequently configured to own the slot.
Examples
The following example removes dial shelf slot 8 from the list of owned dial shelf slots:
dial-shelf split slots remove 8The effect of multiple commands is cumulative.
Related Commands
dial-shelf split slots none
Configures the router in dial shelf split mode but with no slots owned.
dial-tdm-clock
To configure the clock source and priority of the clock source used by the time-division multiplexing (TDM) bus on the dial shelf of the Cisco AS5800, use the dial-tdm-clock command in global configuration mode. To return the clock source and priority to the default values, use the no form of this command.
dial-tdm-clock priority number {external {e1 | t1} [120ohm] | freerun | trunk-slot slot port port} [line {0 | 1}]
no dial-tdm-clock priority number {external {e1 | t1} [120ohm] | freerun | trunk-slot slot port port} [line {0 | 1}]
Syntax Description
Defaults
If no clock sources are specified, the software selects the first available good clock source on a trunk port.
Command Modes
Global configuration
Command History
Usage Guidelines
The TDM bus in the backplane on the dial shelf must be synchronized to the T1/E1 clocks on the trunk cards. The DSC card on the dial shelf provides hardware logic to accept multiple clock sources as input and use one of them as the primary source to generate a stable, PPL synchronized output clock. The input clock can be any of the following sources:
•
•
•
The clock commands are listed in the configuration file with the highest priority listed first.
If the current primary clock source is good, specifying another clock source of higher priority does not cause the clock source to switch to the higher priority clock source. The new higher priority clock source is used as a backup clock source. This prevents switching of the clock source as you enter multiple dial-tdm-clock priority configuration commands in random order. Also, it is important not to disturb the existing clock source as long as it is good. To force the new higher priority clock source to take over from a currently good primary clock source, configure the new clock source and use the no dial-tdm-clock priority command to remove the current primary clock source.
To display the current primary and backup clocks along with their priorities, use the show dial-shelf clocks EXEC command.
Examples
In the following example, an external clock source is set at priority 1 and the trunk card in slot 4, port 1 is set at priority 5:
Router(config)# dial-tdm-clock priority 1 external t1Router(config)# dial-tdm-clock priority 5 trunk-slot 4 port 1Router(config)# exitRelated Commands
show dial-shelf
Displays information about the dial shelf, including clocking information.
