If you connect to a device console through a terminal server session.
How do you execute the break sequence without the terminal server
dropping you out of
your session. (using a Cisco 2600 router with a 32 port async card)
That break sequence leaves the traceroute going and your console
session logged in, but suspends your connection to the device and
returns you to the exec of the terminal server.

I end up having to watch the traceroute complete, which is painful if
it isn't reaching its destination quickly.

Any ideas, anyone?
Kevin

In article <9fd85d30.0407161446.1dd9a696@posting.google.com>,
k_widner@yahoo.com says...
> If you connect to a device console through a terminal server session.
> How do you execute the break sequence without the terminal server
> dropping you out of
> your session. (using a Cisco 2600 router with a 32 port async card)
> That break sequence leaves the traceroute going and your console
> session logged in, but suspends your connection to the device and
> returns you to the exec of the terminal server.
>
> I end up having to watch the traceroute complete, which is painful if
> it isn't reaching its destination quickly.


What exactly are you typing? SHIFT-CTRL-6 or SHIFT-CTRL-6 then X


--

hsb

"Somehow I imagined this experience would be more rewarding" Calvin
*************** USE ROT13 TO SEE MY EMAIL ADDRESS ****************
********************************************************************
Due to the volume of email that I receive, I may not not be able to
reply to emails sent to my account. Please post a followup instead.
********************************************************************

Kevin Widner <k_widner@yahoo.com> wrote:
: If you connect to a device console through a terminal server session.
: How do you execute the break sequence without the terminal server
: dropping you out of
: your session. (using a Cisco 2600 router with a 32 port async card)
: That break sequence leaves the traceroute going and your console
: session logged in, but suspends your connection to the device and
: returns you to the exec of the terminal server.

[...]

: Any ideas, anyone?
: Kevin

I haven't done it for a while, and don't have any routers setup to
test at this momment, but I seem to recall that you can execute
the break sequecne twice in that situation.

First escape sequence wakes up the first device, and the second will get
passed on to the connected piece of equipment. If you have three
routers cascaded, you'd hit the break sequence three times. (And so
on...)

Yes, two escape sequence will send the break to the current session.

It is Ctrl+shift+6 and again Ctrl+shift+6

Also, you could change the escape sequence for the current session by
cmd "terminal escape-character"

R#terminal escape-character ?
BREAK Cause escape on BREAK
CHAR or <0-255> Escape character or its ASCII decimal equivalent
DEFAULT Use default escape character
NONE Disable escape entirely
soft Set the soft escape character for this line

R#

OR..,

You can change the escape sequence for the console line using cmd
"escape-character"

R#lin con 0
R#escape-character ?
BREAK Cause escape on BREAK
CHAR or <0-255> Escape character or its ASCII decimal equivalent
DEFAULT Use default escape character
NONE Disable escape entirely
soft Set the soft escape character for this line

R#

A brief read on this @
http://www.cisco.com/univercd/cc/td/doc/product/software/ssr83/rpc_r/48118.htm#xtocid2096016

HTH

Solomon
John Osmon <josmon@news.rigozsaurus.com> wrote in message news:<40f8bc70@nntp.zianet.com>...
> Kevin Widner <k_widner@yahoo.com> wrote:
> : If you connect to a device console through a terminal server session.
> : How do you execute the break sequence without the terminal server
> : dropping you out of
> : your session. (using a Cisco 2600 router with a 32 port async card)
> : That break sequence leaves the traceroute going and your console
> : session logged in, but suspends your connection to the device and
> : returns you to the exec of the terminal server.
>
> [...]
>
> : Any ideas, anyone?
> : Kevin
>
> I haven't done it for a while, and don't have any routers setup to
> test at this momment, but I seem to recall that you can execute
> the break sequecne twice in that situation.
>
> First escape sequence wakes up the first device, and the second will get
> passed on to the connected piece of equipment. If you have three
> routers cascaded, you'd hit the break sequence three times. (And so
> on...)

Yes, two escape sequence will send the break to the current session. (
for this scenario)

It is Ctrl+shift+6 and again Ctrl+shift+6

Also, you could change the escape sequence for the current session by
cmd "terminal escape-character"

R#terminal escape-character ?
BREAK Cause escape on BREAK
CHAR or <0-255> Escape character or its ASCII decimal equivalent
DEFAULT Use default escape character
NONE Disable escape entirely
soft Set the soft escape character for this line

R#

OR..,

You can change the escape sequence for the console line using cmd
"escape-character"

R#lin con 0
R#escape-character ?
BREAK Cause escape on BREAK
CHAR or <0-255> Escape character or its ASCII decimal equivalent
DEFAULT Use default escape character
NONE Disable escape entirely
soft Set the soft escape character for this line

R#

A brief read on this @
http://www.cisco.com/univercd/cc/td/doc/product/software/ssr83/rpc_r/48118.htm#xtocid2096016

HTH

Solomon

John Osmon <josmon@news.rigozsaurus.com> wrote in message news:<40f8bc70@nntp.zianet.com>...
> Kevin Widner <k_widner@yahoo.com> wrote:
> : If you connect to a device console through a terminal server session.
> : How do you execute the break sequence without the terminal server
> : dropping you out of
> : your session. (using a Cisco 2600 router with a 32 port async card)
> : That break sequence leaves the traceroute going and your console
> : session logged in, but suspends your connection to the device and
> : returns you to the exec of the terminal server.
>
> [...]
>
> : Any ideas, anyone?
> : Kevin
>
> I haven't done it for a while, and don't have any routers setup to
> test at this momment, but I seem to recall that you can execute
> the break sequecne twice in that situation.
>
> First escape sequence wakes up the first device, and the second will get
> passed on to the connected piece of equipment. If you have three
> routers cascaded, you'd hit the break sequence three times. (And so
> on...)