From: Reggie Terrell (rterrell@xxxxxxxxxxxxxxxx)
Date: Fri Apr 07 2000 - 10:25:39 GMT-3
Mike,
Thanks for the quick reply. I am using a 2509 as my terminal server. It is
very possible that the debug sessions that I could not stop where coming from m
y
terminal server. I tried to cycle through as many open sessions as I could to
turn off debugging, but nothing seemed to work. If this happens again, I will
be sure that the terminal server's debug session is turned off.
Thanks for the advice about naming the sessions. I think I'm doing a good job
there, in as much as I am aware of the session and host. I am just unaware of
the source of the debugging output.
Thanks again for your quick reply,
Reggie
"LESH, MIKE" wrote:
> Reggie,
> Just because I'm curious, what kind for terminal server are you
> using? In my experience, the Cisco routers and terminal servers do not
> forward messages from sessions that you are not currently connected to. This
> would imply that debug output would only be coming from the device you are
> directly connected to, which if you are seeing multiple messages would be
> the terminal server. The attached devices will log their messages to memory
> until you return to them, then dump them in your lap. :-)
> As far as being able to distinguish your connections, may I suggest
> giving your connections names via the connection name command, this may help
> to tell and keep straight where you are. Also, I use a menu on the device(s)
> that I have connections from; such as;
> ...
> interface Loopback0
> ip address 193.1.1.1 255.255.255.0
> ...
> ip host Port6 2006 193.1.1.1
> ... , etc.
> menu ccie text 6 Local Open Port 06
> menu ccie command 6 resume Port6 /connect telnet Port6
> ... , etc.
>
> By doing this, I can worry about getting on with what I'm studying,
> and not get worried about where I connected things. Also, it makes it a snap
> to get back to where I left debug running, etc.
> I trust this helps,
> Mike
>
> ----------
> From: Reggie Terrell[SMTP:rterrell@bellatlantic.net]
> Reply To: Reggie Terrell
> Sent: Thursday, April 06, 2000 9:20 PM
> To: ccielab@groupstudy.com
> Subject: Turning off Debug
>
> Hi group,
>
> I have noticed that there are times when I use debug that I can not
> turn off
> debugging. The comm server has multiple sessions established and it
> is
> difficult to tell what router has originated the debug sessions.
>
> Is there any way to figure out what session is generating a debug
> output when
> there are multiple sessions established?
>
> On some commands like debug ip packet, I can tell by looking at the
> debug
> output which lists the source address of the router. On most other
> debug
> commands, it is not so obvious.
>
> Thanks in advance,
>
> Reggie
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:13 GMT-3