-
Cisco IOS Dial Technologies Command Reference, Release 12.2
-
Using Cisco IOS Software
-
Commands A through CAS
-
Commands CHA through CPP
-
Commands D
-
Commands EN through IP
-
Commands IS through L2
-
Commands LCP through MOD
-
Commands MU through PPP
-
Commands PRI through SHE
-
Commands SHOW A through SHOW DI
-
Commands SHOW DS through SHOW LI
-
Commands SHOW M through SHOW N
-
Commands SHOW P through SHOW R
-
Commands SHOW S through SHOW V
-
Commands SHU through X
-
Index
-
Table Of Contents
lcp renegotiation
To allow the L2TP network server (LNS) to renegotiate the PPP Link Control Protocol (LCP) on dial-in calls, using Layer 2 Tunneling Protocol (L2TP) or Layer 2 Forwarding (L2F), use the lcp renegotiation command in virtual private dialup network (VPDN) group configuration mode. To remove LCP renegotiation, use the no form of this command.
lcp renegotiation {always | on-mismatch}
no lcp renegotiation
Syntax Description
always
Always renegotiate LCP at the LNS.
on-mismatch
Renegotiate LCP at the LNS only in the event of an LCP mismatch between the LAC and LNS.
Defaults
LCP renegotiation is disabled on the LNS.
Command Modes
VPDN group configuration
Command History
Usage Guidelines
You must enable the accept-dialin command on the VPDN group before you can use the lcp renegotiation command. Removing the accept-dialin command will remove the lcp renegotiation command from the VPDN group.
This command is valid only at the LNS. This command is useful for an LNS that tunnels to a non-Cisco L2TP access concentrator (LAC), where the LAC may negotiate a different set of LCP options than what the LNS expects.
When a PPP session is started at the LAC, LCP parameters are negotiated, and a tunnel is initiated, the LNS can either accept the LAC LCP negotiations or can request LCP renegotiation. Using the lcp renegotiation always command forces renegotiation to occur at the LNS. If the lcp renegotiation on-mismatch command is configured, then renegotiation will only occur if there is an LCP mismatch between the LNS and LAC.
Note
Older PC PPP clients may experience a "lock up" during PPP LCP renegotiation.
Examples
The following example configures the LNS to renegotiate PPP LCP with a non-Cisco LAC:
vpdn-group 1accept dialinprotocol l2tpvirtual-template 1terminate-from patlcp renegotiation on-mismatchRelated Commands
limit base-size
To define the base number of simultaneous connections that can be done in a single customer or virtual private dialup network (VPDN) profile, use the limit base-size command in customer profile configuration or VPDN profile configuration mode. To remove the limitation, use the no form of this command.
limit base-size {base-number | all}
no limit base-size {base-number | all}
Syntax Description
Defaults
The base size is set to all.
Command Modes
Customer profile configuration
VPDN profile configurationCommand History
Usage Guidelines
Use the limit base-size command to define the base number of simultaneous connections in a single customer or VPDN profile. The session limit applies to all the physical resource groups and pools configured in a single customer profile. If you want to define the number of overflow calls granted to a customer profile by using the limit overflow-size command, do not use the all keyword in the limit base-size command; instead, specify a base number.
Examples
The following example shows the total number of simultaneous connections limited to a base size of 48:
resource-pool profile customer customer1_isplimit base-size 48Related Commands
Defines the number of overflow calls granted to one customer or VPDN profile.
Creates a customer profile.
limit overflow-size
To define the number of overflow calls granted to one customer or virtual private dialup network (VPDN) profile, use the limit overflow-size command in customer profile configuration or VPDN profile configuration mode. To remove the overflow configuration, use the no form of this command.
limit overflow-size {overflow-calls | all}
no limit overflow-size {overflow-calls | all}
Syntax Description
overflow-calls
Number of overflow calls to grant, in the range from 0 to 1000. Default is 0.
all
Accept all overflow calls.
Defaults
The overflow size is set to 0.
Command Modes
Customer profile configuration
VPDN profile configurationCommand History
Usage Guidelines
Use the limit overflow-size customer or VPDN profile configuration command to define the number of overflow calls granted to one customer or VPDN profile. The overflow is not applied if the limit base-size command is set using the all keyword.
Examples
The following example shows 20 overflow calls granted to the customer profile called customer1_isp:
resource-pool profile customer customer1_isplimit overflow-size 20Related Commands
Defines the base number of simultaneous connections that can be done in a single customer or VPDN profile.
Creates a customer profile.
line-power
To configure an ISDN BRI port to supply line power to the terminal equipment (TE), use the line-power command in interface configuration mode. To disable the line power supply, use the no form of this command.
line-power
no line-power
Syntax Description
This command has no arguments or keywords.
Defaults
The BRI port does not supply line power.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is supported only if an installed BRI voice module (BVM) or BRI VIC is equipped to supply line power (phantom power).
This command is used only on a BRI port operating in NT mode. A BRI port operating in TE mode is automatically disabled as a source of line power, and the line-power command is rejected.
When you use the line-power command, the line power provision is activated on a BRI port if the port is equipped with the hardware to supply line power. When you enter the no line-power command, the line power provision is deactivated on a BRI port.
Note
Examples
The following example configures a BRI port to supply power to an attached TE device (only if the BVM is equipped to supply line power):
interface bri 1line-powerloadsharing
To configure endpoints for load sharing, use the loadsharing command in virtual private dialup network (VPDN) group configuration mode. To remove this function, use the no form of this command.
loadsharing ip ip-address [limit session-limit]
no loadsharing ip ip-address [limit session-limit]
Syntax Description
Defaults
No default is set, and this function is not used when not configured.
Command Modes
VPDN group configuration
Command History
Usage Guidelines
Use the loadsharing VPDN group configuration command to configure endpoints for loadsharing.
Examples
In the following example, VPDN group customer1-vpdng is created. L2TP IP traffic load is shared between two HGW/LNS. The IP addresses for the HGW/LNS WAN ports are 172.21.9.67 and 172.21.9.68 (the home gateway is a Cisco IOS router terminating L2TP sessions). The characteristics for link 172.21.9.67 are defined by using the request dialin command. The characteristics for link 172.21.9.68 are defined by using the loadsharing command.
A backup home-gateway router is specified at 172.21.9.69 by using the backup command. This router serves as a backup device for two load-sharing HGW/LNS:
vpdn-group customer1-vpdngrequest dialin l2tp ip 172.21.9.67 domain cisco.comloadsharing ip 172.21.9.68 limit 100backup ip 172.21.9.69 priority 5domain cisco2.comRelated Commands
local name
To specify a local host name that the tunnel will use to identify itself, use the local name command in global configuration mode. To remove a local name, use the no form of this command.
local name host-name
no local name host-name
Syntax Description
Defaults
A local host name must be explicitly configured.
Command Modes
Global configuration
Command History
11.3(5)AA
This command was introduced.
12.0(1)T
This command was integrated into Cisco IOS Release 12.0(1)T.
Usage Guidelines
This command allows each virtual private dialup network (VPDN) group to use a unique and local host name. The password hierarchy sequence that is used for tunnel identification and, subsequently, tunnel authentication, is as follows:
•
•
•
The username command defines the passwords associated with the local name and the host name.
Examples
The following example configures the local host name of the tunnel as Tunnel1:
local name Tunnel1Related Commands
loopback (controller e1)
To loop an entire E1 line (including all channel groups defined on the controller) toward the line and back toward the router or access server, use the loopback command in controller configuration mode. To remove the loop, use the no form of this command.
loopback
no loopback
Syntax Description
This command has no arguments or keywords.
Defaults
Loopback function is disabled.
Command Modes
Controller configuration
Command History
Usage Guidelines
This command is useful for testing the DCE channel service unit/data service unit (CSU/DSU) itself.
To display interfaces currently in loopback operation, use the show interfaces loopback EXEC command.
Examples
The following example configures the loopback test on the E1 line:
controller e1 0loopbackRelated Commands
loopback local (controller)
To loop an entire T1 line (including all channel groups defined on the controller) toward the line and the router or access server, use the loopback local command in controller configuration mode. To remove the loop, use the no form of this command.
loopback local
no loopback local
Syntax Description
This command has no arguments or keywords.
Defaults
Loopback function is disabled.
Command Modes
Controller configuration
Command History
Usage Guidelines
This command is useful for testing the DCE channel service unit/data service unit (CSU/DSU) itself.
To display interfaces currently in loopback operation, use the show interfaces loopback EXEC command.
Examples
The following example configures the loopback test on the T1 line:
controller t1 0loopback localRelated Commands
loopback local (interface)
To loop a channelized T1 or channelized E1 channel group, use the loopback local command in interface configuration mode. To remove the loop, use the no form of this command.
loopback local
no loopback local
Syntax Description
This command has no arguments or keywords.
Defaults
Loopback function is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is useful for looping a single channel group in a channelized environment without disrupting the other channel groups.
To display interfaces currently in loopback operation, use the show interfaces loopback EXEC command.
Examples
The following example configures the loopback test on the T1 line:
interface serial 1/0:22 loopback localRelated Commands
loopback remote (controller)
To loop packets from a MultiChannel Interface Processor (MIP) through the channel service unit/data service unit (CSU/DSU), over a dedicated T1 link, to the remote CSU at the single destination for this T1 link and back, use the loopback remote command in controller configuration mode. To remove the loop, use the no form of this command.
loopback remote
no loopback remote
Syntax Description
This command has no arguments or keywords.
Defaults
Command is disabled.
Command Modes
Controller configuration
Command History
Usage Guidelines
This command applies only when the device supports the remote function. It is used for testing the data communication channels.
For MIP cards, this controller configuration command applies if only one destination exists at the remote end of the cloud, the entire T1 line is dedicated to it, and the device at the remote end is a CSU (not a CSU/DSU). This is an uncommon case; MIPs are not usually used in this way.
To display interfaces currently in loopback operation, use the show interfaces loopback EXEC command.
Examples
The following example configures a remote loopback test:
interface serial 0loopback remoteRelated Commands
map-class dialer
To define a class of shared configuration parameters associated with the dialer map command for outgoing calls from an ISDN interface and for PPP callback, use the map-class dialer command in global configuration mode.
map-class dialer class-name
no map-class dialer class-name
Syntax Description
Defaults
Command is disabled; no class name is provided.
Command Modes
Global configuration
Command History
Usage Guidelines
The class-name argument in the map-class dialer command used to specify the class must be the same as a class-name argument used in a dialer map command.
This command is used on the PPP callback server, not on the callback client.
This command is used to define classes of calls for PPP callback for dial-on-demand routing (DDR), for ISDN Advice of Charge, and for Network Specific Facilities (NSF) call-by-call dialing plans.
For NSF call-by-call support on ISDN Primary-4ESS switches only, use one of the dialing-plan keywords listed in Table 15.
Table 15 NSF Keywords and Supported Services
sdnplan
SDN
Yes
Yes
GSDN (Global SDN)
megaplan
MEGACOMM
No
Yes
Yes
accuplan
ACCUNET
Yes
Yes
Yes
Examples
The following example configures the PPP callback server on an ISDN BRI interface on a router in Atlanta. The callback server requires an enable timeout and a map class to be defined.
interface BRI0ip 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 chap!map-class dialer dial1dialer callback-server usernameThe following example configures the ISDN switch type to Primary-4ESS and configures ISDN PRI on T1 controller 1/0, and sets the D channel for dialer map classes that reference the NSF dialing plans. Finally, the map-class dialer command uses a dialing plan keyword and the dialer outgoing command refers to the same plan.
isdn switch-type primary-4ess!!controller T1 1/0framing esflinecode b8zspri-group timeslots 1-24!interface Serial1/0:23description This is the DMS D-channel 415-886-9503ip address 10.1.1.3 255.255.255.0encapsulation pppno keepalivedialer map ip 10.1.1.1 name detroit class sdnplan 14155770715dialer map ip 10.1.1.2 name oakland class megaplan 14155773775dialer map ip 10.1.1.4 name oakland class accuplan 14155773778dialer-group 1ppp authentication chap!map-class dialer sdnplandialer outgoing sdn!map-class dialer megaplandialer voice-calldialer outgoing mega!map-class dialer accuplandialer outgoing accuThe following partial example configures BRI interface 0 to function as the callback server on the shared network. The callback server requires an enable timeout and a map class to be defined.
interface BRI0ip address 10.2.1.7 255.255.255.0encapsulation pppdialer callback-securedialer enable-timeout 2dialer map ip 10.2.1.8 name atlanta class dial1 81012345678901dialer-group 1ppp callback acceptppp authentication chap!map-class dialer dial1dialer callback-server usernameThe following example configures a map class named "hawaii" and sets an ISDN speed of 56 kbps for the class.
map-class dialer hawaiiisdn speed 56Related Commands
member
To alter the configuration of an asynchronous interface that is a member of a group, use the member command in interface configuration mode. To restore defaults set at the group master interface, use the no form of this command.
member asynchronous-interface-number command
no member asynchronous-interface-number command
Syntax Description
Defaults
No individual configurations are set for member interfaces.
Command Modes
Interface configuration
Command History
Usage Guidelines
You can customize a member interface by using the member command. Interfaces are designated as members of a group by using the interface group-async and group-range commands.
Examples
The following example defines interface 3 with a description of line 3, which is attached to a Hayes Optima modem:
interface group-async 0member 3 description line #3 Hayes OptimaRelated Commands
member (dial peer cor list)
To add a member to a dial peer class of restrictions (COR) list, use the member command in dial peer COR list configuration mode. To remove a member from a list, use the no form of this command.
member class-name
no member class-name
Syntax Description
class-name
Class name previously defined in dial peer COR custom configuration mode by using of the name command.
Defaults
No default behavior or values.
Command Modes
Dial peer COR list configuration
Command History
Examples
The following example adds three members to the COR list named list3:
dial-peer cor list list3member 900_callmember 800_callmember catchallRelated Commands
modem answer-timeout
To set the amount of time that the Cisco IOS software waits for the Clear to Send (CTS) signal after raising the data terminal ready (DTR) signal in response to RING, use the modem answer-timeout command in line configuration mode. To revert to the default value, use the no form of this command.
modem answer-timeout seconds
no modem answer-timeout
Syntax Description
Defaults
15 seconds
Command Modes
Line configuration
Command History
Usage Guidelines
This command is useful for modems that take a long time to synchronize to the appropriate line speed.
For more information, see the chapter "Creating and Using Modem Chat Scripts" in the Cisco IOS Dial Technologies Configuration Guide, Release 12.2.
Examples
The following example sets the timeout interval to 20 seconds for the modem connected to lines 3 through 13:
line 3 13 modem answer-timeout 20Related Commands
Supports dial-in modems that use the DTR signal to control the off-hook status of the modem.
Configures a line for both incoming and outgoing calls.
modem at-mode
To open a directly connected session and enter AT command mode, which is used for sending AT (modem attention) commands to Microcom manageable modems, use the modem at-mode command in EXEC mode.
modem at-mode slot/port
no modem at-mode slot/port
Syntax Description
slot/port
Slot number and modem port number. (Include the forward slash (/) when entering this variable.)
Defaults
Command is disabled.
Command Modes
EXEC
Command History
Usage Guidelines
Manageable modems return "OK" if the AT command you send is successfully enabled. Press Ctrl-C after sending an AT command to close the directly connected session.
Note
Examples
The following example opens a directly connected session on modem 1/1, enters AT command mode on modem 1/1, and transmits the AT commands through the out-of-band feature of modem 1/1:
Router# modem at-mode 1/1You are now entering AT command mode on modem (slot 1 / port 1).Please type CTRL-C to exit AT command mode.at%vMNP Class 10 V.34/V.FC Modem Rev 1.0/85OKat\sIDLE 000:00:00LAST DIALNET ADDR: FFFFFFFFFFFFMODEM HW: SA 2W United States4 RTS 5 CTS 6 DSR - CD 20 DTR - RIMODULATION IDLEMODEM BPS 28800 AT%G0MODEM FLOW OFF AT\G0MODEM MODE AUT AT\N3V.23 OPR. OFF AT%F0AUTO ANS. ON ATS0=1SERIAL BPS 115200 AT%U0BPS ADJUST OFF AT\J0SPT BPS ADJ. 0 AT\W0ANSWER MESSGS ON ATQ0SERIAL FLOW BHW AT\Q3PASS XON/XOFF OFF AT\X0PARITY 8N ATRelated Commands
Resets the hardware for one or more manageable modems on access servers and routers.
modem at-mode-permit
To permit a Microcom modem to accept a directly connected session, use the modem at-mode-permit command in line configuration mode. To disable permission for modems to accept a direct connection, use the no form of this command.
modem at-mode-permit
no modem at-mode-permit
Syntax Description
This command has no arguments or keywords.
Defaults
Command is enabled.
Command Modes
Line configuration
Command History
Usage Guidelines
After you enter this command, enter the modem at-mode command to enable a directly connected session on the modem. From AT command mode, you can enter AT (modem attention) commands directly from your terminal session.
For a complete list of supported AT commands, refer to the AT command documentation that came with your access server or router.
The no modem at-mode-permit command disables a modem from accepting a direct connection, which is useful for ensuring modem security.
Note
Examples
The following example permits the modem connected to TTY line 1 to accept a directly connected session:
line 1modem at-mode-permitRelated Commands
modem autoconfigure discovery
To configure a line to discover which kind of modem is connected to the router and to configure that modem automatically, use the modem autoconfigure discovery command in line configuration mode. To disable this feature, use the no form of this command.
modem autoconfigure discovery
no modem autoconfigure discovery
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Line configuration
Command History
Usage Guidelines
The modem is identified each time the line is reset. If a modem cannot be detected, the line continues retrying for 10 seconds. When the modem type is determined, this information remains stored until the modem is recycled or disconnected. Using Discovery mode is much slower than configuring a line directly.
Each time the modem is reset (every time a chat reset script is executed), a string of commands is sent to the modem, the first one being "return to factory-defaults."
Examples
The following example automatically discovers which kind of modem is attached to the router or access server:
modem autoconfigure discoveryRelated Commands
Directs a line to attempt to configure the attached modem using a predefined modemcap.
modem autoconfigure type
To direct a line to attempt to configure the attached modem using the entry for the modem-type argument, use the modem autoconfigure type command in line configuration mode. To disable this feature, use the no form of this command.
modem autoconfigure type modem-type
no modem autoconfigure type
Syntax Description
Defaults
No default behavior or values.
Command Modes
Line configuration
Command History
Usage Guidelines
The modem is reconfigured each time the line goes down.
Examples
The following example automatically configures the attached modem using the codex_3260 modemcap entry:
modem autoconfigure type codex_3260Related Commands
Configures a line to discover which kind of modem is connected to the router and to configure that modem automatically.
modem autotest
To automatically and periodically perform a modem diagnostics test for modems inside the access server or router, use the modem autotest command in global configuration mode. To disable or turn off the modem autotest service, use the no form of this command.
modem autotest {error threshold | minimum modems | time hh:mm [interval]}
no modem autotest
Syntax Description
Defaults
Command is disabled.
Command Modes
Global configuration
Command History
Examples
The following example shows how to set the modem autotest to run once per week at 3:00 a.m. Additionally, the autotest will activate if the system detects a modem error count higher than 40 errors.
Step 1
Router# show clock*15:00:01.031 EST Aug 25 1997Step 2
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# modem autotest time 03:00 168Step 3
Router(config)# modem autotest error 40Router(config)# exitRouter#%SYS-5-CONFIG_I: Configured from console by consoleStep 4
Router# show modem testDate Time Modem Test Reason State Result5/15 07:25:17 AM 1/0 Back-To-Back TIME INTERVAL Idle FAIL5/15 07:25:17 AM 1/1 Back-To-Back TIME INTERVAL Idle PASS5/15 07:25:17 AM 1/2 Back-To-Back TIME INTERVAL Idle PASS5/15 07:25:17 AM 1/3 Back-To-Back TIME INTERVAL Idle FAIL5/15 07:25:17 AM 1/4 Back-To-Back TIME INTERVAL Idle PASS5/15 07:25:17 AM 1/5 Back-To-Back TIME INTERVAL Idle PASS5/15 07:25:17 AM 1/6 Back-To-Back TIME INTERVAL Idle PASS5/15 07:25:17 AM 1/7 Back-To-Back TIME INTERVAL Idle PASS5/15 07:25:17 AM 1/8 Back-To-Back TIME INTERVAL Idle PASS5/15 07:25:17 AM 1/9 Back-To-Back TIME INTERVAL Idle PASS...Alternatively, you can display which modems were marked bad by the modem autotest by issuing the show modem EXEC command. Bad modems are marked by the letter B. In this example, modems 1/0 and 1/3 are marked bad (identified with a B), which takes them out of commission and makes them unable to participate in dial services:
Router# show modemInc calls Out calls Busied Failed No SuccMdm Usage Succ Fail Succ Fail Out Dial Answer Pct.B 1/0 0% 0 0 0 0 1 0 0 0%1/1 0% 0 0 0 0 3 0 0 0%1/2 0% 0 0 0 0 1 0 0 0%B 1/3 0% 0 0 0 0 1 0 0 0%1/4 0% 0 0 0 0 1 0 0 0%1/5 0% 0 0 0 0 1 0 0 0%1/6 0% 0 0 0 0 1 0 0 0%1/7 0% 0 0 0 0 1 0 0 0%1/8 0% 0 0 0 0 1 0 0 0%1/9 0% 0 0 0 0 1 0 0 0%...1/20 0% 0 0 0 0 0 0 0 0%1/21 0% 0 0 0 0 0 0 0 0%1/22 0% 0 0 0 0 0 0 0 0%modem bad
To remove an integrated modem from service and indicate it as suspected or proven to be inoperable, use the modem bad command in line configuration mode. To restore a modem to service, use the no form of this command.
modem bad
no modem bad
Syntax Description
This command has no arguments or keywords.
Defaults
Command is disabled.
Command Modes
Line configuration
Command History
Usage Guidelines
If you mark a modem as inoperable, it appears as Bad—without the asterisk (*)—in the Status column of the show modem command output. A modem marked inoperable by the modem startup-test command appears as Bad* in the show modem command output. Use the no modem bad command to unmark a modem as Bad* or Bad and restore it for dialup connection services.
Note
Examples
The first part of the following example shows a successful connection between modem 2/1 and modem 2/0, which verifies normal operating conditions between these two modems. However, when modem 2/1 is tested against modem 2/3, the back-to-back modem test fails. Therefore, modem 2/3 is suspected or proven to be inoperable. Modem 2/3 is removed from dialup services through the use of the modem bad command on line 28.
Router# test modem back-to-back 2/1 2/0Repetitions (of 10-byte packets) [1]: 10Router#%MODEM-5-B2BCONNECT: Modems (2/1) and (2/0) connected in back-to-back test: CONNECT9600/REL-MNP%MODEM-5-B2BMODEMS: Modems (2/0) and (2/1) completed back-to-back test: success/packets = 20/20Router# test modem back-to-back 2/1 2/3Repetitions (of 10-byte packets) [1]: 10Router#%MODEM-5-BADMODEMS: Modems (2/3) and (2/1) failed back-to-back test: NOCARRIERRouter# configure terminalRouter(config)# line 28Router(config-line)# modem badRouter(config-line)# endRelated Commands
