This isn't entirely correct. On our switching platforms this is still forwarded in hardware. There is no way you could SPAN line rate traffic through the CPU of most Cisco switches. If it is ERSPAN or something that requires encapsulation it might be.
For EPC on the software based ISRs, this is CPU driven, but all traffic is centrally forwarded on the CPU. -Pete On Thu, Dec 2, 2010 at 12:38 PM, raymondh (NSP) <raymondh....@gmail.com> wrote: > SPAN is too CPU based. > As per one of the members proposed, use netflow that's the best way to > achieve. > if you do have a heavy load, set a high sampling rate. > > > --raymondh > > On 03-Dec-2010, at 12:17 AM, Joe Loiacono wrote: > >> cisco-nsp-boun...@puck.nether.net wrote on 12/01/2010 09:51:44 PM: >> >>> How I am able to see traffic (source IP, destination IP and port) which >> is >>> passing from Cisco routers, from specific interface or as a whole. >>> >>> Which is easiest and troubleless way to achieve this. Kindly also guide >> me >>> with full set of commands to achieve this. >> >> Try IP Accounting: >> >> http://www.ciscopress.com/articles/article.asp?p=764234 >> _______________________________________________ >> cisco-nsp mailing list cisco-...@puck.nether.net >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ > > > _______________________________________________ > cisco-nsp mailing list cisco-...@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
