-
Cisco IOS Dial Technologies Command Reference, Release 12.3
-
Introduction
-
Dial Technologies Commands: A through cas-group
-
Dial Technologies Commands: channel through cpp
-
Dial Technologies Commands: disconnect through H
-
Dial Technologies Commands: initiate through ipx
-
Dial Technologies Commands: isdn all through isdn x25
-
Dial Technologies Commands: L
-
Dial Technologies Commands: M
-
Dial Technologies Commands: N through pptp
-
Dial Technologies Commands: pri through R
-
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 X
-
Table Of Contents
show controllers e1 call-counters
show controllers t1 call-counters
show controllers t1 firmware-status
script activation
To specify that a chat script start on a physical terminal line any time the line is activated, use the script activation command in line configuration mode. To disable this feature, use the no form of this command.
script activation regular-expression
no script activation
Syntax Description
regular-expression
Regular expression that specifies the set of modem scripts that might be executed. The first script name that matches the regular-expression argument will be used.
Defaults
Not assigned to terminal lines
Command Modes
Line configuration
Command History
Usage Guidelines
This command provides an asynchronous handshake to a user or device that activates the line. It can be activated by several events, such as a user issuing a carriage return on a vacant line, by a modem on the line sensing an incoming carrier, or an asynchronous device (such as another router) sending data. Each time an EXEC session is started on a line, the system checks to see if a script activation command is configured on the line. If so, and the regular-expression argument (a regular expression) matches an existing chat script name, the matched script is run on the line. For information about regular expressions, see the appendix "Regular Expressions" in the Cisco IOS Dial Technologies Configuration Guide.
The script activation command can mimic a login handshake of another system. For example, a system that dials into a line on a router and expects an IBM mainframe login handshake can be satisfied with an appropriate activation script.
This command also can send strings to asynchronous devices that are connecting or dialing into a router.
The script activation command functions only on physical terminal (tty) lines. It does not function on virtual terminal lines.
Examples
The following example specifies that the chat script with a name that includes "telebit" will be activated whenever line 4 is activated:
line 4script activation telebitRelated Commands
script arap-callback
To specify that a chat script start on a line any time an AppleTalk Remote Access (ARA) client requests a callback, use the script arap-callback command in line configuration mode. To disable this feature, use the no form of this command.
script arap-callback regular-expression
no script arap-callback
Syntax Description
regular-expression
Regular expression that specifies the set of modem scripts that might be executed. The first script name that matches the regular-expression argument is used.
Defaults
Not assigned to terminal lines
Command Modes
Line configuration
Command History
Usage Guidelines
This command specifies that if an originating ARA client requests callback, the device will be disconnected and the chat script defined by the regular-expression argument will be executed to call back the client. The first available line specified for callback, and for which a chat script has been applied, will be used for the callback.
Create a chat script using the chat script command. The script arap-callback command functions only on physical terminal (tty) lines. It does not function on virtual terminal lines.
Examples
The following example specifies that a chat script with a name that includes usr4 will be activated whenever a client requests a callback on line 4:
line 4script arap-callback usr4Related Commands
script callback
To specify that a chat script start on a line any time a client requests a callback, use the script callback command in line configuration mode. To disable this feature, use the no form of this command.
script callback regular-expression
no script callback
Syntax Description
regular-expression
Regular expression that specifies the set of modem scripts that might be executed. The first script name that matches the regular-expression argument is used.
Defaults
Not assigned to terminal lines
Command Modes
Line configuration
Command History
Usage Guidelines
This command specifies that if an originating client requests callback, the device will be disconnected and the chat script defined by the regular-expression argument will be executed to call back the client. The first available line specified for callback, and for which a chat script has been applied, will be used for the callback. Regular expression characters and strings are described in the appendix "Regular Expressions" at the end of the Cisco IOS Dial Technologies Configuration Guide.
Create a chat script using the chat script command.
The script callback command functions only on physical terminal (tty) lines. It does not function on virtual terminal lines.
Examples
The following example specifies that the chat script with a name that includes supra4 will be activated whenever a client requests a callback on line 4:
line 4script callback supra4Related Commands
script connection
To specify that a chat script will start on a physical terminal line any time a remote network connection is made to a line, use the script connection command in line configuration mode. To disable this feature, use the no form of this command.
script connection regular-expression
no script connection
Syntax Description
regular-expression
Set of modem scripts that can be executed. The first script name that matches the regular-expression argument will be used.
Defaults
Not assigned to terminal lines
Command Modes
Line configuration
Command History
Usage Guidelines
This command provides modem dialing commands and commands for logging onto remote systems. The script connection command functions only on physical terminal (tty) lines. It does not function on virtual terminal lines.
This command can be used to initialize an asynchronous device sitting on a line to which a reverse network connection is made.
For information about regular expressions, see the appendix "Regular Expressions" in the Cisco IOS Dial Technologies Configuration Guide.
Examples
The following example specifies that the chat script with a name that includes "inband" will be activated whenever a remote connection to line 4 is established. The router can send a login string and password to the UNIX server when a network tunneling connection comes into line 4:
line 4script connection inbandUsing this example and the topology in Figure 3, the access server or router can send a login string and password to the UNIX server when a network tunneling connection comes into line 4.
Figure 3 Network Tunneling Connection on an Asynchronous Line
Related Commands
script dialer
To specify a default modem chat script, use the script dialer command in line configuration mode. To disable this feature, use the no form of this command.
script dialer regular-expression
no script dialer
Syntax Description
regular-expression
Set of modem scripts that can be executed. The first script that matches the regular-expression argument will be used.
Defaults
No chat script is defined.
Command Modes
Line configuration
Command History
Usage Guidelines
This command is used by DDR modules to provide modem dialing commands and commands to log in to remote systems.
The regular-expression argument is used to specify the name of the modem script that is to be executed. The first script that matches the argument in this command and the dialer map command will be used. For information about regular expressions, see the appendix "Regular Expressions" in the Cisco IOS Dial Technologies Configuration Guide.
If you adhere to the naming convention recommended for chat scripts (see the chat-script command), the modem lines (the regular-expression argument in the script dialer command) will be set to one of the following regular expressions to match patterns, depending on the kind of modem you have:
•
codex-.*
•
•
•
In the dialer map command, you can specify the modulation but leave the type of modem unspecified, as in .*-v32bis.
Examples
The following example shows line chat scripts being specified for lines connected to Telebit and US Robotics modems:
! Some lines have telebit modemsline 1 6script dialer telebit.*!! Some lines have US robotics modemsline 7 12script dialer usr.*Related Commands
script reset
To specify that a chat script will start on a physical terminal line any time the specified line is reset, use the script reset command in line configuration mode. To disable this feature, use the no form of this command.
script reset regular-expression
no script reset
Syntax Description
regular-expression
Set of modem scripts that might be executed. The first script name that matches the regular-expression argument will be used.
Defaults
Not assigned to terminal lines.
Command Modes
Line configuration
Command History
Usage Guidelines
Chat scripts provide modem dialing commands and commands for logging onto remote systems. Use this command to reset a modem attached to a line every time a call is dropped.
The script reset command functions only on physical terminal (tty) lines. It does not function on virtual terminal lines.
For information about regular expressions, see the appendix "Regular Expressions" in the Cisco IOS Dial Technologies Configuration Guide.
Examples
The following example specifies that any chat script name with the word "linebackup" in it will be activated any time line 7 is reset:
line 7script reset linebackupThe following example resets a modem sitting on a line each time a call is dropped:
chat-script drop-line ""+++"" " " ATH OK "ATS0=1" OK "ATS9=21"line 4script reset drop-lineRelated Commands
script startup
To specify that a chat script will start on a physical terminal line any time the router is powered up, use the script startup command in line configuration mode. To disable this feature, use the no form of this command.
script startup regular-expression
no script startup
Syntax Description
regular-expression
Set of modem scripts that might be executed. The first script that matches the regular-expression argument will be used.
Defaults
Not assigned to terminal lines
Command Modes
Line configuration
Command History
Usage Guidelines
Use this command to initialize asynchronous devices connected to a line when the router is started up or reloaded. You can also use it to start up a banner other than the default banner on lines. The script startup command functions only on physical terminal (tty) lines. It does not function on virtual terminal lines.
For information about regular expressions, see the appendix "Regular Expressions" in the Cisco IOS Dial Technologies Configuration Guide.
Examples
The following example specifies that a chat script with the word "linestart" in its name will be activated whenever line 5 is started up:
line 5script startup linestartRelated Commands
session-limit (VPDN)
To limit the number of sessions that are allowed through a specified virtual private dialup network (VPDN) group, use the session-limit command in VPDN group configuration mode. To remove a configured session limit restriction, use the no form of this command.
session-limit number
no session-limit number
Syntax Description
number
Specifies the number of sessions allowed through a specified VPDN group. The number of sessions can range from 0 to 32767.
Defaults
No default behavior or values.
Command Modes
VPDN group configuration
Command History
Usage Guidelines
Use this command to limit the number of allowed sessions for a specified VPDN group. If the session-limit command is configured to 0, no sessions are allowed on the VPDN group.
This command works independently from the session-limit command used in global configuration mode. Using the session-limit command in global configuration mode, you can restrict the total number of sessions allowed on all VPDN groups. VPDN group session limiting is configured in VPDN group configuration mode.
Global VPDN session limiting and VPDN group session limiting work independently, but global VPDN session limiting is enforced before individual VPDN group limiting. For example, if you apply the vpdn session-limit 2 command in global configuration mode and the session-limit 3 command in VPDN group configuration mode to the VPDN group named group1, no more than two calls are allowed in the VPDN group group1.
Examples
The following example creates a VPDN group named scoot, creates virtual template 5, and restricts the VPDN group group1 to three sessions:
Router(config)# vpdn-group group1Router(config-vpdn)# accept dialinRouter(config-vpdn-acc-in)# protocol l2tpRouter(config-vpdn-acc-in)# virtual-template 5Router(config-vpdn-acc-in)# exitRouter(config-vpdn)# terminate-from hostname host1Router(config-vpdn)# session-limit 3Related Commands
sgbp dial-bids
To allow the stack group to bid for dialout connection, use the sgbp dial-bids command in global configuration mode. To disable this function, use the no form of this command.
sgbp dial-bids
no sgbp dial-bids
Syntax Description
This command has no arguments or keywords.
Defaults
The stack group bid function is disabled by default.
Command Modes
Global configuration
Command History
Examples
The following example shows how to configure a stack group for large-scale dialout:
sgbp group foreversgbp member NAS2 172.21.17.17sgbp dial-bidsRelated Commands
sgbp group
To define a named stack group and make this router a member of that stack group, use the sgbp group command in global configuration mode. To remove the definition, use the no form of this command.
sgbp group name
no sgbp group
Syntax Description
Defaults
Disabled. No stack group name is provided.
Command Modes
Global configuration
Command History
Usage Guidelines
Define the same stack group name across all the stack members.
Examples
The following example makes this system a member of the stack group named "stackq":
sgbp group stackqRelated Commands
sgbp member
To specify the host name and IP address of a router or access server that is a peer member of a stack group, use the sgbp member command in global configuration mode. To remove the member association, use the no form of this command.
sgbp member peer-name [peer-ip-address]
no sgbp member peer-name
Syntax Description
Defaults
Disabled. When enabled, names and IP addresses of peer routers or access servers in the stack group are not provided.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to specify the names of peer hosts (other hosts, not the one being configured) in the specified stack group after you have entered the sgbp dial-bids command.
Examples
The following example configures the current router to recognize the three routers (west, east, and south) as peer members of the stack group named "mystackgroup":
sgbp group mystackgroupsgbp member west 10.69.5.2sgbp member east 172.16.6.3sgbp member south 192.168.15.4Related Commands
sgbp ppp-forward
To enable forwarding of PPP calls—in addition to Multilink PPP (MLP) calls—to the winner of the Stack Group Bidding Protocol (SGBP) bid, use the sgbp ppp-forward command in global configuration mode. To return to the default state, use the no form of this command.
sgbp ppp-forward
no sgbp ppp-forward
Syntax Description
This command has no arguments or keywords.
Defaults
Only Multilink PPP calls are forwarded.
Command Modes
Global configuration
Command History
Usage Guidelines
When this command is enabled, both PPP and Multilink PPP calls are projected to the winner of the SGBP bid.
Examples
The following partial example enables forwarding of PPP calls, as well as MLP calls, to the winner of the SGBP bidding:
sgbp ppp-forwardRelated Commands
sgbp protocol
To set a specific tunneling protocol to use for Stack Group Bidding Protocol (SGBP), use the sgbp protocol command in global configuration mode. To change this command back to its default, use the no form of this command.
sgbp protocol {any | l2f | l2tp}
no sgbp protocol
Syntax Description
Defaults
The any keyword is the default, which allows L2TP and L2F to be offered by a stack group member when bidding on a call, and allows bids with either L2TP or L2F to be accepted by the stack group member on which the call arrived.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is needed when both routers support both L2F and L2TP, but there is a preference that L2F be used between the stack group members instead of L2TP.
Note
Examples
The following example shows how to configure a stack group for large-scale dialout and set L2F as the tunneling protocol:
sgbp group foreversgbp member NAS2 172.21.17.17sgbp dial-bidssgbp protocol l2fRelated Commands
sgbp seed-bid
To set the bidding level that a stack group member can bid with for a bundle, use the sgbp seed-bid command in global configuration mode. To return to the default state, use the no form of this command.
sgbp seed-bid {default | offload | forward-only | bid}
no sgbp ppp-forward
Syntax Description
Defaults
The default keyword; no bid-level integer value is set.
Command Modes
Global configuration
Command History
Usage Guidelines
In the case of equivalent stack group members stacked to receive calls in a rotary group across multiple PRIs, use the sgbp seed-bid default command across all stack members. The stack member that receives the first call for a certain user always wins the bid and hosts the master bundle interface. All subsequent calls to the same user received by another stack member will project to this stack member. If the multiple calls come in concurrently over multiple stack members, the SGBP tie-breaking mechanism will break the tie.
To leverage the relative higher power of one stack member over another, you can set the designated stack member (of higher CPU power) as offload server with the sgbp seed-bid offload command. The bid that is sent is the precalibrated per-platform bid approximating the CPU power, minus the bundle load. In this case, the offload server hosts the master bundle. All calls from other stack members get projected to this stack member. One or more offload servers can be defined—if the bids are equal, the SGBP tie-breaking mechanism will break the tie.
The interfaces that received the calls are projected to the master bundle interface and are considered children of the master bundle interface for the call. See the output of the show ppp multilink command for an example of master bundle interface (shown as "Master link") and the children of it.
You can also manually designate bid values with the sgbp seed-bid command. This value overrides the default or offload setting. The bid sent out is the user-configured value minus the bundle load. The bundle load is defined as the number of active bundles on the stack member. In effect, the more current active bundles on a router, the lower its bid for an additional bundle.
If you have assorted or exactly the same platforms and for some reason want to designate one or more as offload servers, you can manually set the bid value to be significantly higher than the rest. For example, you might use the sgbp seed-bid 9999 command. To determine the initial bid value associated with your particular platform, use the show sgbp command. This method allows you to manually designate the bid values when you have assorted platforms and want to designate one or more platforms as offload servers; for example, one Cisco 4700 (given the highest seed-bid), two Cisco 4000s and one Cisco 7000.
To check the bid value currently assigned on the system, use the show sgbp queries command.
Examples
The following example sets the SGBP bidding level to forward-only:
sgbp seed-bid forward-onlyRelated Commands
shelf-id
To change the shelf number assigned to the router shelf or dial shelf on the Cisco AS5800, use the shelf-id command in global configuration mode. To return the shelf numbers to the default value, use the no form of this command.
shelf-id number {router-shelf | dial-shelf}
no shelf-id number
Syntax Description
number
Number to assign to the shelf. Range is from 0 to 9999.
router-shelf
Specified number to the router shelf.
dial-shelf
Specified number to the dial shelf.
Defaults
The default shelf number for the router shelf is 0.
The default shelf number for the dial shelf is 1, or one number higher than the specified router shelf number.
Command Modes
Global configuration
Command History
Usage Guidelines
The shelf number is used to distinguish between cards on the router shelf and cards on the dial shelf.
Caution
You can specify the shelf number through the setup facility during initial configuration of the
Cisco AS5800. This is the recommended method to specify shelf numbers.To display the shelf numbers, use the show running-config command. If a shelf number has been changed, the pending change is shown in the output of the show version command (for example, the dial-shelf ID is 87; will change to 2 on reload).
Examples
The following example shows how to assign 456 as the dial shelf number:
shelf-id 456 dial-shelfRelated Commands
show version
Displays the configuration of the system hardware, the software version, the names and sources of configuration files, and the boot images.
show async status
To display the status of activity on all lines configured for asynchronous support, use the show async status command in privileged EXEC mode.
show async status
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The display resulting from this command shows all asynchronous sessions, whether they are using Serial Line Internet Protocol (SLIP) or PPP encapsulation.
Examples
The following is sample output from the show async status command:
Router# show async statusAsync protocol statistics:Rcvd: 5448 packets, 7682760 bytes1 format errors, 0 checksum errors, 0 overrun, 0 no bufferSent: 5455 packets, 7682676 bytes, 0 droppedTty Local Remote Qd InPack OutPac Inerr Drops MTU Qsz1 192.168.7.84 Dynamic 0 0 0 0 0 1500 10* 3 192.168.7.98 None 0 5448 5455 1 0 1500 10Table 22 describes the significant fields shown in the display.
show busyout
To display the busyout status for a card on the dial shelf, use the show busyout command in privileged EXEC mode.
show busyout shelf[/slot[/port]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the busyout EXEC command or the ds0 busyout controller command to configure modem busyout.
Examples
The following is sample output from the show busyout command for a trunk card in slot 4 located in dial shelf 1, with busyout pending:
Router# show busyout 1/4Controller t1 busyout status:(s - static d - dynamic p - pending)1/4/0 :ppppppppppppppppppppppp.1/4/1 :sssssssssssssssssssssss.1/4/2 :ppppppppppppppppppppppp.1/4/3 :ddddddddddddddddddddddd.1/4/4 :ppppppppppppppppppppppp.1/4/5 :ppppppppppppppppppppppp.1/4/6 :ppppppppppppppppppppppp.1/4/7 :sssssssssssssssssssssss.1/4/8 :ppppppppppppppppppppppp.1/4/9 :ppppppppppppppppppppppp.1/4/10 :ddddddddddddddddddddddd.1/4/11 :ppppppppppppppppppppppp.Router#See Table 23 to further interpret the display.
The following is sample output from the show busyout command for a modem card in shelf 1, slot 9, and indicates the busyout is complete:
Router# show busyout 1/9Slot 1/9: Busyout (no calls remaining)The following is sample output from the show busyout command, the busyout command, the ds0 busyout command, and another show busyout command:
Router# show busyout 1/0Controller t1 busyout status:(s - static d - dynamic p - pending)1/0/0 :ppppppppppppppppppppppp.1/0/1 :ppppppppppppppppppppppp.1/0/2 :ppppppppppppppppppppppp.1/0/3 :ddddddddddddddddddddddd.1/0/4 :ppppppppppppppppppppppp.1/0/5 :ppppppppppppppppppppppp.1/0/6 :ppppppppppppppppppppppp.1/0/7 :sssssssssssssssssssssss.1/0/8 :ppppppppppppppppppppppp.1/0/9 :ppppppppppppppppppppppp.1/0/10 :ddddddddddddddddddddddd.1/0/11 :ppppppppppppppppppppppp.Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router (config)# controller t1 1/0/1Router (config-controller)# busyoutRouter (config-controller)# ds0 busyout 15-24Router (config-controller)# endRouter# show busyout 1/0Controller t1 busyout status:(s - static d - dynamic p - pending)1/0/0 :ppppppppppppppppppppppp.1/0/1 :sssssssssssssssssssssss.1/0/2 :ppppppppppppppppppppppp.1/0/3 :ddddddddddddddddddddddd.1/0/4 :ppppppppppppppppppppppp.1/0/5 :ppppppppppppppppppppppp.1/0/6 :ppppppppppppppppppppppp.1/0/7 :sssssssssssssssssssssss.1/0/8 :ppppppppppppppppppppppp.1/0/9 :ppppppppppppppppppppppp.1/0/10 :ddddddddddddddddddddddd.1/0/11 :ppppppppppppppppppppppp.Table 23 describes the significant fields shown in the show busyout displays.
