From: Daniel M. Dawson (dandawson@xxxxxxxxxx)
Date: Tue Jan 30 2001 - 01:51:23 GMT-3
In the terminal server do a show sesion to see what sessions are connected
already. Type the number of the session followed by <enter key> and it
reconnects you to that session. type disconnect <session number> to get rid
of a particular session (nice if you get a router connected in the wrong
order). logout out of the terminal server and it clears all your sessions
and you can start fresh. in the example below the "õ" is a representation
of when I typed <control-shift-6> x to exit the router back to the terminal
server. The * next to the connection number is the default session (the
last one you were in) and if you simply hit enter the terminal server will
take you back to that session. This works great for speed and mobility if
you set up the console cables to match the router numbers and the reverse
telnet numbers and log in to each router first in order. Then you never
have to type "clear line <async line number>". Just type the number of the
router you want to go to. If you mess up on the order use the disconnect
command.
TermServ#sh ses
Conn Host Address Byte Idle Conn Name
* 1 c1 172.22.88.1 0 1 c1
2 c2 172.22.88.1 3 04:42 c2
TermServ#c5
Translating "c5"
Trying C5 (172.22.88.1, 2005)... Open
R5#õ
TermServ#sh ses
Conn Host Address Byte Idle Conn Name
1 c1 172.22.88.1 0 1 c1
2 c2 172.22.88.1 3 04:42 c2
* 3 c5 172.22.88.1 0 0 c5
TermServ#c4
Translating "c4"
Trying C4 (172.22.88.1, 2004)... Open
R4#õ
TermServ#sh ses
Conn Host Address Byte Idle Conn Name
1 c1 172.22.88.1 0 1 c1
2 c2 172.22.88.1 3 04:43 c2
3 c5 172.22.88.1 0 0 c5
* 4 c4 172.22.88.1 0 0 c4
TermServ#
oops...session three should be connected to c3 not c5!
TermServ#disconnect 3
Closing connection to c5 [confirm]
TermServ#sh ses
Conn Host Address Byte Idle Conn Name
1 c1 172.22.88.1 0 2 c1
2 c2 172.22.88.1 3 04:43 c2
* 4 c4 172.22.88.1 0 0 c4
TermServ#c3
Translating "c3"
Trying C3 (172.22.88.1, 2003)... Open
R3#õ
TermServ#sh ses
Conn Host Address Byte Idle Conn Name
1 c1 172.22.88.1 0 2 c1
2 c2 172.22.88.1 3 04:43 c2
* 3 c3 172.22.88.1 0 0 c3
4 c4 172.22.88.1 0 0 c4
TermServ#
TermServ#logout
(You have open connections) [confirm]
Closing: c1 !
Closing: c2 !
Closing: c3 !
Closing: c4 !
TermServ#
TermServ#sh ses
% No connections open
TermServ#
Daniel M. Dawson
Network Systems Consultant
Network Care Professional Services (NPS)
Lucent Technologies
Mobile: (405) 850-1493
Pager: (800) 622-9202
E-mail: dandawson@lucent.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Halaska, David
Sent: Monday, January 29, 2001 10:06 AM
To: 'Chuck Larrieu'; CCIE_Lab Groupstudy List
Subject: RE: Lab bushwhacks - terminal server
I think once you have used one of your terminal server lines to connect to a
router, like RT1, then you can just get back in but typing 1. A friend
suggested to me that you do the following when you first get into the
terminal server.
log into every router in order using ctrl shift 6 x to get out. Once you do
that, you should be able to get in by using the line number. So you would
use 3 instead of RT3.
David Halaska
-----Original Message-----
From: Chuck Larrieu [mailto:chuck@cl.cncdsl.com]
Sent: Sunday, January 28, 2001 1:39 PM
To: CCIE_Lab Groupstudy List
Subject: Lab bushwhacks - terminal server
OK, I think I am starting to get a feel for terminal server gotcha's. And
based solely on my experience here at home, and never having been in the Lab
itself, but trying to anticipate the kinds of things that can happen during
troubleshooting.....
It seems that the asynch lines can get "hung" for whatever reason. I am
finding that even after fooling around doing things like changing the flow
control that often I can still get into most of my routers. Occasionally, I
will get a "connection refused" from one or two of them.
This of course could be disastrous if it were to happen during any part of
the lab prior to troubleshooting. It could also be one way a crafty Lab
Proctor might try to bushwhack someone. Screw with the terminal server
settings and let the unprepared candidate waste his three hours getting the
TS to connect!
Some combination of clear tty line X or clear line X seems to do the trick.
Never hurts to do both.
Chuck
http://www.1112.net/lastpage.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:48 GMT-3