At 04:19 AM 7/2/01, FELIX KISSIEDU wrote:
>try "debug serial interface" command
That won't help him. He wanted to check ip traffic details between two
points on a point-to-point connection. Debug serial shows keepalives and
low-level serial interface stuff.
To look at ip traffic he should use debug ip packet detail. (Be careful on
a busy production router. This displays a lot of info, and when you ask a
router to use CPU cycles to display output on the console instead of using
those cycles to route packets, you're asking for trouble.)
To see traffic for just see one interface, try
debug condition interface interface
If you enter the debug condition interface command, the debugging output
will be turned off for all interfaces except the specified interface. I've
never tried this. I just discovered it in the documentation. It may be new
in 12.0.
To see specific traffic, he could apply an access list to debug ip packet,
as someone else suggested. But how much IP traffic does this point-to-point
link carry? It probably carries traffic for multiple IP sessions. So the
access list idea could be impractical... Remember that IP addresses are
end-to-end.
So the interface condition is probably a better way to do it.
Priscilla
________________________
Priscilla Oppenheimer
http://www.priscilla.com
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=10681&t=10598
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
