From: Narcis Micsoniu (micsoniu@telus.net)
Date: Sun Oct 03 2004 - 20:53:22 GMT-3
I subscribe.
Here is another question related to a similar issue: is there a way to
log/see the type of protocol type specified in the Layer 2 frame (LAN/WAN)
on a router/switch without engaging a sniffer?
In other words, is there a magical IOS command which might do just that?
Thanks
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Brant I. Stevens
Sent: Sunday, October 03, 2004 9:48 AM
To: ccie2be; ccielab@groupstudy.com; Moffat, Ed
Subject: Re: Debug ip packet for an interface
Tim,
Consider one more member of the minority enlightened by your asking this
question.
-Brant
On 10/01/2004 11:34 AM, "ccie2be" <ccie2be@nyc.rr.com> wrote:
> Hey Ed,
>
> Thanks for pointing that out.
>
> I'm amazed that for such a seemingly useful command, I'm first learning
> about it now. Almost every time I've run a debug, I've thought about how
> much easier it would be if the debug output weren't cluttered up with
> traffic crossing other interfaces that wasn't relevant to the problem I'm
> trying to solve.
>
> Kind of makes me wonder if I was part of a small minority of people who
> didn't know about this command or part of the vast majority who didn't
know.
>
> Well, in any case, I know about it now and so does the rest of the GS
> community on account of you and a couple of others, so I guess this was a
> good question to ask.
>
> Tim
>
> ----- Original Message -----
> From: "Moffat, Ed" <EMoffat@FSCI.com>
> To: "ccie2be" <ccie2be@nyc.rr.com>
> Sent: Friday, October 01, 2004 11:19 AM
> Subject: RE: Debug ip packet for an interface
>
>
> You've got it.
>
> However, I would set the condition first before issuing the debug
> command. That is especially important if you have lots of interfaces and
> processed switched packets as the router could get slammed very quickly
> with your debug. By setting the condition first, it makes sure that when
> you issue the debug command that it will only be applied to the
> interface you want.
>
> -Ed-
>
> -----Original Message-----
> From: ccie2be [mailto:ccie2be@nyc.rr.com]
> Sent: Friday, October 01, 2004 7:17 AM
> To: Moffat, Ed; Group Study
> Subject: Re: Debug ip packet for an interface
>
> Hi Ed,
>
> Thanks for getting back to me. I appreciate it.
>
> Let me make sure I'm clear about what you're saying.
>
> Let's say I want to see all packets crossing int bri 0.
>
> Would I use both debug commands like this?
>
> debup ip packet
> debug condition interface bri 0
>
> Thanks, Tim
>
> ----- Original Message -----
> From: "Moffat, Ed" <EMoffat@FSCI.com>
> To: "ccie2be" <ccie2be@nyc.rr.com>; "Group Study"
> <ccielab@groupstudy.com>
> Sent: Friday, October 01, 2004 10:08 AM
> Subject: RE: Debug ip packet
>
>
> debug condition interface <interface>
>
> show debug condition will show you what conditions are set
>
> no debug condition <#> or no debug condition <condition> will remove
> the settings.
>
> Be sure to do this when you are done or else the condition will remain
> set until you reload your router. The undebug all command does not
> remove the condition.
>
> HTH
>
> -Ed Moffat-
> CCIE #13196
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> ccie2be
> Sent: Friday, October 01, 2004 6:33 AM
> To: Group Study
> Subject: Debug ip packet
>
> Hi guys,
>
> I hope this isn't a totally stupid question, but...
>
> Is there a way to configure debug ip packet so that I can see just the
> packets coming in or leaving a given interface?
>
> I know an acl an be attached to debug ip packet but I can't figure out a
> way to specify just a single interface.
>
> Thanks alot, Tim
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Nov 06 2004 - 17:11:42 GMT-3