try this command which will tell what packet and source are sending the traffic with ttl of 1 show buffer input-interface <> header/packet
On Mon, Dec 7, 2009 at 8:06 PM, Drew Weaver <[email protected]> wrote: > Drew Weaver wrote: > > Hi, > > > > It is possible. > > > > We're a co-location style facility where we do not have direct > > control over what the end systems do. > > > > I would think that a system like the 6500 should be able to handle a > > little UDP traffic without losing its mind but i've been wrong about > > things in the past =) > > Well, mtr is a traceroute style program, and one that can be quite > aggressive at that (though useful). If it's sending a lot of packets at > your router which have TTL=1 when they arrive, then that's a lot of CPU > punts. > > You didn't specify whether anything was *wrong* here; are you > experiencing problems, or just counter anomalies? > > I take it the port-channel is in routed mode, rather than switchport? > -------------- > > The problem is I'm seeing queue drops, so my first reaction to that was to > see what kind of packets were being queued. > > You are correct the interface is not a switchport and has an IP assigned to > it. > > thanks, > -Drew > > > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > -- Thanks Kamlesh Sharma _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
