Hi Group,
Recently due to some problems my colleague issued a debug ip error command
on the rsm.
The problem is we could not stop the process at all. We tried using the no
debug ip error but it never came out of the process, there was a lot of
details regarding routing info . Luckily for us
doesn't even undebug all works
-Original Message-
From: Gayathri [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 03, 2001 10:31 AM
To: [EMAIL PROTECTED]
Subject: debug ip error
Hi Group,
Recently due to some problems my colleague issued a debug ip error command
on the rsm.
have yout tried command 'no debug all'
ma
-Original Message-
From: gayathri [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 03, 2001 12:01 PM
To: cisco [EMAIL PROTECTED]
Cc: gayathri [EMAIL PROTECTED]
Subject: debug ip error
Hi Group,
Recently due to som
ue issued a debug ip error command
> on the rsm.
>
> The problem is we could not stop the process at all. We tried using the no
> debug ip error but it never came out of the process, there was a lot of
> details regarding routing info . Luckily for us we had HSRP.
>
> We had to
nd
>enter command
>sequence to get out of debug mode.
>
>Gayathri wrote:
>
> > Hi Group,
> >
> > Recently due to some problems my colleague issued a debug ip error command
> > on the rsm.
> >
> > The problem is we could not stop the process at all
>or it's undeb all (used to be even easier, in "the good ole days", u
>al worked)
>
>if that was a production router, then you need to be severely warned
>about using the debug commands (especially the packet-trapping
>commands) on a production machine. Just the volume of ASCII
>spewing onto
"Howard C. Berkowitz" <[EMAIL PROTECTED]> wrote:
> Ah, but it was even worse in the Old Days of wooden ships, steel men,
> and xGS routers. Each telnet session on an MGS router took up about
> 20% of the CPU, at least around release 9.0. That was the show
> process overhead of just being log
gt;
> > Recently due to some problems my colleague issued a debug ip error
command
> > on the rsm.
> >
> > The problem is we could not stop the process at all. We tried using the
no
> > debug ip error but it never came out of the process, there was a lot of
> >
8 matches
Mail list logo
