-
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
disconnect
To disconnect a line, use the disconnect command in EXEC mode.
disconnect [connection]
Syntax Description
connection
(Optional) Number of the line or name of the active network connection to be disconnected.
Command Modes
EXEC
Command History
Usage Guidelines
Do not disconnect a line to end a session. Instead, log off the host, so that the Cisco IOS software can clear the connection. Then end the session. If you cannot log out of an active session, disconnect the line.
Examples
In the following example, the user disconnects from the device Slab to return to the router:
Slab% disconnectConnection closed by remote hostRelated Commands
dnis (VPDN)
To specify the Dialed Number Identification Service (DNIS) group name or DNIS number of users that are to be forwarded to a tunnel server using a virtual private dialup network (VPDN), use the dnis command in request dial-in VPDN subgroup configuration mode. To remove a DNIS group or number from a VPDN group, use the no form of this command.
dnis {dnis-group-name | dnis-number}
no dnis {dnis-group-name | dnis-number}
Syntax Description
Defaults
Disabled
Command Modes
Request dial-in VPDN subgroup configuration
Command History
Usage Guidelines
You must specify a tunneling protocol using the protocol command in request dial-in VPDN subgroup configuration mode before issuing the dnis command. Removing or changing the protocol command configuration removes any existing dnis command configuration from the request dial-in VPDN subgroup.
You can configure a VPDN group to tunnel multiple DNIS group names and DNIS numbers by issuing multiple instances of the dnis command.
VPDN groups can also be configured to tunnel users based on domain name using the domain command.
Examples
The following example configures a VPDN group to tunnel calls from multiple DNIS numbers and from the domain cisco.com to the tunnel server at 10.1.1.1 using the Layer 2 Forwarding (L2F) protocol:
Router(config)# vpdn-group usersRouter(config-vpdn)# request dialinRouter(config-vpdn-req-in)# protocol l2fRouter(config-vpdn-req-in)# dnis 1234Router(config-vpdn-req-in)# dnis 5678Router(config-vpdn-req-in)# domain cisco.com!Router(config-vpdn)# initiate-to 10.1.1.1Related Commands
dnis group
To include a group of Dialed Number Identification Service (DNIS) numbers in a customer profile, use the dnis group command in customer profile configuration mode. To remove a DNIS group from a customer profile, use the no form of this command.
dnis group {default | name dnis-group-name}
no dnis group {default | name dnis-group-name}
Syntax Description
Defaults
No DNIS groups are associated with a customer profile.
Command Modes
Customer profile configuration
Command History
Usage Guidelines
Use the dnis group customer profile configuration command to include a group of DNIS numbers in a customer profile or discriminator.
Examples
The following example includes the DNIS group called customer1dnis in the customer1 customer profile:
resource-pool profile customer customer1dnis group customer1dnisRelated Commands
dialer dnis group
Creates a DNIS group.
resource-pool profile customer
Creates a customer profile.
domain
To specify the domain name of users that are to be forwarded to a tunnel server using a virtual private dialup network (VPDN), use the domain command in request dial-in VPDN subgroup configuration mode. To remove a domain from a VPDN group or subgroup, use the no form of this command.
domain domain-name
no domain [domain-name]
Syntax Description
Defaults
Disabled
Command Modes
Request dial-in VPDN subgroup configuration
Command History
12.0(4)XI
This command was introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0(5)T.
Usage Guidelines
You must specify a tunneling protocol using the protocol command in request dial-in VPDN subgroup configuration mode before issuing the domain command. Removing or changing the protocol command configuration removes any existing domain command configuration from the request dial-in VPDN subgroup.
You can configure a request dial-in VPDN subgroup to tunnel calls from multiple domain names by issuing multiple instances of the domain command.
VPDN groups can also be configured to tunnel users based on Dialed Number Identification Service (DNIS) group names or DNIS numbers using the dnis command.
Examples
The following example configures VPDN group 1 to request a dial-in Layer 2 Tunnel Protocol (L2TP) tunnel to IP address 10.99.67.76 when it receives a PPP call from a username with the domain name cisco1.com, the domain name cisco2.com, or the DNIS number 4321:
Router(config)# vpdn-group 1Router(config-vpdn)# request-dialinRouter(config-vpdn-req-in)# protocol l2tpRouter(config-vpdn-req-in)# domain cisco1.comRouter(config-vpdn-req-in)# domain cisco2.comRouter(config-vpdn-req-in)# dnis 4321!Router(config-vpdn)# initiate-to ip 10.99.67.76Related Commands
ds0 busyout (channel)
To busyout one or more digital signal level 0s (DS0s), use the ds0 busyout command in controller configuration mode. To cancel busyout on a DS0, use the no form of this command.
ds0 busyout ds0
no ds0 busyout ds0
Syntax Description
ds0
DS0 number listed as a single channel or channel range. The range of numbers can be from 1 to 24 for T1. For example, from 1 to 10, or from 10 to 24.
Defaults
Disabled
Command Modes
Controller configuration
Command History
Usage Guidelines
Use the ds0 busyout command when you to busyout a one or more DS0s (channels). If there is an active call, the software waits until the call terminates by a disconnection; then the DS0 is busied out. First you must specify the T1 line (port) containing the 24 DS0s, using the controller T1 command.
To busyout all DS0s on a trunk card or all modems on a modem card, use the busyout privileged EXEC command.
To display the busyout information, use the show busyout privileged EXEC command.
Note
The ds0 busyout command only applies to cas-group command configurations for channel-associated signaling. This command has no effect on pri-group command configurations.
Examples
In this example, the controller T1 is configured with cas-group (channel-associated signaling). The following example removes DS0s 1 through 10 from dialup services. These DS0s are assigned to the T1 port (line) in shelf 6, slot 0, port 0:
controller t1 6/0/0ds0 busyout 1-10exitRelated Commands
ds0 busyout-threshold
To define a threshold to maintain a balance between the number of DS0s and modems, use the ds0 busyout-threshold command in global configuration mode. To remove the threshold, use the no form of this command.
Cisco AS5300 and AS5800 Access Servers Only
ds0 busyout-threshold threshold-number
no ds0 busyout-threshold threshold-number
Note
Syntax Description
threshold-number
Number of modems that are free when the router should enforce the stipulation that the number of free DS0 lines is less than or equal to the number of modems.
Command Modes
Global configuration
Command History
11.3(2)AA
This command was introduced as modem busyout-threshold.
12.2
This command was changed to ds0 busyout-threshold for the Cisco AS5300 and AS5800 access servers.
Usage Guidelines
The ds0 busyout-threshold command functionality is also often termed autobusyout. This command applies to all DS0 lines coming into the router and counts all free modems in all pools.
The ds0 busyout-threshold command periodically checks to see if the number of free modems is less that the user specified threshold and if it is it ensures the number of free DS0 channels is less than or equal to the number of modems.
This command should only be used where excess calls to one router are forwarded by the exchange to an additional router on the same exchange group number.
Since the ds0 busyout-threshold command checks only periodically, the threshold should be greater than the number of calls the user expects to receive in 1 minute plus a safety margin. For example, if the user receives an average of 10 calls per minute, then a threshold of 20 would be advised. Very small thresholds should be avoided since they do not allow sufficient time for the exchange to respond to out-of-service notifications from the router, and callers may receive busy signals when free modems are all used.
Caution
On T3 controllers, any contained T1 controllers that are not in use should be undeclared to remove them from the autobusyout list.
Examples
The following example shows how you might configure the ds0 busyout-threshold command:
ds0 busyout-threshold 30Related Commands
ds0-group (controller e1)
To define E1 channels for compressed voice calls and the channel-associated signaling (CAS) method by which the router connects to the PBX or PSTN, enter the ds0-group command in controller configuration mode. To remove the group and signaling setting, use the no form of this command.
ds0-group channel timeslots range type signal
no ds0-group channel timeslots range type signal
Syntax Description
Defaults
No channel-associated signaling is configured on the controller. All R2 signaling types have DNIS turned on by default.
Command Modes
Controller configuration
Command History
Usage Guidelines
Use this command to configure support for incoming and outgoing call signals (such as on-hook and off-hook) on each E1 controller.
If you specify the time-slot range 1-31, the system software automatically uses the sixteenth time slot to transmit the channel-associated signaling.
The signaling you configure on the access server must match the signaling used by the central office. For example, if the central office switch is forwarding R2 analog signaling to a Cisco 2600 or 3600 series router, the E1 controller on the router must also be configured for R2 analog signaling (r2-analog).
All R2 signaling options have DNIS support turned on by default. If you enable the ani option, the collection of DNIS information is still performed. Specifying the ani option does not disable DNIS. DNIS is the number being called. ANI is the caller's number. For example, if you are configuring router A to call router B, the DNIS number is router B and the ANI number is router A. ANI is very similar to Caller ID.
To customize the R2 signaling parameters, refer to the cas-custom controller configuration command. When you enable the ds0-group command, the cas-custom command is automatically set up to be polled for configuration information. However, unless you enable or turn on specific features with the ds0-custom command, the cas-custom feature has an empty set of signaling parameters.
DNIS is automatically collected for modem pools and R2 tone signaling. You do not need to specify the collection of DNIS information with the ds0-group command. However, if you are using non-R2 tone signaling, the system must be manually configured to collect DNIS information. For non-R2 CAS signaling, DNIS collection is done only for E&M-fgb.
Examples
In most cases, you will configure the same channel-associated signaling on each E1 controller. The following examples configure signaling and customized parameters on controller E1 2 using the ds0-group and cas-custom controller configuration commands.
The actual channel-associated signaling is configured on the sixteenth time slot, which is the reason why this time slot does not come up in the following output.
Router(config)# controller e1 2Router(config-controller)# ds0-group 1 timeslots 1-31 type r2-digital r2-compelled aniRouter(config-controller)#%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 1 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 2 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 3 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 4 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 5 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 6 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 7 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 8 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 9 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 10 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 11 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 12 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 13 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 14 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 15 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 17 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 18 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 19 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 20 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 21 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 22 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 23 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 24 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 25 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 26 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 27 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 28 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 29 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 30 is up%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 31 is upThe following example shows all the supported E1 signaling types on a Cisco 2600 or 3600 series router.
Router(config-controller)# ds0-group 1 timeslots 1-31 type ?e&m-fgb E & M Type II FGBe&m-fgd E & M Type II FGDe&m-immediate-start E & M Immediate Startfxs-ground-start FXS Ground Startfxs-loop-start FXS Loop Startp7 P7 Switchr2-analog R2 ITU Q411r2-digital R2 ITU Q421r2-pulse R2 ITU Supplement 7sas-ground-start SAS Ground Startsas-loop-start SAS Loop StartRouter(config-controller)# cas-group 1 timeslots 1-31 type r2-analog ?r2-compelled R2 Compelled Register Signallingr2-non-compelled R2 Non Compelled Register Signallingr2-semi-compelled R2 Semi Compelled Register Signalling<cr>R2 signaling parameters can be customized with the cas-custom controller configuration command:
Router(config-controller)# cas-custom 1Router(config-ctrl-cas)# ?CAS custom commands:caller-digits Digits to be collected before requesting CallerIDcategory Category signalcountry Country Namedefault Set a command to its defaultsexit Exit from cas custom modeinvert-abcd invert the ABCD bits before tx and after rxmetering R2 network is sending metering signalnc-congestion Non Compelled Congestion signalno Negate a command or set its defaultsencapsulation cpp
Note
To enable encapsulation for communication with routers or bridges using the Combinet Proprietary Protocol (CPP), use the encapsulation cpp command in interface configuration mode. To disable CPP encapsulation, use the no form of this command.
encapsulation cpp
no encapsulation cpp
Syntax Description
This command has no arguments or keywords.
Defaults
CPP encapsulation disabled.
Command Modes
Interface configuration
Command History
11.2
This command was introduced.
12.3(4)T
This command was removed and is no longer available in Cisco IOS software.
Usage Guidelines
Use this command to communicate over an ISDN interface with Cisco 700 and 800 series (formerly Combinet) routers that do not support PPP but do support CPP.
Most Cisco routers support PPP. Cisco routers can communicate over ISDN with these devices by using PPP encapsulation, which supports both routing and fast switching.
The Cisco 700 and 800 series routers support only IP, IPX, and bridging. For AppleTalk, these Cisco routers automatically perform half-bridging.
This command is supported on ISDN BRIs and PRIs only.
Examples
The following example configures BRI interface 0 to communicate with a router or bridge that does not support PPP:
interface bri 0encapsulation cppcpp callback acceptcpp authenticationThe following example configures PRI serial interface 1/1:23 to communicate with a router or bridge that does not support PPP:
controller t1 1/1framing esflinecode b8zspri-group timeslots 1-23isdn switchtype primary-4ess!interface Serial1/1:23encapsulation cppcpp callback accept cpp authenticationRelated Commands
encryption mppe
To enable Microsoft Point-to-Point Encryption (MPPE) on an Industry-Standard Architecture (ISA) card, use the encryption mppe command in controller configuration mode. To disable MPPE, use the no form of this command.
encryption mppe
no encryption mppe
Syntax Description
This command has no arguments or keywords.
Command Default
IPSec is the default encryption type.
Command Modes
Controller configuration
Command History
12.0(5)XE5
This command was introduced.
12.1(5)T
This command was integrated into Cisco IOS Release 12.1(5)T.
Usage Guidelines
Using the ISA card offloads MPPE from the Route Processor and will improve performance in large-scale environments.
The router must be rebooted for the change to the encryption mppe command configuration to take effect.
Examples
The following example enables MPPE encryption on the ISA card in slot 5, port 0:
Router(config)# controller isa 5/0Router(config-controller)# encryption mppeRelated Commands
debug ppp mppe
Displays debug messages for MPPE events.
encryption mppe
Enables MPPE encryption on the virtual template.
show ppp mppe
Displays MPPE information for an interface.
failover group-number
To configure shelf redundancy for Cisco AS5800 universal access servers, use the failover group-number command in redundancy configuration mode. To disable redundancy, use the no form of this command.
failover group-number group-code
no failover group-number group-code
Syntax Description
Defaults
Redundancy is not enabled.
Command Modes
Redundancy configuration
Command History
12.1(5)XV1
This command was introduced.
12.2(11)T
This command was integrated into Cisco IOS Release 12.2(11)T.
Usage Guidelines
This command must be configured on both router shelves. The group-code argument is used by the system controller and must be the same for both router shelves forming the redundant pair.
For successful failover to occur, both router-shelf configurations must be synchronized. Configure each router shelf separately, as active and backup respectively, with the same configuration except for the IP address on egress interfaces.
Note
Examples
The following example assigns the configured router shelf to the redundancy pair designated as 25. These commands must be issued on both router shelves in the redundant router-shelf pair:
Router(config)# redundancyRouter(config-red)# failover group-number 25Related Commands
redundancy
Enters redundancy mode for further configuration.
show redundancy
Displays current or historical status and related information and displays shelf-redundancy status.
firmware location
To download firmware into the modems, use the firmware location command in Service Processing Element (SPE) configuration mode. To revert the router to the system embedded image default, use the no form of this command.
firmware location [IFS:[/]]filename
no firmware location
Syntax Description
Defaults
Downloads SPE firmware in Flash memory.
Command Modes
SPE configuration
Command History
Usage Guidelines
Use the firmware location SPE configuration command to download firmware into your modems. This command specifies the location of the firmware file and downloads the firmware in the range of SPEs specified, depending on the states configured by the firmware upgrade command. Use the firmware location command with the firmware upgrade command. The entire SPE is affected by the firmware location command.
The latest SPE firmware image can usually be retrieved from Cisco.com. You must first copy the SPE image from a TFTP server to Flash memory using the copy tftp flash command.
The firmware location command is a configuration command and must be saved into the system configuration using the write memory command; otherwise, at the next reboot downloading of the specified firmware will not occur.
The firmware location command was first supported in Cisco IOS Release 12.0(4)XI1. For earlier images, use the copy command. For the Cisco IOS Release 12.0(4)XI1 images, the copy flash modem command is disabled for MICA technologies modems and newer versions of the 56-kbps Microcom modems. The older V.34 Microcom modems still use the copy command for downloading in Cisco IOS Release 12.0(4)XI1 images.
Note
You cannot use the firmware location command on SPEs that are in the Bad state.Examples
The following example shows how to display all legal IFSs:
router# dir all-filesystemsDirectory of nvram:/121 -rw- 1543 <no date> startup-config122 ---- 5 <no date> private-config126968 bytes total (125368 bytes free)Directory of system:/6 dr-x 0 <no date> memory1 -rw- 2929 <no date> running-config2 dr-x 0 <no date> ucode17 dr-x 0 <no date> vfilesNo space information availableDirectory of flash:/1 -rw- 12575032 <no date> c5300-js-mz.122-11.T16777216 bytes total (4202120 bytes free)Directory of bootflash:/1 -rw- 1155864 <no date> c5300-boot-mz.113-10.T.bin2 -rw- 381540 <no date> mica-modem-pw.2.6.2.0.bin3 -rw- 384056 <no date> pw2621.ios8388608 bytes total (5682340 bytes free)Directory of lex:/No files in directoryNo space information availableThe following example shows how to enter the SPE configuration mode, set the range of SPEs, specify the firmware file location in Flash memory, download the file to the SPEs, and display a status report using the show spe EXEC command:
router# configure terminalrouter(config)# spe 7/0 7/17router(config-spe)# firmware location flash:np_6_75Router(config-spe)# firmware upgrade busyoutStarted downloading firmware flash:np_6_75.sperouter(config-spe)# exitrouter# show spe 7...SPE SPE SPE SPE Port CallSPE# Port # State Busyout Shut Crash State Type7/00 0000-0005 ACTIVE 1 0 0 BBBBBB ______7/01 0006-0011 DOWNLOAD 1 0 0 bbbbbb ______7/02 0012-0017 DOWNLOAD 1 0 0 bbbbbb ______7/03 0018-0023 DOWNLOAD 1 0 0 bbbbbb ______...The following configuration example specifies a firmware file located in Flash memory:
spe 1/0 1/8firmware location np-spe-upw-1.0.1.2.binThe following configuration example shows how to download firmware that is not bundled with the Cisco IOS image:
spe 1/2 1/4firmware location flash:portware.2620.iosThe following configuration example shows how to download firmware that is bundled with the Cisco IOS image:
spe 2/9 2/9firmware location system:/ucode/microcom_firmwareRelated Commands
firmware upgrade
To modify the way in which the service processing element (SPE) will be downloaded, use the firmware upgrade command in SPE configuration mode. To revert to the default SPE firmware upgrade option, busyout, use the no form of this command.
firmware upgrade {busyout | recovery | reboot}
no firmware upgrade
Cisco AS5350, Cisco AS5400, and Cisco AS5800
firmware upgrade [busyout | download-maintenance | reboot]
Syntax Description
Defaults
An upgrade occurs when all calls are terminated on the SPE (busyout).
For the Cisco AS5350, Cisco AS5400, and Cisco AS5800 there is no default.Command Modes
SPE configuration
Command History
Usage Guidelines
Three methods of upgrade are available: busyout, reboot, and download-maintenance or recovery.
The reboot keyword requests the Cisco access servers to upgrade SPE firmware at the next reboot.
The busyout keyword upgrades SPE firmware after waiting for all calls to be terminated on an SPE.
The download-maintenance or recovery keyword requests SPE firmware download during maintenance time.
Use this command in conjunction with the firmware location command and the spe download maintenance command.
The SPE firmware location command is designed to integrate all continuous ranges of SPEs containing the same firmware location. However, the firmware upgrade command does not affect the ranges of SPEs. As such, all SPEs within the ranges of SPEs must have the same firmware upgrade mode or the router uses the default upgrade mode to busyout state. If you want to upgrade a single SPE within an existing range of SPEs with a different upgrade mode than is currently configured, you must first change the upgrade mode for the entire range of SPEs and then change the firmware location for the specific SPE being upgraded. Furthermore, each time you merge ranges of SPEs due to configuration changes, verify that the configuration of the SPE firmware upgrade remains effective to what is desired.
Examples
The following example sets the SPEs and specifies the firmware upgrade to take place once all calls are terminated on the SPE:
Router(config)# spe 1/03Router(config-spe)# firmware location np-spe-upw-1.0.1.2.binRouter(config-spe)# firmware upgrade busyoutIf the busyout upgrade command is specified, or if no upgrade mode is specified, the SPE modems are set into a "pending download" state when you use the firmware location command on the specified SPE. The pending download state prevents any modem in that state to be allocated for new calls until the state is cleared. Modems with active calls remain active for their call durations, but enter the pending download state when they terminate. This pending download state can be cleared only when the SPE is finally downloaded. When all modems within the SPE are in the pending download state and no active calls remain on the SPE, the SPE is reloaded. The busyout option is the fastest way to upgrade modems on an active router but can severely impact the capacity of the router during the upgrade. The following example sets the default option for the firmware upgrade process:
Router(config-spe)# firmware upgrade busyoutIf reboot upgrade is specified, the SPE modems are not reloaded to the new firmware location until the router is rebooted. The reboot upgrade option is useful for routers that need to have their SPE upgraded and that also will be rebooted for maintenance. When the new firmware is configured, the configuration takes effect after the reboot takes place. The following example sets the firmware upgrade reboot:
Router(config-spe)# firmware upgrade rebootIf recovery upgrade is specified, the SPE modems are reloaded based on the modem recovery algorithm. Only when no active calls exist on the SPE does the firmware download take place. Furthermore, at the time configured with the modem recovery maintenance command, the modem recovery maintenance process attempts, in a controller fashion, to reload the modems by busying out the modems for a window duration of time to make the download take place. Refer to the modem recovery documentation for more information. The recovery upgrade option upgrades modems on an active router with the least impact. Capacity is kept at a maximum. However, this option may take a few days for all modems to be reloaded to the new firmware location. The following example sets the system for a firmware upgrade recovery:
Router(config-spe)# firmware upgrade recoveryFor the Cisco AS5350, Cisco AS5400, or Cisco AS5800, use the following syntax to set the system for a firmware upgrade recovery:
Router(config-spe)# firmware upgrade download-maintenanceRelated Commands
flowcontrol
To set the method of data flow control between the terminal or other serial device and the router, use the flowcontrol command in line configuration mode. To disable flow control, use the no form of this command.
flowcontrol {none | software [lock] [in | out] | hardware [in | out]}
no flowcontrol {none | software [lock] [in | out] | hardware [in | out]}
Syntax Description
Defaults
Flow control is disabled.
Command Modes
Line configuration
Command History
Usage Guidelines
When software flow control is set, the default stop and start characters are Ctrl-S and Ctrl-Q (XOFF and XON). You can change them with the stop-character and start-character commands.
If a remote Telnet device requires software flow control, the remote system should not be able to turn it off. Using the lock option makes it possible to refuse "dangerous" Telnet negotiations if they are inappropriate.
Examples
The following example sets hardware flow control on line 7:
line 7flowcontrol hardwareRelated Commands
source template
Sets the flow control start character.
stop-character
Sets the flow control stop character.
force-local-chap
To force the L2TP network server (LNS) to reauthenticate the client, use the force-local-chap command in VPDN group configuration mode. To disable reauthentication, use the no form of this command.
force-local-chap
no force-local-chap
Syntax Description
This command has no arguments or keywords.
Defaults
Proxy authentication. The Challenge Handshake Authentication Protocol (CHAP) response to the Layer 2 Transport Protocol access concentrator (LAC) authentication challenge is passed to 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 force-local-chap command. Removing the accept-dialin command will remove the force-local-chap command from the VPDN group.
This command is used only if CHAP authentication is enabled for PPP (using the ppp authentication chap command). This command forces the LNS to reauthenticate the client in addition to the proxy authentication that occurs at the LAC. If the force-local-chap command is used, then the authentication challenge occurs twice. The first challenge comes from the LAC and the second challenge comes from the LNS. Some PPP clients may experience problems with double authentication. If this problem occurs, authentication challenge failures may be seen if the debug ppp authentication command is enabled.
Examples
The following example enables CHAP authentication at the LNS:
vpdn-group 1accept dialinprotocol l2tpvirtual-template 1terminate-from patforce-local-chapRelated Commands
group-range
To create a list of member asynchronous interfaces (associated with a group interface), use the group-range command in interface configuration mode. To remove an interface from the member list, use the no form of this command.
group-range low-end-of-interfacerange high-end-of-interfacerange
no group-range interface
Syntax Description
Defaults
No interfaces are designated as members of a group.
Command Modes
Interface configuration
Command History
Usage Guidelines
Using the group-range command, you create a group of asynchronous interfaces that are associated with a group asynchronous interface on the same device. This group interface is configured by using the interface group-async command. This one-to-many structure allows you to configure all associated member interfaces by entering one command on the group interface, rather than entering this command on each interface. You can customize the configuration on a specific interface by using the member command. Interface numbers can be removed from the interface group using the no group-range command.
Examples
The following example defines interfaces 2, 3, 4, 5, 6, and 7 as members of asynchronous group interface 0:
interface group-async 0group-range 2 7Related Commands
group session-limit
To specify the maximum number of concurrent sessions allowed across all virtual private dialup network (VPDN) groups associated with a particular VPDN template, use the group session-limit command in VPDN template configuration mode. To disable session limiting for a VPDN template, use the no form of this command.
group session-limit number
no group session-limit number
Syntax Description
number
Maximum number of concurrent sessions allowed across all VPDN groups associated with a particular VPDN template. Valid values are from 1 to 32767.
Defaults
No session limit is configured at the VPDN template level.
Command Modes
VPDN template configuration
Command History
12.2(4)B
This command was introduced.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
Usage Guidelines
Use this command to specify the maximum number of concurrent sessions across all VPDN groups associated with a VPDN template. If you configure a group session limit for the default VPDN template, that session limit is the session limit for all VPDN groups not associated with a named VPDN template. The group session limit configured by this command does not terminate active sessions. If you configure a group session limit that is lower than the number of current active sessions, no sessions are terminated and no new sessions can start.
Session limits configured at the VPDN group level by the session-limit (VPDN) command take precedence over session limits configured at the VPDN template level when the VPDN group level session limit has a lower configured value than the VPDN template level.
Examples
The following example shows how to configure 100 as the maximum number of concurrent sessions across all VPDN groups attached to the VPDN template called template1:
vpdn session-limit 100vpdn-template template1group session-limit 100Related Commands
