From: Jv (jayavenkad@hotmail.com)
Date: Tue Jan 14 2003 - 22:04:01 GMT-3
Hi all,
I hava a similar issue on my 2600 Router. When I try the same debug
ip icmp command and also any of the debug commands, through my telnet
session with terminal monitor enabled....I never get any output displayed in
my telnet session.....
Appreciate any Clarification...
Thanks!
Jv.
----- Original Message -----
From: "tan" <tan@dia.janis.or.jp>
To: "'Matthew Poole'" <matthew.poole@blueyonder.co.uk>;
<ccielab@groupstudy.com>
Cc: "'Joe Chang'" <changjoe@earthlink.net>
Sent: Wednesday, January 15, 2003 6:11 AM
Subject: RE: lack of output in debug ip icmp
> Thanks, I was aware debug ip packet detail had outgoing icmps, I was just
> curious why debug ip icmp would not. Not a burning issue.
>
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> > Matthew Poole
> > Sent: Wednesday, January 15, 2003 4:04 AM
> > To: ccielab@groupstudy.com
> > Cc: Joe Chang; tan
> > Subject: Re: lack of output in debug ip icmp
> >
> >
> > For a variation on Joe Changs post you could add detail to
> > the debug, this
> > will show your ICMP going out.
> >
> > R9#ping 10.1.1.1
> >
> >
> > Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds:
> > !!!!!
> > Success rate is 100 percent (5/5), round-trip min/avg/max =
> > 28/30/32 ms
> > R9#
> > 4d08h: IP: s=10.1.1.2 (local), d=10.1.1.1 (Serial0), len 100, sending
> > 4d08h: ICMP type=8, code=0
> > 4d08h: IP: s=10.1.1.1 (Serial0), d=10.1.1.2 (Serial0), len 100, rcvd 3
> > 4d08h: ICMP type=0, code=0
> > 4d08h: IP: s=10.1.1.2 (local), d=10.1.1.1 (Serial0), len 100, sending
> > 4d08h: ICMP type=8, code=0
> > 4d08h: IP: s=10.1.1.1 (Serial0), d=10.1.1.2 (Serial0), len 100, rcvd 3
> > 4d08h: ICMP type=0, code=0
> > 4d08h: IP: s=10.1.1.2 (local), d=10.1.1.1 (Serial0), len 100, sending
> > 4d08h: ICMP type=8, code=0
> >
> > ----- Original Message -----
> > From: "Joe Chang" <changjoe@earthlink.net>
> > To: <ccielab@groupstudy.com>
> > Sent: Thursday, January 09, 2003 3:20 AM
> > Subject: Re: lack of output in debug ip icmp
> >
> >
> > > To debug outgoing ip packets you could try this:
> > >
> > > access-list 100 permit icmp any any
> > > debug ip packet 100
> > >
> > >
> > > ----- Original Message -----
> > > From: "Joe" <groupstudy@comcast.net>
> > > To: "'tan'" <tan@dia.janis.or.jp>; "'Ccielab (E-mail)'"
> > > <ccielab@groupstudy.com>
> > > Sent: Wednesday, January 08, 2003 11:27 PM
> > > Subject: RE: lack of output in debug ip icmp
> > >
> > >
> > > > Sometimes you gotta disable fast switching.
> > > >
> > > > -----Original Message-----
> > > > From: nobody@groupstudy.com
> > [mailto:nobody@groupstudy.com] On Behalf Of
> > > > tan
> > > > Sent: Wednesday, January 08, 2003 5:39 AM
> > > > To: Ccielab (E-mail)
> > > > Subject: OT: lack of output in debug ip icmp
> > > >
> > > >
> > > > Is it normal that typical outgoing pings are not output
> > to console under
> > > > "debug ip icmp"? Only return pings and other icmp types
> > are included,
> > > > but not standard echo request. I have been bit a few
> > times just assuming
> > > > my ping went out and was troubleshooting the return path,
> > when it turned
> > > > out it never left the router because unroutable. I have found only
> > > > "debug ip pack det" will include outgoing ping? I know
> > not much can be
> > > > done about it, but anyone else find it odd or offer an
> > explanation why?
> > > > .
> > > .
> > .
> .
.
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:49 GMT-3