If you want to know which session has been suspended most recently, look for the session listed in the show session command that has an asterisk to the left of the entry. This is particularly dangerous when you are changing the configuration or using potentially damaging exec commands-be careful about what router you are actually using when you have suspended Telnet connections. With a suspended Telnet connection, you also just happened to reconnect to another router. That is fine, until you realize how much you tend to press the Enter key occasionally to clear some of the clutter from the screen.
#HOW TO USE TELNET CISCO SOFTWARE#
The interesting and potentially dangerous nuance here is that if a Telnet session is suspended and you simply press Enter, Cisco IOS Software resumes the connection to the most recently suspended Telnet connection. For instance, just typing the command 2 does the same thing as typing the command resume 2. (The where command provides the same output.) Also, instead of using the resume command, you can just use the session number as a command. The resume command can be used to resume either connection however, the resume command requires a connection ID, which is shown in the show sessions command. The two connections can be suspended or resumed easily.
Then, after Telnetting to New York, that connection was suspended. After Telnetting to Milwaukee, the Telnet connection was suspended. Example 13-10 begins with the Cincy command prompt that would be seen in Bench's Telnet window because the user at Bench Telnetted into Cincy first. The play-by-play notes in the example explain most of the details. (Note: User pressed Ctrl-Shift-6 and then x) Cincy#disconnect 2 (Done with New York, terminate Telnet)Ĭlosing connection to NewYork (Just press Enter to confirm) (Pressing Enter resumes most recently suspended active Telnet) (Note: User pressed Ctrl-Shift-6 and then x) (Tired of Milwaukee again can't imagine why!) Cincy#disconnect 1 (No more need to use Milwaukee Telnet terminated!)Ĭlosing connection to milwaukee (User presses Enter to confirm) (Note: User pressed Ctrl-Shift-6 and then x) (User wants to go back to Cincy) Cincy# (WOW! User just pressed Enter and resumes the last Telnet) Milwaukee> (User can type commands on Milwaukee) (where does the same thing) Address Byte Idle Conn NameĬincy#resume 1 (Resume connection 1 (see show session) to Milwaukee) (This command lists suspended Telnet sessions) Address Byte Idle Conn Name (Note: User pressed Ctrl-Shift-6 and then x)
NewYork> (User can now type commands on New York) (User is getting into New York now, based on telnet NewYork command) (Note: User pressed Ctrl-Shift-6 and then x) Cincy#telnet NewYork (User back at Cincy because Telnet was suspended)
Password: (User plugs in password, can type commands at Milwaukee)Įxample 13-10 Telnet Suspensions (Continued) Example 13-10 shows example output, with annotations to the side.Ĭincy#telnet milwaukee (User issues command to Telnet to Milwaukee) The example begins with Bench already logged into Cincy. The user then Telnets to New York and again suspends the connection. When in Milwaukee, the user suspends the Telnet by pressing Ctrl-Shift-6, followed by pressing the letter x. When in Cincy, the user Telnets to Milwaukee. In the figure, the router administrator is using Bench to Telnet into the Cincy router. To understand the suspend function, you should to refer to the network diagram in Figure 13-4. One of the most important features of the telnet command is the suspend feature. The telnet IOS exec command enables you to Telnet from one Cisco device to another in practical use, it is typically to another Cisco device.