|
|
The configuration commands described in this chapter are used to configure modems and modem lines on access servers and routers.
For line configuration information and examples, refer to the "Configuring Modem Support and Asynchronous Devices" chapter in the Dial Solutions Configuration Guide.
To support the extended BOOTP request specified in RFC 1084, and to specify information that will be sent in response to BOOTP requests, use the async-bootp global configuration command. To clear the list, use the no form of this command.
async-bootp tag [:hostname] data| tag | Item being requested; expressed as filename, integer, or IP dotted decimal address. See Table 1 for possible values. |
| :hostname | (Optional) This entry applies only to the specified host. The argument can be either an IP address or a logical host name. |
| data | List of IP addresses entered in dotted decimal notation or as logical host names, a number, or a quoted string. |
| Keyword and Argument Pair | Use |
|---|---|
| bootfile | Server boot file from which to download the boot program. Use the optional :hostname and data arguments to specify the host or hosts. |
| subnet-mask mask | Dotted decimal address specifying the network and local subnetwork mask (as defined by RFC 950). |
| time-offset offset | A signed 32-bit integer specifying the time offset of the local subnetwork in seconds from Coordinated Universal Time. |
| gateway address | Dotted decimal address specifying the IP addresses of gateways for this subnetwork. A preferred gateway should be listed first. |
| time-server address | Dotted decimal address specifying the IP address of time servers (as defined by RFC 868). |
| ien116-server address | Dotted decimal address specifying the IP address of name servers (as defined by IEN 116). |
| dns-server address | Dotted decimal address specifying the IP address of Domain Name Servers (as defined by RFC 1034). |
| log-server address | Dotted decimal address specifying the IP address of an MIT-LCS UDP log server. |
| quote-server address | Dotted decimal address specifying the IP address of Quote of the Day servers (as defined in RFC 865). |
| lpr-server address | Dotted decimal address specifying the IP address of Berkeley UNIX Version 4 BSD servers. |
| impress-server address | Dotted decimal address specifying the IP address of Impress network image servers. |
| rlp-server address | Dotted decimal address specifying the IP address of Resource Location Protocol (RLP) servers (as defined in RFC 887). |
| hostname name | Name of the client (which might or might not be domain qualified, depending upon the site). |
| bootfile-size value | Two-octet value specifying the number of 512 octet (byte) blocks in the default boot file. |
If no extended BOOTP commands are entered, the software generates a gateway and subnet mask appropriate for the local network.
Global configuration
This command first appeared in Cisco IOS Release 10.3.
Each of the tag keyword-argument pairs is a field that can be filled in and sent in response to BOOTP requests from clients.
BOOTP supports the extended BOOTP requests specified in RFC 1084 and works for both SLIP and PPP encapsulation.
Use the show async bootp EXEC command to list the configured parameters. BOOTP works for both SLIP and PPP.
The following example specifies different boot files: one for a PC and one for a Macintosh. With this configuration, a BOOTP request from the host on 192.168.31.1 results in a reply listing the boot filename as pcboot. A BOOTP request from the host named mac results in a reply listing the boot filename as macboot.
async-bootp bootfile :192.168.31.1 "pcboot" async-bootp bootfile :mac "macboot"
The following example specifies a subnet mask of 255.255.0.0:
async-bootp subnet-mask 255.255.0.0
The following example specifies a negative time offset of the local subnetwork of -3600 seconds:
async-bootp time-offset -3600
The following example specifies the IP address of a time server:
async-bootp time-server 192.168.31.1
You can use the master indexes or search online to find documentation of related commands.
service old-slip-prompts
The peer default ip address command replaces the async default ip address command.
Refer to the description of the peer default ip address command for more information.
To enable RIP, OSPF, and IGRP routing protocols on an asynchronous interfaces when using the /routing keyword with the ppp and slip EXEC commands, use the async default routing interface command. To disable this function, use the no form of this command.
async default routingThis command has no arguments or keywords.
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 11.1.
For asynchronous interfaces in interactive mode, the async default routing command causes the ppp and slip EXEC commands to be interpreted as though the /route keyword had been included in the command. For asynchronous interfaces in dedicated mode, the async default routing command turns on the use of routing protocols on the line. Without the async default routing command, there is no way to enable the use of routing protocols automatically on a dedicated asynchronous interface.
The following example enables the use of routing protocols on asynchronous interface 4. In this example, asynchronous interface 4 is dedicated for asynchronous use.
interface async 4 ip address 191.191.191.191 255.255.255.0 async default routing async mode dedicated
You can use the master indexes or search online to find documentation of related commands.
async dynamic routing
async mode dedicated
async mode interactive
ppp
slip
To specify dynamic asynchronous addressing, use the async dynamic address interface configuration command. To disable dynamic addressing, use the no form of this command.
async dynamic addressThis command has no arguments or keywords.
Dynamic addressing is disabled.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
You can control whether addressing is dynamic (the user specifies the address at the EXEC level when making the connection), or whether default addressing is used (the address is forced by the system). If you specify dynamic addressing, the router must be in interactive mode and the user will enter the address at the EXEC level.
It is common to configure an asynchronous interface to have a default address and to allow dynamic addressing. With this configuration, the choice between the default address or a dynamic addressing is made by the user when they enter the slip or ppp EXEC command. If the user enters an address, it is used, and if the user enters the default keyword, the default address is used.
The following example shows dynamic addressing assigned to async interface 6.
interface ethernet 0ip address 10.0.0.1 255.0.0.0interface async 6async dynamic address
You can use the master indexes or search online to find documentation of related commands.
peer default ip address
To allow the use of routing protocols on an interface, use the async dynamic routing interface configuration command. To disable the use of routing protocols, use the no form of this command.
async dynamic routingThis command has no arguments or keywords.
Dynamic routing is disabled.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
The use of routing protocols is further controlled by the use of the /routing keyword in the slip and ppp EXEC command.
The following example shows how to enable asynchronous routing on async interface 6. The ip tcp header-compression passive command enables Van Jacobson TCP header compression and prevents transmission of compressed packets until a compressed packet arrives from the asynchronous link.
interface async 6 async dynamic routing async dynamic address async default ip address 10.11.14.2 ip tcp header-compression passive ip unnumbered ethernet 0
You can use the master indexes or search online to find documentation of related commands.
async dynamic address
ip tcp header-compression
To configure the Cisco IOS software to automatically execute a command when a user connects to a particular line, use the autocommand line configuration command.
autocommand command| command | Any appropriate EXEC command, including the host name and any switches that occur with the EXEC command. |
No commands are configured to automatically execute.
Line configuration
This command first appeared in Cisco IOS Release 10.0.
This command enables you to automatically execute an EXEC command when a user connects to a line.
The following example forces an automatic connection to a host named host21 (which could be an IP address):
line vty 4 autocommand connect host21
To configure automatic line disconnect, use the autohangup line configuration command. This command causes the EXEC to issue the exit command when the last connection closes.
autohangupThis command has no arguments or keywords.
Disabled
Line configuration
This command first appeared in Cisco IOS Release 10.0.
This command is useful for UNIX UUCP applications that automatically disconnect lines because UUCP scripts cannot issue the exit command to hang up the telephone.
The following example enables automatic line disconnect on lines 5 through 10:
line 5 10 autohangup
To return a terminal line to idle state, use the clear line EXEC command.
clear line line-number| line-number | Absolute line number. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
Use this command to log out of a specific session running on another line. If the line uses a modem, the modem will be disconnected.
In the following example, line 3 is reset to idle state:
clear line 3
To allow an EXEC process on a line, use the exec line configuration command. Use the no form of this command to turn off the EXEC process for the specified line.
execThis command has no arguments or keywords.
The EXEC processes start is activated automatically on all lines.
Line configuration
This command first appeared in Cisco IOS Release 10.0.
When you want to allow an outgoing connection only for a line, use the no exec command. When a user tries to Telnet to a line with the no exec command configured, the user will get no response when pressing the Return key at the login screen.
The following example turns off the EXEC on line 7. You might want to do this on the auxiliary port if the attached device (for example, the control port of a rack of modems) sends unsolicited data. If this happens, an EXEC process starts, which makes the line unavailable.
line 7 no exec
To set the interval that the EXEC command interpreter waits until user input is detected, use the exec-timeout line configuration command. Use the no form of this command to remove the timeout definition.
exec-timeout minutes [seconds]| minutes | Integer that specifies the number of minutes. |
| seconds | (Optional) Additional time intervals in seconds. An interval of zero specifies no timeouts. |
10 minutes
Line configuration
This command first appeared in Cisco IOS Release 10.0.
If no input is detected, the EXEC facility resumes the current connection, or if no connections exist, it returns the terminal to the idle state and disconnects the incoming session. It is the same as entering exec-timeout 0.
The following example sets a time interval of 2 minutes, 30 seconds:
line console exec-timeout 2 30
The following example sets a time interval of 10 seconds:
line console exec-timeout 0 10
To set the method of data flow control between the terminal or other serial device and the router, use the flowcontrol line configuration command. Use the no form of this command to disable flow control.
flowcontrol {none | software [lock] [in | out] | hardware [in | out]}| none | Turns off flow control. |
| software | Sets software flow control. An optional keyword specifies the direction: in causes the Cisco IOS software to listen to flow control from the attached device, and out causes the software to send flow control information to the attached device. If you do not specify a direction, both are assumed. |
| lock | Used to make it impossible to turn off flow control from the remote host when the connected device needs software flow control. This option applies to connections using the Telnet or rlogin protocols. |
| hardware | Sets hardware flow control. An optional keyword specifies the direction: in causes the software to listen to flow control from the attached device, and out causes the software to send flow control information to the attached device. If you do not specify a direction, both are assumed. For more information about hardware flow control, see the hardware manual that was shipped with your router. |
No flow control
Line configuration
This command first appeared in Cisco IOS Release 10.0.
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.
The following example sets hardware flow control on line 7:
line 7 flowcontrol hardware
You can use the master indexes or search online to find documentation of related commands.
start-character
stop-character
terminal flowcontrol
To create a list of member asynchronous interfaces (associated with a group interface), use the group-range interface configuration command. Use the no form of the command to remove an interface from the member list.
group-range low-end-of-range high-end-of-range| low-end-of-range | Beginning interface number to be made a member of the group interface. |
| high-end-of-range | Ending interface number to be made a member of the group interface. |
No interfaces are designated as members of a group.
Interface configuration
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.
The following example defines interfaces 2, 3, 4, 5, 6, and 7 as members of asynchronous group interface 0:
interface group-async 0 group range 2 7
You can use the master indexes or search online to find documentation of related commands.
interface group-async
member
To limit the size of the IP output queue, use the hold-queue interface configuration command. To return the output queue to the default size, use the no form of this command.
hold-queue packets| packets | Maximum number of packets. The range of values is 0 to 65535. |
10 packets (default for asynchronous interfaces only)
Interface configuration
This command first appeared in Cisco IOS Release 10.0. The no hold-queue command first appeared in Cisco IOS Release 11.1.
The default of 10 packets allows the Cisco IOS software to queue a number of back-to-back routing updates. This is the default for asynchronous interfaces only; other media types have different defaults.
The hold queue stores packets received from the network that are waiting to be sent to the client. It is recommended that the queue size not exceed ten packets on asynchronous interfaces. For most other interfaces, queue length should not exceed 100.
The following example changes the packet queue length of a line to five packets:
interface async 2 async default ip address 172.31.7.5 hold-queue 5
To configure an access list to be used for packets transmitted to and from the asynchronous host, use the ip access-group interface configuration command. To disable control over packets transmitted to or from an asynchronous host, use the no form of this command.
ip access-group access-list-number {in | out}| access-list-number | Assigned IP access list number. |
| in | Defines access control on packets transmitted from the asynchronous host. |
| out | Defines access control on packets being sent to the asynchronous host. |
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
With this command in effect, the IP destination address of each packet is run through the access list for acceptability and dropped or passed.
The following example assumes that users are restricted to certain servers designated as SLIP or PPP servers, but that normal terminal users can access anything on the local network:
! access list for normal connections access-list 1 permit 172.16.0.0 0.0.255.255 ! ! access list for SLIP packets. access-list 2 permit 172.16.42.55 access-list 2 permit 172.16.111.1 access-list 2 permit 172.16.55.99 ! ! Specify the access list interface async 6 async dynamic address ip access-group 1 out ip access-group 2 in
To specify the size of the largest Internet packet, use the ip mtu interface configuration command. To return to the default MTU size of 1500 bytes, use the no form of this command.
ip mtu bytes| bytes | Maximum number of bytes. The range of values is 64 to 1000000. |
1500 bytes
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
The following example sets the packet MTU size to 200 bytes:
interface async 5 async default ip address 172.31.7.5 ip mtu 200
To identify a specific line for configuration and start the line configuration command collection mode, use the line global configuration command.
line [aux | console | tty | vty] line-number [ending-line-number]| aux | (Optional) Auxiliary EIA/TIA-232 DTE port. Must be addressed as relative line 0. The auxiliary port can be used for modem support and asynchronous connections. |
| console | (Optional) Console terminal line. The console port is DCE. |
| tty | (Optional) Standard asynchronous line. |
| vty | (Optional) Virtual terminal for remote console access. |
| line-number | The relative number of the terminal line (or the first line in a contiguous group) that you want to configure when the line type is specified. Numbering begins with zero. |
| ending-line-number | (Optional) The relative number of the last line in a contiguous group that you want to configure. If you omit the keyword, then line-number and ending-line-number are absolute rather than relative line numbers. |
There is no default line.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
You can address a single line or a consecutive range of lines with the line command. A line number is necessary, though, and you will receive an error message if you forget to include it.
Entering the line command with the optional line type (AUX, CON, TTY, or VTY) designates the line number as a relative line number. For example, to configure line parameters for line 7 (a TTY line), you could enter the following:
Router(config)# line tty 7
You also can enter the line command without specifying a line type. In this case, the line number is treated as an absolute line number. For example, to configure line parameters for line 5, which can be of any type, you could enter the following:
Router(config)# line 5
Absolute line numbers increment consecutively and can be difficult to manage on large systems. Relative line numbers are a shorthand notation used in configuration. Internally, the Cisco IOS software uses absolute line numbers. You cannot use relative line numbers everywhere, but you can use absolute line numbers everywhere.
The absolute line number of the auxiliary port is 1. The relative line number of the auxiliary port is 0. See the modem line configuration command to set up modem support on the auxiliary port.
The software keeps a table of absolute and relative line numbers that you can display with the EXEC command show users all. A sample display follows:
Router> show users all
Line User Host(s) Idle Location
0 con 0 chaff console
1 tty 1 Engineering printer
2 tty 2
3 tty 3 DREGGS 1:07 Katy x1111
4 tty 4 Console E3-D
5 tty 5 Mkt. demo area
6 tty 6
7 tty 7 DREGGS 14 Marie x1112
10 tty 10
. . .
135 tty 135
136 tty 136
137 tty 137 rp4-printer
140 tty 140 Braille printer
141 aux 0
142 vty 0 Denise idle DENISE-MAC.CISCO.COM
143 vty 1 Michael idle 0 DREGGS.CISCO.COM
144 vty 2
145 vty 3
146 vty 4
147 vty 5
The absolute line numbers are listed at the far left, followed by the line type, and then the relative line number. Relative line numbers always begin numbering at zero and define the type of line. Addressing the second virtual terminal line as line VTY 1, for example, is easier than remembering it as line 143--its absolute line number.
The line types are ranked as follows in the line table:
The terminal from which you locally configure the router is attached to the console port. To configure line parameters for the console port, enter the following:
Router(config)# line con 0
The console relative line number must be 0.
Virtual terminal lines are used to allow remote access to the router. A virtual terminal line is not associated with either the auxiliary or console port. The router has five virtual terminal lines by default. However, you can create additional virtual terminal lines as described in the section "Create Additional Virtual Terminal Lines" in the "Configuring Protocol Translation and Virtual Asynchronous Devices" chapter of the Dial Solutions Configuration Guide.
Configuring the console port or virtual terminal lines allows you to perform such tasks as setting communication parameters, specifying autobaud connections, and configuring terminal operating parameters for the terminal you are using.
The following example starts configuration for virtual terminal lines 0 to 4:
line vty 0 4
In the following example, the user creates and configures the maximum 100 virtual terminal lines with the no login command:
line vty 0 99 no login
In the following example, the user eliminates virtual terminal line number 5 and all higher-numbered virtual terminal lines. Only virtual terminal lines 0 to 4 will remain.
no line vty 5
In the following example, the user configures console line 0, auxiliary line 0, and virtual terminal lines 0 to 4:
line vty 0 4 login line con 0 password baskerville line aux 0 password Mypassword no exec access-class 1 in speed 19200 line vty 0 exec-timeout 0 0 password Mypassword line vty 1 exec-timeout 0 0 password Mypassword line vty 2 exec-timeout 0 0 password Mypassword line vty 3 password Mypassword line vty 4 password Mypassword
You can use the master indexes or search online to find documentation of related commands.
show line
show users all
To alter the configuration of an asynchronous interface that is a member of a group, use the member interface configuration command. Use the no form of the command to restore defaults set at the group master interface.
member number interface-command| number | Number of the asynchronous interface to be altered. |
| interface-command | One or more of the following commands entered for this specific interface:
· peer default ip address · description |
No individual configurations are set for member interfaces.
Interface configuration
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.) To restore the defaults set at the group master interface, use the no form of this command.
The following example defines interface 3 with a description of line 3, which is attached to a Hayes Optima modem:
interface group-async 0 member 3 description line #3 Hayes Optima
You can use the master indexes or search online to find documentation of related commands.
group-range
interface group-async
To support dial-in modems that use the data terminal ready (DTR) signal to control the off-hook status of the modem, use the modem callin line configuration command. Use the no form of this command to disable this feature.
modem callinThis command has no arguments or keywords.
No modem control
Line configuration
This command first appeared in Cisco IOS Release 10.0.
In response to RING, the router raises the DTR signal, which indicates to the modem that it should answer the call. At the end of the session, the Cisco IOS software lowers DTR, which disconnects the modem. This command is useful for older modems that do not support auto answer.
This command uses CTS, whereas newer modem commands in the Cisco IOS software use DSR.
Only use the modem callin command on the ASM terminal server, where hardware flow control is not possible. If you have a more recent device (such as a Cisco 2509 through 2512, Cisco 2520 through 2523, a Cisco AS5100, Cisco 3600 series, or Cisco AS5200), use the modem dialin command instead.
The following example configures lines 10 through 16 for dial-in modems that can run at speeds from 300 to 19,200 bps:
line 10 16 modem callin autobaud
You can use the master indexes or search online to find documentation of related commands.
modem answer-timeout
modem inout
To configure a line for reverse connections, use the modem callout line configuration command. Use the no form of this command to disable this feature.
modem calloutThis command has no arguments or keywords.
No modem control
Line configuration
This command first appeared in Cisco IOS Release 10.0.
This command supports ports connected to computers that would normally be connected to modems. It causes the access server to act somewhat like a modem.
This command uses CTS and should be used only on access servers that do not support hardware flow control. If you have an access server that is newer than the ASM terminal server (such as a Cisco 2509 through 2512, Cisco 2520 through 2523, a Cisco AS5100, Cisco 3600 series, or a Cisco AS5200), use the modem host command instead. The modem callout command uses CTS, whereas the modem host command uses DSR/DCD. If CTS is used for modem control instead of DSR/DCD, it prevents CTS from being used by hardware flow control.
The following example configures lines 17 through 32 in reverse connection mode to a large terminal switch. By using Telnet to connect to a TCP port on this host, the user gets the next free line in the rotary group.
line 17 32 rotary 1 modem callout
You can use the master indexes or search online to find documentation of related commands.
modem inout
rotary
The modem printer command replaces the modem cts-required command. Refer to the description of the modem printer command for more information.
To configure a line to enable a modem attached to the router to accept incoming calls only, use the modem dialin line configuration command. Use the no form of this command to disable this feature.
modem dialinThis command has no arguments or keywords.
Do not permit incoming calls to the modem.
Line configuration
This command first appeared in Cisco IOS Release 11.1.
This command supports modems that can automatically handle telephone line activity, such as answering the telephone after a certain number of rings.
The following example configures a line for a high-speed modem:
line 5 modem dialin
You can use the master indexes or search online to find documentation of related commands.
dialer
modem inout
parity
To configure a line to leave data terminal ready (DTR) signals low, unless the line has an active incoming connection or an EXEC process, use the modem dtr-active line configuration command. Use the no form of this command to disable this feature.
modem dtr-activeThis command has no arguments or keywords.
No modem control
Line configuration
This command first appeared in Cisco IOS Release 10.0.
This command does not use the Carrier Detect (CD) signal.
This command can be useful if the line is connected to an external device (for example, a time-sharing system) that must know whether a line is in active use. The modem dtr-active command is similar to the no modem line configuration command.
The following example configures a line for low DTR:
line 5 modem dtr-active
You can use the master indexes or search online to find documentation of related commands.
To configure a line for reverse connections where hardware flow control is also required, use the modem host line configuration command. Use the no form of this command to disable the line modem control for reverse connections.
modem hostThis command has no arguments or keywords.
No modem control
Line configuration
This command first appeared in Cisco IOS Release 11.1.
This command supports ports connected to computers that would normally be connected to modems. This command causes the access server to act like a modem.
The modem host command is identical in operation to the modem callout command except that DSR/DCD is used for modem control instead of CTS. This frees CTS for use by hardware flow control.
The following example configures a line to send a DSR/CD active signal to the modem for data switches and hosts:
line 5 modem host
You can use the master indexes or search online to find documentation of related commands.
modem callout
modem printer
To configure a line for both incoming and outgoing calls, use the modem inout line configuration command. Use the no form of this command to disable this feature.
modem inoutThis command has no arguments or keywords.
No modem control
Line configuration
This command first appeared in Cisco IOS Release 10.0.
This command uses DSR and RING signals for carrier detection.
The Cisco IOS software does not support any dialing protocols; therefore, the host system software or the user must provide any special dialing commands when using the modem for outgoing calls.
The following example configures a line for both incoming and outgoing calls:
line 5 modem inout
You can use the master indexes or search online to find documentation of related commands.
dialer
parity
To configure a line to require a data set ready (DSR) signal, use the modem printer line configuration command. Use the no form of this command to use CTS instead of DSR.
modem printerThis command has no arguments or keywords.
No modem control
Line configuration
This command first appeared in Cisco IOS Release 11.1.
This command uses RING/DCD (Data Carrier Detect) /DSR as the modem control signal instead of CTS. This leaves CTS free for use in hardware flow control. You can configure hardware flow control concurrently with the modem printer command.
While the modem dialin command supports modems concurrently with hardware flow control, the other auxiliary modem control options for printers, such as modem cts-required, use CTS instead of DSR/CD, as the CD signal.
The following example configures a line to send a DSR signal to the modem:
line 5 modem printer
The modem dialin command replaces the modem ri-is-cd command. Refer to the description of the modem dialin command for more information.
To enable the NetBIOS Frames Protocol (NBF) on an interface, use the netbios nbf interface configuration command. To disable NetBIOS Frames Protocol support on an interface, use the no form of this command.
netbios nbfThis command has no arguments or keywords.
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 11.1.
The following example enables NetBIOS Frames Protocol on asynchronous interface 1 (connected to remote access client using a NetBEUI application) and Ethernet interface 0 (connected to the remote router):
interface async 1 netbios nbf interface ethernet 0 netbios nbf
You can use the master indexes or search online to find documentation of related commands.
netbios name-cache
show netbios cache
show nbf sessions
To specify the mode of a slow-speed serial interface on a router as either synchronous or asynchronous, use the physical-layer interface configuration command. Use the no form of this command to return the interface to its default mode, which is synchronous.
physical-layer {sync | async}| sync | Place the interface in synchronous mode. |
| async | Place the interface in asynchronous mode. |
Synchronous mode
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
This command applies only to low-speed serial interfaces available on Cisco 2520 through Cisco 2523 routers.
If you specify the no physical-layer command, you return the interface to its default mode (synchronous).
In synchronous mode, low-speed serial interfaces support all interface configuration commands available for high-speed serial interfaces, except the following two commands:
When placed in asynchronous mode, low-speed serial interfaces support all commands available for standard asynchronous interfaces.
When you enter this command, it does not appear in the output of show running config and show startup config commands, because the command is a physical layer command.
The following example changes a low-speed serial interface from synchronous to asynchronous mode:
interface serial 2 physical-layer async
To define a group of lines consisting of one of more lines, use the rotary line configuration command. Use the no form of this command to remove a line or group of lines from a rotary group.
rotary group| group | Integer between 1 and 100 that you choose to identify the rotary group. |
No group of lines is defined.
Line configuration
This command first appeared in Cisco IOS Release 10.0.
Typically, rotary groups are used on devices with multiple modem connections to allow connections to the next free line in a hunt group.
Connections to a rotary group can take advantage of the following features:
The remote host must specify a particular TCP port on the router to connect to a rotary group with connections to an individual line. The available services are the same, but the TCP port numbers are different. Table 2 lists the services and port numbers for both rotary groups and individual lines.
| Services Provided | Base TCP Port for Rotaries | Base TCP Port for Individual Lines |
|---|---|---|
| Telnet protocol | 3000 | 2000 |
| Raw TCP protocol (no Telnet protocol) | 5000 | 4000 |
| Telnet protocol, binary mode | 7000 | 6000 |
| XRemote protocol | 10000 | 9000 |
For example, if Telnet protocols are required, the remote host connects to the TCP port numbered 3000 (decimal) plus the rotary group number. If the rotary group identifier is 13, the corresponding TCP port is 3013.
If a raw TCP stream is required, the port is 5000 (decimal) plus the rotary group number. If rotary group 5 includes a raw TCP (printer) line, the user connects to port 5005 and is connected to one of the raw printers in the group.
If Telnet binary mode is required, the port is 7000 (decimal) plus the rotary group number.
The following example establishes a rotary group consisting of virtual terminal lines 2 through 4 and defines a password on those lines. By using Telnet to connect to TCP port 3001, the user gets the next free line in the rotary group. The user does not have to remember the range of line numbers associated with the password.
line vty 2 4 rotary 1 password letmein login
You can use the master indexes or search online to find documentation of related commands.
dialer
modem bad
modem callout
session-timeout
To specify that a chat script start on a physical terminal line any time the line is activated, use the script activation line configuration command. Use the no form of this command to disable this feature.
script activation regexp| regexp | Regular expression that specifies the set of modem scripts that might be executed. The first script name that matches the argument regexp will be used. |
Not assigned to terminal lines
Line configuration
This command first appeared in Cisco IOS Release 10.0.
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 argument regexp (a regular expression) matches an existing chat script name, the matched script is run on the line. For more information about regular expressions, refer to the "Regular Expressions" appendix in this publication.
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 (VTY) lines.
The following example specifies that the chat script with a name that includes telebit will be activated whenever line 4 is activated:
line 4 script activation telebit
You can use the master indexes or search online to find documentation of related commands.
chat-script
dialer map modem-script system-script
dialer map modem-script system-script name
script activation
script connection
script dialer
script reset
script startup
start-chat
To specify that a chat script start on a physical terminal line any time a remote network connection is made to a line, use the script connection line configuration command. Use the no form of this command to disable this feature.
script connection regexp| regexp | Specifies the set of modem scripts that might be executed. The first script name that matches the argument regexp will be used. |
Not assigned to terminal lines
Line configuration
This command first appeared in Cisco IOS Release 10.0.
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 (VTY) 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, refer to the "Regular Expressions" appendix in this publication.
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 4 script connection inband
Using this example and the topology in Figure 2, 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.
You can use the master indexes or search online to find documentation of related commands.
chat-script
dialer map modem-script system-script
dialer map modem-script system-script name
script activation
script dialer
script reset
script startup
start-chat
To specify that a chat script start on a physical terminal line any time the specified line is reset, use the script reset line configuration command. Use the no form of this command to disable this feature.
script reset regexp| regexp | Specifies the set of modem scripts that might be executed. The first script name that matches the argument regexp will be used. |
Not assigned to terminal lines.
Line configuration
This command first appeared in Cisco IOS Release 10.0.
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 (VTY) lines.
For information about regular expressions, refer to the "Regular Expressions" appendix in this publication.
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 7 script reset linebackup
The 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 4 script reset drop-line
You can use the master indexes or search online to find documentation of related commands.
chat-script
dialer map modem-script system-script
dialer map modem-script system-script name
script activation
script connection
script dialer
script startup
start-chat
To specify that a chat script start on a physical terminal line any time the router is powered up, use the script startup line configuration command. Use the no form of this command to disable this feature.
script startup regexp| regexp | Specifies the set of modem scripts that might be executed. The first script that matches the argument regexp will be used. |
Not assigned to terminal lines
Line configuration
This command first appeared in Cisco IOS Release 10.0.
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 (VTY) lines.
For information about regular expressions, refer to the "Regular Expressions" appendix in this publication.
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 5 script startup linestart
You can use the master indexes or search online to find documentation of related commands.
chat-script
dialer map modem-script system-script
dialer map modem-script system-script name
script activation
script connection
script dialer
script reset
start-chat
To display the parameters that have been configured for extended BOOTP requests, use the show async bootp privileged EXEC command.
show async bootpThis command has no arguments or keywords.
Privileged EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show async bootp command.
sloth# show async bootp
The following extended data will be sent in BOOTP responses:
bootfile (for address 192.168.31.1) "pcboot"
bootfile (for address 172.16.1.110) "dirtboot"
subnet-mask 255.255.0.0
time-offset -3600
time-server 192.168.31.1
Table 3 describes significant fields shown in the display.
| Field | Description |
|---|---|
| bootfile... "pcboot" | Indicates that the boot file for address 192.168.31.1 is named pcboot. |
| subnet-mask 255.255.0.0 | Specifies the subnet mask. |
| time-offset -3600 | Indicates that the local time is one hour (3600 seconds) earlier than Coordinated Universal Time (UTC). |
| time-server 192.168.31.1 | Indicates the address of the time server for the network. |
To display the status of activity on all lines configured for asynchronous support, use the show async status privileged EXEC command.
show async statusThis command has no arguments or keywords.
Privileged EXEC
This command first appeared in Cisco IOS Release 10.0.
The display resulting from this command shows all asynchronous sessions, whether they are using SLIP or PPP encapsulation.
The following is sample output from the show async status command:
router# show async status
Async protocol statistics:
Rcvd: 5448 packets, 7682760 bytes
1 format errors, 0 checksum errors, 0 overrun, 0 no buffer
Sent: 5455 packets, 7682676 bytes, 0 dropped
Tty Local Remote Qd InPack OutPac Inerr Drops MTU Qsz
1 192.168.7.84 Dynamic 0 0 0 0 0 1500 10
* 3 192.168.7.98 None 0 5448 5455 1 0 1500 10
Table 4 describes significant fields shown in the display.
| Field | Description |
|---|---|
| Rcvd | Statistics on packets received. |
| 5448 packets | Packets received. |
| 7682760 bytes | Total number of bytes. |
| 1 format errors | Spurious characters received when a packet start delimiter is expected. |
| 0 checksum errors | Count of checksum errors. |
| 0 overrun | Number of giants received. |
| 0 no buffer | Number of packets received when no buffer was available. |
| Sent | Statistics on packets sent. |
| 5455 packets | Packets sent. |
| 7682676 bytes | Total number of bytes. |
| 0 dropped | Number of packets dropped. |
| Tty | Line number. |
| * | Line currently in use. |
| Local | Local IP address on the link. |
| Remote | Remote IP address on the link; "Dynamic" indicates that a remote address is allowed but has not been specified; "None" indicates that no remote address is assigned or being used. |
| Qd | Number of packets on hold queue (Qsz is the maximum). |
| InPack | Number of packets received. |
| OutPac | Number of packets sent. |
| Inerr | Number of total input errors; sum of format errors, checksum errors, overruns and no buffers. |
| Drops | Number of packets received that would not fit on the hold queue. |
| MTU | Current maximum transmission unit size. |
| Qsz | Current output hold queue size. |
To display a terminal line's parameters, use the show line EXEC command.
show line [line-number]| line-number | (Optional) Absolute line number of the line for which you want to list parameters. |
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following sample output from the show line command shows that line 17 is a virtual terminal line with a transmit and receive rate of 9600 bps. Also shown is the modem state, terminal screen width and length, and so on.
router# show line 17
Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns
A 17 VTY 9600/9600 - - - - - 1 0 0/0
Line 17, Location: "", Type: ""
Length: 24 lines, Width: 80 columns
Baud rate (TX/RX) is 9600/9600
Status: Ready, Connected, Active, No Exit Banner, Async interface active
Capabilities: Line usable as async interface
Modem state: Ready
Special Chars: Escape Hold Stop Start Disconnect Activation
^^x none - - none
Timeouts: Idle EXEC Idle Session Modem Answer Session Dispatch
never never none not set
Session limit is not set.
Time since activation: never
Editing is enabled.
History is enabled, history size is 10.
Full user help is disabled
Allowed transports are lat telnet rlogin mop. Preferred is lat.
No output characters are padded
No special data dispatching characters
Line is running SLIP routing for address 1.0.0.2.
0 output packets queued, 0 input packets.
Group codes: 0
Table 5 describes the fields in the show line output.
| Field | Description |
|---|---|
| Tty | Line number. In this case, 17. |
| Typ | Type of line. In this case, a virtual terminal line (VTY), which is active, in asynchronous mode denoted by the preceding 'A.' Other possible values are:
|
|
Tx/Rx | Transmit rate/receive rate of the line. |
| A | Indicates whether autobaud has been configured for the line. A value of F indicates that autobaud has been configured; a hyphen indicates that it has not been configured. |
| Modem | Types of modem signals that have been configured for the line. Possible values include
|
|
Roty | Rotary group configured for the line. |
| AccO, AccI | Output or Input access list number configured for the line. |
| Uses | Number of connections established to or from the line since the system was restarted. |
| Noise | Number of times noise has been detected on the line since the system restarted. |
| Overruns | Hardware (UART) overruns and/or software buffer overflows, both defined as the number of overruns or overflows that have occurred on the specified line since the system was restarted. Hardware overruns are buffer overruns; the UART chip has received bits from the software faster than it can process them. A software overflow occurs when the software has received bits from the hardware faster than it can process them. |
| Line | Current line. |
| Location | Location of the current line. |
| Type | Type of line, as specified by the line global configuration command. |
| Length | Length of the terminal or screen display. |
| Width | Width of the terminal or screen display. |
| Baud rate (TX/RX) | Transmit rate/receive rate of the line. |
| Status | State of the line: Ready or not, connected or disconnected, active or inactive, exit banner or no exit banner, async interface active or inactive. |
| Capabilities | Current terminal capabilities. In this case, the line is usable as an asynchronous interface. |
| Modem state | Modem control state. This field should always read READY. |
| Special Chars | Current settings of special characters that were input by the user (or taken by default) from the following global configuration commands:
|
|
Timeouts | Current settings that were input by the user (or taken by default) from the following global configuration commands:
|
|
Session limit | Maximum number of sessions. |
| Time since activation | Last time start_process was run. |
| Editing | Whether or not command line editing is enabled. |
| History | Current history length, set by the user (or taken by default) from the history configuration command. |
| Full user help | Whether or not full user help has been set by the user with the terminal full-help command or by the administrator with the full-help line configuration command. |
| Allowed transports are... | Current set transport method, set by the user (or taken by default) from the transport preferred line configuration command. |
| characters are padded | Current set padding, set by the user (or taken by default) from the padding line configuration command. |
| data dispatching characters | Current dispatch character set by the user (or taken by default) from the dispatch-character line configuration command. |
| Line | Definition of the specified line's protocol and address. |
| output, input packets | Number of output and input packets queued on this line. |
| Group codes | AT group codes. |
To display the values set for the current modem, use the show modemcap command. This display lists the modems for which the router has entries. To display the attributes associated with a specific modem, use the show modemcap modem-name command.
show modemcap modem-name| modem-name | The name of the modem (such as Codex_3260). |
The list of modems for which the router has entries.
EXEC
This command first appeared in Cisco IOS Release 11.1.
When a modem name is supplied, this command displays the available modem values. Table 6 identifies the list of attributes and their description:
| Modem Attribute | Description |
|---|---|
| Factory defaults (FD) | Returns the modem to factory default configuration. This is commonly "&F" |
| Autoanswer (AA) | Sets the modem to answer the phone if DTR is high, preferably on the first ring. This is commonly "S0=1" |
| Carrier detect (CD) | Instructs the modem to raise CD signal when a carrier is detected. Cisco configures modems into auto-answer mode by default. Oddly this is not the default for most modems, which just raise CD and leave it high. This is commonly "&C1."
In auto-answer mode, the modem waits until it detects a ring, then responds to the incoming call and negotiates an end-to-end connection with the other modem. At this point, the modem receiving the call informs the router that it has a call ready to be processed; this notification is performed by raising the signal on RS-232 pin 8 (the Data Carrier Detect signal) to high. |
| Drop with DTR (DTR) | Drops the connection if DTR signal drops. There is frequently an option to reset the configuration while doing this. However, this option should not be used. The connection should only drop. The correct value for this is commonly "&D2." |
| Set hardware flow control (HFL) | Uses RTS/CTS (out-of-band) flow control. |
| Set software flow control (SFL) | Uses XON/XOFF (in-band) flow control. |
| Lock to maximum DTE speed (SPD) | Instructs the modem to lock the speed at which it communicates to the router to a single rate, preferably the highest. This attribute is important and is often hard to find in manuals.
SPD is often linked to the hardware flow control variable. Look for phrases like "bps rate adjust" and "bit rate adjust." Some modems set the speed to a value that depends on an S-register; other modems simply lock to the speed that was used when the last AT command was issued. Locking to the speed that was last used is handled automatically. To enable the S-register to set the speed, you must include the proper S-register value for the fastest possible DTE speed. |
| Best error control (BER) | Instructs the modem to negotiate its best error control with remote modems. For ARAP users, this is MNP5/LAPB, but not MNP4. |
| Best compression (BCP) | Instructs the modem to negotiate its best compression with remote modems. |
| No error control (NER) | Instructs the modem to negotiate no error control with remote modems. This will be used when placing outgoing (callback) ARAP calls. |
| No compression (NCP) | Instructs the modem to negotiate no compression with remote modems. This is used when placing outgoing (callback) ARAP calls. |
| No echo (NEC) | Requests the modem not to echo characters. This is commonly "E0." |
| No response codes (NRS) | Requests the modem not to send a response when you issue a command. This is commonly "Q1." |
| Set Caller ID (CID) | Requests that Caller ID information be returned when dialin occurs. Currently not used. |
| Miscellaneous strings (MSC) | Sends any extra commands that are needed for the modem to work (possibly with specific platforms). |
| Template entry (TPL) | This is the name of another modem type. It is referenced as the value of any of the previously listed attributes if they are not set on the current modem type. |
As an alternative to repeatedly entering the same data, use templates as a way to join modemcap entries. For example, consider the following modemcap entries:
modemcap entry gv_basics:FD=&F:AA=S0=1:CD=&C1:DTR=&D2:NEC=E0:NRS=Q1 modemcap entry global_village:HFL=&K3\\X1:BCP=%C1:NCP=%C0:TPL=gv_basics modemcap entry gv_teleport:NCP=%C0:TPL=gv_basics
To look up the factory default for a global_village modem, perform the following steps:
Step 1 Look at the global_village modemcap entry for the factory default (FD).
Step 2 If you fail to find FD in global_village, look at the global_village modemcap entry for a template (TPL).
Step 3 Find a TPL called "gv_basics."
Step 4 Look in the gv_basics modemcap entry for the FD.
Step 5 Find FD=&F in the gv_basics modemcap entry.
Step 6 Use &F as the FD for the global_village.
The following example shows the modem values in a Codex_3260:
show modemcap Codex_3260
You can use the master indexes or search online to find documentation of related commands.
modemcap edit
modemcap entry
Use the show nbf cache user level EXEC command to display NetBIOS name cache contents.
show nbf cacheThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.1.
The following is sample output from the show nbf cache command:
router>show nbf cacheHW Addr Name How Idle NetBIOS Packet Savings 1000.5a89.449a IKBA E0 6 0 0000.0000.0000 NANOO async1 21 0
Table 7 describes significant fields shown in the display.
| Field | Description |
|---|---|
| HW Addr | MAC address mapped to the NetBIOS name in this entry. |
| Name | NetBIOS name mapped to the MAC address in this entry. |
| How | Interface through which this information was learned. |
| Idle | Period of time (in seconds) since this entry was last accessed. A hyphen in this column indicates a static entry in the NetBIOS name cache. |
| NetBIOS Packet Savings | Number of packets to which local replies were made (thus preventing transmission of these packets over the network). |
You can use the master indexes or search online to find documentation of related commands.
netbios access-list
netbios input-access-filter
netbios name-cache
netbios nbf
netbios output-access-filter
show nbf sessions
Use the show nbf sessions user level EXEC command to view NetBEUI connection information.
show nbf sessionsThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.1.
The following is sample output from the show nbf sessions command:
router>show nbf sessionsAsync6 NetBIOS Session Table: Srcnum Destnum Dest-Interface DestMAC 8 6 Ethernet0 00aa.005b.c17b NetBIOS Global Session Table: Srcnum Destnum Dest-Interface DestMAC Src-Interface SrcMac(I) 6 8 Async7 0000.0000.0000 Ethernet0 00aa.005b.c17b(95) ADD_[GROUP]NAME_QUERY queuesize=0 STATUS_QUERY queuesize=0 STATUS_RESPONSE queuesize=0 NAME_QUERY queuesize=0 NAME_RECOGNIZED queuesize=0 SESSION_INITIALIZE queuesize=0 SESSION_INITIALIZE (pending) queuesize=0
Table 8 describes significant fields shown in the display.
| Field | Description |
|---|---|
| Interface NetBIOS Session Table: | Summarizes Async/ISDN interface NetBIOS connection information. |
| Srcnum, Destnum | Source and destination connection numbers. |
| Dest-Interface, DestMAC | Destination interface and MAC address. |
| Global NetBIOS Session Table: | Summarizes LAN NetBIOS connection information. |
| Dest-Interface DestMAC | Destination interface (Async7 in this case) and MAC address (0000.0000.0000 in this case). |
| Src-Interface SrcMac | Source interface (Ethernet0 in this case) and MAC address (00aa.005b.c17b(95) in this case). |
| NetBIOS Datagram Queue Summary | Summarizes NetBIOS pending datagram queues. |
| ADD_[GROUP]NAME_QUERY | Add Group Name Query packets. |
| STATUS_QUERY | Status Query packets. |
| STATUS_RESPONSE | Status Response packets. |
| NAME_QUERY | Name Query packets. |
| NAME_RECOGNIZED | Name Recognized packets. |
| SESSION_INITIALIZE (pending) | NetBIOS session Initialize packets. |
You can use the master indexes or search online to find documentation of related commands.
netbios access-list
netbios input-access-filter
netbios output-access-filter
netbios name-cache
netbios nbf
show nbf cache
To display information about the active lines on the router, use the show users user EXEC command.
show users [all]| all | (Optional) Specifies that all lines be displayed, regardless of whether anyone is using them. |
User EXEC
This command first appeared in a release prior to Cisco IOS Release 10.0.
This command displays the line number, connection name, idle time, and terminal location.
The following is sample output from the show users command:
router# show users
Line User Host(s) Idle Location
0 con 0 idle
* 2 vty 0 rose idle 0 BASHFUL.CISCO.COM
The following is sample output from the show users all command:
router# show users all
Line User Host(s) Idle Location
* 0 vty 0 rose idle 0 BASHFUL.CISCO.COM
1 vty 1
2 con 0
3 aux 0
4 vty 2
The asterisk (*) indicates the current terminal session.
Table 9 describes significant fields shown in the displays.
| Field | Description |
|---|---|
| Line | Contains three subfields.
|
|
User | User using the line. If no user is listed in this field, no one is using the line. |
| Host(s) | Host to which the user is connected (outgoing connection). A value of idle means that there is no outgoing connection to a host. |
| Idle | Interval (in minutes) since the user has entered something. |
| Location | Either the hard-wired location for the line or, if there is an incoming connection, the host from which incoming connection came. |
You can use the master indexes or search online to find documentation of related commands.
show users
To set the flow control start character, use the start-character line configuration command. Use the no form of this command to remove the character.
start-character ascii-number| ascii-number | Decimal representation of the start character. |
Decimal 17
Line configuration
This command first appeared in Cisco IOS Release 10.0.
This command defines the character that signals the start of data transmission when software flow control is in effect. See the "ASCII Character Set" appendix in the Configuration Fundamentals Command Reference for a list of ASCII characters.
The following example changes the start character to Ctrl-B, which is decimal 2:
line 2
start-character 2
You can use the master indexes or search online to find documentation of related commands.
flowcontrol
stop-character
terminal start-character
To specify that a chat script start on a specified line at any point, use the start-chat privileged EXEC command. Use the no form of this command to stop the chat script.
start-chat regexp [line-number [dialer-string]]| regexp | Specifies the name of a regular expression or modem script to be executed. If there is more than one script with a name that matches the argument regexp, the first script found will be used. |
| line-number | (Optional) Indicates the line number on which to execute the chat script. If you do not specify a line number, the current line number is chosen. If the specified line is busy, the script is not executed and an error message appears. If the dialer-string argument is specified, line-number must be entered; it is not optional if you specify a dialer string. This command functions only on physical terminal (TTY) lines. It does not function on virtual terminal (VTY) lines. |
| dialer-string | (Optional) String of characters (often a telephone number) to be sent to a DCE. If you enter a dialer string, you must also specify line-number, or the chat script regexp will not start. |
Privileged EXEC
This command first appeared in Cisco IOS Release 10.0.
This command provides modem dialing commands for a chat script that you want to apply immediately to a line. If you do not specify a line, the script runs on the current line. If the specified line is already in use, the script is not activated and an error message appears.
The argument regexp 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 more information about regular expressions, refer to the "Regular Expressions" appendix in this publication.
This command functions only on physical terminal (TTY) lines. It does not function on virtual terminal (VTY) lines.
The following example forces a dialout on line 8 using the script telebit:
start-chat telebit line 8
You can use the master indexes or search online to find documentation of related commands.
chat-script
dialer map modem-script system-script
dialer map modem-script system-script name
script activation
script connection
script dialer
script reset
script startup
| ascii-number | Decimal representation of the stop character. |
Decimal 19
Line configuration
This command first appeared in Cisco IOS Release 10.0.
This command defines the character that signals the end of data transmission when software flow control is in effect. See the "ASCII Character Set" appendix in the Configuration Fundamentals Command Reference for a list of ASCII characters.
The following example changes the stop character to Ctrl-E, which is decimal 5:
line 3
stop-character 5
You can use the master indexes or search online to find documentation of related commands.
flowcontrol
start-character
terminal stop-character
|
|