|
|
This chapter describes how to manage connections to other hosts, set banner messages for router users, and create menus of specific user tasks. For a complete description of the connections, menu, and system banner commands in this chapter, refer to the "Connection, Menu, and System Banner Commands" chapter in the Cisco IOS Configuration Fundamentals Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.
The following sections describe the taks required to manage connections, configure messages and banners, and configure user-menus:
Examples for the above sections can be found at the end of the chapter in the "Connection Management, System Banner, and User-Menu Examples" section.
This section describes session-management activities. The following sections describe connection-management activities that apply to all supported connection protocols:
 |
Note In screen output examples that show two caret (^^) symbols together, the first caret represents the Control key (Ctrl) and the second caret represents the keystroke sequence Shift-6. The double-caret combination (^^) means hold down the Ctrl key while you press the Shift and the 6 key. |
By default, the escape sequence is Ctrl^x. If you press the escape key (Escape-Char), you change the Shift-Ctrl-6 sequence to whatever you want. For example, if you press Escape-Char Break, the Break key becomes the new escape character to suspend a session and to access the EXEC prompt.
You can have several concurrent sessions open and switch back and forth between them.
The number of sessions that can be open is defined by the session-limit command.
To switch between sessions by escaping one session and resuming a previously opened session, use the following commands:
| Command | Purpose | |
|---|---|---|
Step 1 | Ctrl-Shift-6 then x (Ctrl^x) by default | Escapes the current connection and return to the EXEC prompt. |
Step 2 | where | Lists the open sessions. All open sessions associated with the current terminal line are displayed. |
Step 3 | resume [connection] [keyword] | Makes the connection. |
The Ctrl^x, where, and resume commands are available with all supported connection protocols.
You could also make a new connection while you are at the EXEC prompt.
To assign a logical name to a connection, use the following command in EXEC mode:
| Command | Purpose |
|---|---|
name-connection | Assigns a logical name to a connection. |
The logical name can be useful for keeping track of multiple connections.
You are prompted for the connection number and name to assign. The where command displays a list of the assigned logical connection names.
| Command | Purpose |
|---|---|
login | Changes a login username. |
When you enter this command, the system prompts you for a username and password. Enter the new username and the original password. If the username does not match, but the password does, the Cisco IOS software updates the session with the new username used by login command attempt.
If no username and password prompts appear, the network administrator did not specify that a username and password be required at login time. If both the username and password are entered correctly, the session becomes associated with the specified username.
When you access a system with TACACS security, you can enter your login name or specify a TACACS server by using the following argument when the "Username:" prompt appears:
user @tacacs-serverThe router must be one of the routers defined in a router configuration. For more information, refer to the "Specifying a TACACS Host" section later in this chapter, or refer to the tacacs-server host command in the "TACACS, Extended TACACS, and TACACS+ Commands" chapter of the Security Command Reference.
If you do not specify a host, the router tries each of the TACACS servers in the list until it receives a response.
If you specify a host that does not respond, no other TACACS server will be queried. The router either denies access or function, according to the action specified by the tacacs-server last-resort command, if it is configured.
If you specified a TACACS server host with the user @tacacs-server argument, the TACACS server specified is used for all subsequent authentication or notification queries, with the possible exception of SLIP address queries.
For an example of changing a login name, see the "Changing a Login Name Example" section at the end of this chapter.
You can prevent access to your terminal session while keeping your connection open by setting up a temporary password. To lock access to the terminal, use the following commands in EXEC mode:
| Command | Purpose | |
|---|---|---|
Step 1 | lock | Issues the lock command. The system prompts you for a password. |
Step 2 | password | Enters a password, which can be any arbitrary string. The screen clears and displays the message "Locked." |
Step 3 | password | To regain access to your sessions, re-enters the password. |
The Cisco IOS software honors session timeouts on a locked line. You must clear the line to remove this feature. The system administrator must set up the line to allow use of the temporary locking feature.
You can specify a TACACS host when you dial in or use the login command. Only the specified host is accessed for user authentication information.
To specify the name of a TACACS host at login, use the following command in EXEC mode:
| Command | Purpose |
|---|---|
user@hostname | Specifies the name of a TACACS host at login. |
For an example of specifying a TACACS host, see the "Specifying a TACACS Host Example" section at the end of this chapter.
You can send messages to one or all terminal lines. A common reason for doing this is to inform users of an impending shutdown. To send a message to other terminals, use the following command in EXEC mode:
| Command | Purpose |
|---|---|
send {line-number | *}
| Sends a message to other terminals. |
The system prompts for the message, which can be up to 500 characters long. Enter Ctrl-Z to end the message. Enter Ctrl-C to abort the command.
To clear a TCP connection, use the following command in privileged EXEC mode:
| Command | Purpose |
|---|---|
clear tcp {line line-number | local host-name port remote
host-name port | tcb address}
| Clears a TCP connection. |
The clear tcp command is particularly useful for clearing hung TCP connections.
The clear tcp line line-number command terminates the TCP connection on the specified TTY line. Additionally, all TCP sessions initiated from that TTY line are terminated.
The clear tcp local host-name port remote host-name port command terminates the specific TCP connection identified by the host name/port pair of the local and remote router.
The protocol used to initiate a session determines how you exit that session.
To exit XRemote, you must quit all active X connections, usually with a command supported by your X client system. Usually, when you quit the last connection (all client processes are stopped), XRemote closes and you return to the EXEC prompt. Check your X client system documentation for specific information about exiting an XRemote session.
To exit a SLIP and PPP, you must hang up the dial-in connection, usually with a command that your dial-in software supports.
To exit a LAT, Telnet, rlogin, TN3270, and X.3 PAD session begun from the router to a remote device, enter the escape sequence (Ctrl-Shift-6 then x [Ctrl^x] by default) and enter the disconnect command at the EXEC prompt. You can also log off the remote system.
Except for XRemote, you also can escape to the EXEC prompt and enter either of the following commands to terminate an active terminal session:
To exit a Telnet session to a router, see the "Log Out of a Router" section.
The method you use to disconnect from a router depends on where you are located in relation to the router, and the port on the router to which you log in. Keep the following in mind:
To disconnect a line, use the following command in EXEC mode:
| Command | Purpose |
|---|---|
disconnect [connection] |
Avoid disconnecting a line to end a session. Instead, log off the host to allow the router to clear the connection. Then end the session. Only if you cannot log out of an active session should you disconnect the line.
The types of messages that can be displayed to terminal users who connect to the router are described in the following sections:
You can configure messages to be displayed on a console or terminal not in use. Also called a vacant message, this message is different from the banner message displayed when an EXEC process is activated. To configure an idle terminal message, use the following command in line configuration mode:
| Command | Purpose |
|---|---|
vacant-message [d message d] | Displays an idle terminal message. |
You can display a "line in use" message when an incoming connection is attempted and all rotary group or other lines are in use. Use the following command in line configuration mode:
| Command | Purpose |
|---|---|
refuse-message d message d | Displays a "line in use" message. |
If you do not define such a message, the user receives a system-generated error message when all lines are in use. You also can use this message to provide the user with further instructions.
You can display a "host failed" message when a Telnet connection with a specific host fails. Use the following command in line configuration mode:
| Command | Purpose |
|---|---|
busy-message hostname d message d | Displays a "host failed" message. |
Banners can be customized with the use of banner tokens as described in the following section:
The types of banners that can be displayed to terminal users who connect to the router are described in the following sections:
You also can turn off message displays, as described in the "Enabling or Disabling the Display of Banners" section.
For an example of displaying terminal banner messages, see the "Configuring Banners Example" section at the end of this chapter.
Table 5 lists the tokens supported by the different banner commands.
You can configure a message-of-the-day (MOTD) banner to be displayed on all connected terminals. This banner is displayed at login and is useful for sending messages that affect all network users (such as impending system shutdowns). To do so, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
banner motd d message d | Configures a MOTD banner. |
You can configure a login banner to be displayed on all connected terminals. This banner is displayed after the MOTD banner and before the login prompts.
To configure a login banner, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
banner login d message d | Configures a login banner. |
The login banner cannot be disabled on a per-line basis. To globally disable the login banner, you must delete the login banner with the no banner login command.
You can configure a line-activation banner to be displayed when an EXEC process (such as a line-activation or incoming connection to a VTY line) is created. To do so, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
banner exec d message d | Configures a banner to be displayed on terminals with an interactive EXEC session. |
You can configure a banner to be displayed on terminals connected to reverse Telnet lines. This banner is useful for providing instructions to users of these types of connections. Reverse Telnet connections are described in more detail in the "Establishing a Reverse Telnet Session to a Modem" chapter in the Dial Solutions Configuration Guide.
To configure a banner that is sent on incoming connections, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
banner incoming d message d | Configures a banner to display on terminals connected to reverse Telnet lines. |
Default banner messages have been known to cause connectivity problems in some non-Cisco Serial Link Interface Protocol (SLIP) andPPP dial-up software. You cand now customize the SLIP-PPP banner message to make Cisco SLIP and PPP compatible with non-Cisco dial-up software. To configure the SLIP-PPP banner message, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
banner slip-ppp d message d | Configures the SLIP-PPP banner to display a customized message. |
You can control display of the MOTD and line-activation (EXEC) banners. By default, these banners are displayed on all lines. To suppress or reinstate the display of such banners, use one of the following commands in line configuration mode:
| Command | Purpose |
|---|---|
no exec-banner | Suppresses MOTD and EXEC banner display. |
exec-banner | Reinstates the display of the EXEC or MOTD banners. |
no motd-banner | Suppresses MOTD banner display only. |
motd-banner | Reinstates the display of the MOTD banners. |
These commands determine whether the router will display the EXEC banner and the MOTD banner when an EXEC session is created. These banners are defined with the banner motd and banner exec commands. By default, the MOTD banner and the EXEC banner are enabled on all lines.
Disable the EXEC and MOTD banners using the no exec-banner command.
The MOTD banners can also be disabled by the no motd-banner line configuration command, which disables MOTD banners on a line. If the no exec-banner command is configured on a line, the MOTD banner will be disabled regardless of whether the motd-banner command is enabled or disabled. Table 6 summarizes the effects of the exec-banner command and the motd-banner command.
| exec-banner (default) | no exec-banner | |
|---|---|---|
| motd-banner (default) | MOTD banner EXEC banner | None |
| no motd-banner | EXEC banner | None |
For reverse Telnet connections, the EXEC banner is never displayed. Instead, the incoming banner is displayed. The MOTD banner is displayed by default, but it is disabled if either the no exec-banner command or no motd-banner command is configured. Table 7 summarizes the effects of the exec-banner command and the motd-banner command for reverse Telnet connections.
| exec-banner (default) | no exec-banner | |
|---|---|---|
| motd-banner (default) | MOTD banner incoming banner | incoming banner |
| no motd-banner | incoming banner | incoming banner |
A menu is a displayed list of actions from which a user can select without having to know anything about the underlying command-level details. A menu system (also known as a user-menu) effectively controls which functions a user can access. Figure 5 illustrates the parts that make up a typical menu.
To create menus, perform the tasks in the following sections:
Anyone who can enter configuration mode can create these menus. Keep the following guidelines in mind when you create menus:
You can specify an identifying title for the menu. To specify the menu title, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
menu name title d title d | Specifies the title for the menu.The d indicates a delimiting character. |
The following example specifies the title that is displayed when the OnRamp menu is selected. The following four main elements create the title:
The following example shows the command used to create the title for the menu shown in Figure 3, at the beginning of this section:
Router(config)# menu OnRamp title /^[[H^[[J Enter TEXT message. End with the character '/'. Welcome to OnRamp Internet Services Type a number to select an option; Type 9 to exit the menu. / Router(config)#
You can position the title of the menu horizontally by preceding the title text with blank characters. You can also add lines of space above and below the title by pressing Enter.
In this example, the title text consists of the following:
Title text must be enclosed within text delimiter characters--the slash character (/) in this example. Title text delimiters are characters that do not ordinarily appear within the text of a title, such as slash (/), double quote ("), or tilde (~). You can use any character that is not likely to be used within the text of the title as delimiter characters. Ctrl-C is reserved for special use and should not be used in the text of the title.
This title text example also includes an escape character sequence to clear the screen before displaying the menu. In this case the string ^[[H^[[J is an escape string used by many VT100-compatible terminals to clear the screen. To enter it, you must enter Ctrl-V before each escape character (^[).
You can also use the menu clear-screen command to clear the screen before displaying menus and submenus, instead of embedding a terminal-specific string in the menu title. This option uses a terminal-independent mechanism based on termcap entries defined in the router and the terminal type configured for the user's terminal. The menu clear-screen command allows the same menu to be used on multiple types of terminals instead of having terminal-specific strings embedded within menu titles. If the termcap entry does not contain a clear string, the menu system inserts 24 new lines, causing all existing text to scroll off the top of the terminal screen.
To clear the screen before displaying the menu, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
menu name clear-screen | Specifies screen clearing before displaying menus and submenus. |
The following example clears the screen before displacing the OnRamp menu or a submenu:
Router(config)# menu OnRamp clear-screen
You can specify a prompt for the menu. To specify the menu prompt, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
menu name prompt delimiter prompt delimiter | Specifies the prompt for the menu. |
Each displayed menu entry consists of the selection key (number, letter, or string) and the text describing the action to be performed. You can specify descriptive text for a maximum of 18 menu items. Because each menu entry represents a single user interface command, you must specify the menu item text one entry at a time. To specify the menu item text, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
menu name text item text | Specifies the text for the menu item. |
The following example specifies the text that is displayed for the three entries in the OnRamp menu:
Router(config)# menu OnRamp text 1 Read email Router(config)# menu OnRamp text 2 UNIX Internet Access Router(config)# menu OnRamp text 9 Exit menu system
You can provide access to context-sensitive help by creating a "help server" host and use a menu entry to make a connection to that host.
Menu selection keys do not need to be contiguous. You can provide consistency across menus by assigning a particular number, letter, or string to a special function--such as Help or Exit--regardless of the number of menu entries in a given menu. For example, menu entry H could be reserved for help across all menus.
When more than nine menu items are defined in a menu, the menu line-mode and menu single-space commands are activated automatically. The commands can be configured explicitly for menus of nine items or fewer. For more information on these commands, refer to the section "Specifying Menu Display Configuration Options" later in this chapter.
Each displayed menu entry issues a user interface command when the user enters its key. Each menu entry can have only a single command associated with it. To specify the menu item command, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
menu name command item command | Specifies the command to be performed when the menu item is selected. |
The following example specifies the commands that are associated with the three entries in the OnRamp menu:
Router(config)# menu OnRamp command 1 rlogin mailsys Router(config)# menu OnRamp command 2 rlogin unix.cisco.com Router(config)# menu OnRamp command 9 menu-exit
When a menu item allows you to make a connection, the menu item should also contain entries that can be used to resume connections; otherwise, when you try to escape from a connection and return to the menu, there is no way to resume the session. It will sit idle until you log off.
You can build the resume connection EXEC command into a menu entry so that the user can resume a connection, or you can configure the line using the escape-char none command to prevent users from escaping their sessions.
To specify connection resumption as part of the menu item command, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
menu name command item resume [connection] /connect [connect string] | Specifies the command to be performed when the menu item is selected. |
You can use the resume command in the following menu entries:
In the following example, the resume command is embedded in the menu command so that selecting the menu item either starts the specified connection session (if one is not already open) or resumes the session (if one is already open):
Router(config)# menu Duluth text 1 Read email Router(config)# menu Duluth command 1 resume mailsys /connect rlogin mailsys
In the following example, the resume command is used in a separate menu entry (entry 3) to resume a specific connection:
Router(config)# menu Duluth text 3 Resume UNIX Internet Access Router(config)# menu Duluth command 3 resume unix.cisco.com
| Command | Purpose |
|---|---|
menu name command item resume /next | Specifies resume/next connection resumption. |
The following example shows a menu entry (entry 6) created to step through all of the user's connections:
Router(config)# menu Duluth text 6 Resume next connection Router(config)# menu Duluth command 6 resume /next
When a user presses Enter without specifying an item, the router performs the command for the default item. To specify the default item, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
menu name default item | Uses the command to be performed when no item is specified. |
To create submenus that are opened by selecting a higher-level menu entry, use the menu command to invoke a menu in a line menu entry. To specify a submenu item command, use the following commands in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step 1 | menu name text item text | Specifies the menu item that invokes the submenu. |
Step 2 | menu name command item menu name2 | Specifies the command to be used when the menu item is selected. |
Step 3 | menu name2 title delimiter title2 delimiter | Specifies the title for the submenu. |
Step 4 | menu name2 text item text | Specifies the submenu item. |
Step 5 | menu name2 command item command | Specifies the commands to be used when the submenu item is selected. |
The following example specifies that the menu item (entry 8) activates the submenu in the OnRamp menu:
Router(config)# menu OnRamp text 8 Set terminal type
The following example specifies the command that is performed when the menu item (entry 8) is selected in the OnRamp menu:
Router(config)# menu OnRamp command 8 menu Terminals
The following example specifies the title for the Terminals submenu:
Router(config)# menu Terminals title / Supported Terminal Types Type a number to select an option; Type 9 to return to the previous menu.
The following example specifies the submenu items for the Terminals submenu:
Router(config)# menu Terminals text 1 DEC VT420 or similar Router(config)# menu Terminals text 2 Heath H-19 Router(config)# menu Terminals text 3 IBM 3051 or equivalent Router(config)# menu Terminals text 4 Macintosh with gterm emulator Router(config)# menu Terminals text 9 Return to previous menu
The following example specifies the commands associated with the items in the Terminals submenu:
Router(config)# menu Terminals command 1 term terminal-type vt420 Router(config)# menu Terminals command 2 term terminal-type h19 Router(config)# menu Terminals command 3 term terminal-type ibm3051 Router(config)# menu Terminals command 4 term terminal-type gterm Router(config)# menu Terminals command 9 menu-exit
When you select entry 8 on the main menu, the Terminals submenu appears:
Supported Terminal Types
Type a number to select an option;
Type 9 to return to the previous menu.
1 DEC VT420 or similar
2 Heath H-19
3 IBM 3051 or equivalent
4 Macintosh with gterm emulator
9 Return to previous menu
|
Note If you nest too many levels of menus, the system prints an error message on the terminal and returns to the previous menu level. |
A hidden menu entry is a menu item that contains a selection key but no associated text describing the action to be performed. Include this type of menu entry to aid system administrators who help users. The normal procedure is to specify a menu command but omit specifying any text for the item. To specify a hidden menu item, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
menu name command item command | Specifies the command to be used when the hidden menu entry is selected. |
The following example shows the command associated with the submenu entry in the OnRamp menu:
Router(config)# menu OnRamp command 7 show whoami
Comm Server "cs101", Line 0 at 0 bps. Location "Second floor, West" Additional data: Terminals submenu of OnRamp Internet Access menu
To prevent the information from being lost if the menu display clears the screen, this command always displays a More prompt before returning.
In addition to the menu clear-screen command, described in the section "Specifying the Menu Title," the following are the three other menu commands that define menu functions:
In a menu of nine or fewer items, you ordinarily select a menu item by entering the item number or a letter. In line mode, you select a menu entry by entering the item key and pressing Enter. The line mode allows you to backspace over the selection and enter another before pressing Enter to issue the command. This function allows you to change the selection before you invoke the command.
To invoke the line-mode option, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
menu name line-mode | Specifies line-mode operation. |
The line-mode option is invoked automatically when more than nine menu items are defined, but it can also be configured explicitly for menus of nine items or fewer.
In order to use strings as selection keys, you must enable the menu line-mode command.
If there are nine or fewer menu items, the Cisco IOS software ordinarily displays the menu items double-spaced. In a menu of more than nine items, the single-space option is activated automatically to fit the menu into a normal 24-line terminal screen. However, the single-space option also can be configured explicitly for menus of nine or fewer items.
To invoke the single-space option, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
menu name single-space | Specifies single-space operation. |
The status-line option displays a line of status information about the current user at the top of the terminal screen before the menu title is displayed. This status line includes the router's host name, the user's line number, and the current terminal type and keymap type (if any).
To display the status-line option, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
menu name status-line | Displays a status line when using a menu. |
To configure per-item options, use either or both of the following commands in global configuration mode:
| Command | Purpose |
|---|---|
menu name options item pause | After the command is issued, pauses before redrawing the menu. Enter this command once for each menu item that pauses. |
menu name options item login | Requires a login before the command. Enter this command once for each menu item that requires a login. |
To invoke the menu, use the following command at the EXEC prompt:
| Command | Purpose |
|---|---|
menu name |
You can define menus containing privileged EXEC commands, but users must have privileged access when they start up the menu.
To ensure that a menu is automatically invoked on a line, make sure the menu does not have any exit paths that leave users in an interface they cannot operate, then configure that line with the command autocommand menu menu_name.
Menus also can be invoked on a per-user basis by defining an autocommand for that local username.
The following example invokes the OnRamp menu:
Router> menu OnRamp
Welcome to OnRamp Internet Services
Type a number to select an option;
Type 9 to exit the menu.
1 Read email
2 UNIX Internet access
3 Resume UNIX connection
6 Resume next connection
9 Exit menu system
To delete the menu from the configuration, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
no menu name | Deletes the menu by specifying the menu name. |
In order to use the menu again, you must reconfigure the entire menu again.
The following example deletes the OnRamp menu from the configuration:
Router(config)# no menu OnRamp
This section contains the following examples:
Router> login Username: user2 Password: % Access denied Still logged in as "user1"
Next, the user attempts the login change again, with the username user2, but enters the correct (original) password. This time the password matches the current login information, the login username is changed to user2, and the user is allowed access to the EXEC at the user-level.
router> login Username: user2 Password: router>
In the following example, user1 specifies the TACACS host host1 to authenticate the password:
router> login Username: user1@host1 Translating "HOST1"...domain server (131.108.1.111) [OK]
The following example clears a TCP connection using its TTY line number. The show tcp command displays the line number (tty2) that is used in the clear tcp command.
Router# show tcp
tty2, virtual tty from host router20.cisco.com
Connection state is ESTAB, I/O status: 1, unread input bytes: 0
Local host: 171.69.233.7, Local port: 23
Foreign host: 171.69.61.75, Foreign port: 1058
Enqueued packets for retransmit: 0, input: 0, saved: 0
Event Timers (current time is 0x36144):
Timer Starts Wakeups Next
Retrans 4 0 0x0
TimeWait 0 0 0x0
AckHold 7 4 0x0
SendWnd 0 0 0x0
KeepAlive 0 0 0x0
GiveUp 0 0 0x0
PmtuAger 0 0 0x0
iss: 4151109680 snduna: 4151109752 sndnxt: 4151109752 sndwnd: 24576
irs: 1249472001 rcvnxt: 1249472032 rcvwnd: 4258 delrcvwnd: 30
SRTT: 710 ms, RTTO: 4442 ms, RTV: 1511 ms, KRTT: 0 ms
minRTT: 0 ms, maxRTT: 300 ms, ACK hold: 300 ms
Router# clear tcp line 2
[confirm]
[OK]
The following example clears a TCP connection by specifying its local router host name and port and its remote router host name and port. The show tcp brief command displays the local (Local Address) and remote (Foreign Address) host names and ports to use in the clear tcp command.
Router# show tcp brief
TCB Local Address Foreign Address (state)
60A34E9C router1.cisco.com.23 router20.cisco.1055 ESTAB
Router# clear tcp local router1 23 remote router20 1055
[confirm]
[OK]
The following example clears a TCP connection using its TCB address. The show tcp brief command displays the TCB address to use in the clear tcp command.
Router# show tcp brief
TCB Local Address Foreign Address (state)
60B75E48 router1.cisco.com.23 router20.cisco.1054 ESTAB
Router# clear tcp tcb 60B75E48
[confirm]
[OK]
The following example shows how to use the banner global configuration commands and the no exec-banner line configuration command to notify your users that the server is going to be reloaded with new software:
! The EXEC and MOTD banners are inappropriate for the VTYs. line vty 0 4 no exec-banner ! banner exec / This is Cisco Systems training group router. Unauthorized access prohibited. / ! banner incoming / You are connected to a Hayes-compatible modem. Enter the appropriate AT commands. Remember to reset anything you have changed before disconnecting. / ! banner motd / The router will go down at 6pm for a software upgrade /
When someone connects to the router, the MOTD banner appears before the login prompt. After the user successfully logs in to the router, the EXEC banner or incoming banner will be displayed, depending on the type of connection. For a reverse Telnet login, the incoming banner will be displayed. For all other connections, the router will display the EXEC banner.
The following example sets the SLIP-PPP banner using several tokens and the percent sign (%) as the delimiting character:
router(config)# banner slip-ppp %
Enter TEXT message. End with the character '%'.
Starting $(encap) connection from $(gate-ip) to $(peer-ip) using a maximum packet size of $(mtu) bytes... %
When you enter the slip command, you will see the following banner. Notice that the $(token) syntax is replaced by the corresponding configuration variable.
Starting SLIP connection from 192.168.69.96 to 172.16.80.8 using a maximum packet size of 1500 bytes...
The following example allows menu users to Telnet to one of three different machines. The user can also view the output of the show user command and exit the menu. One hidden menu item, specified by the selection here, allows system administrators to view the current software version.
menu new title ^C Telnet Menu ^C menu new prompt ^C Please enter your selection: ^C menu new text 1 telnet system1 menu new command 1 telnet system1 menu new options 1 pause menu new text 2 telnet system2 menu new command 2 telnet system2 menu new options 2 pause menu new text b telnet systemblue menu new command b telnet systemblue menu new options b pause menu new text me show user menu new command me show user menu new options me pause menu new command here show version menu new text Exit Exit menu new command Exit menu-exit menu new clear-screen menu new status-line menu new default me menu new line-mode !
Posted: Wed Aug 16 20:12:26 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.