From: Thomas Larus (tlarus@xxxxxxx)
Date: Thu Nov 29 2001 - 10:04:29 GMT-3
I was doing a simple practice exercise where I needed to add passwords
and exec timeout 0 to all vty, aux and con lines. Once I did that, I
had trouble getting back to the remote routers because my session was
still up. You know, how you have to use resume rather than the host
name once you have session going. At some point, I rebooted my terminal
server, but the remote router still acted like there was a session
clogging their con port. Clear line was not an option because there was
no longer a session as far as the rebooted termserver was concerned. I
went to the remote router with my PC console cable, tried different con
port settings, and logged out. Still no luck.
I finally rebooted the remote routers that were giving me trouble, and
everything was fine. Probably something simple, but I need to
understand what was wrong, since one does not have direct access to the
routers in the Lab and I would like to spare myself the embarrassment
and time waste of asking the proctor to do physical reboots. He or she
might well say, you need to figure out a workaround, because someday
you will need to fix configs for equipment thousands of miles away,
where a direct link to the console port is not available. (He or she
will probably not say all that, but that will be the thinking).
BTW, could someone please explain transport input preferred.
Thanks in advance,
Thomas Larus
This archive was generated by hypermail 2.1.4 : Fri Jun 21 2002 - 06:45:25 GMT-3