I'd be very careful with EPC on sup2t. I can't find anything definitive but it doesn't sound 100% supported, so I'm not sure what side effects you could run into.
As far as why capture functions like EPC aren't supported in software on sup2t is mainly because it hasn't been built. Some of the EPC infrastructure was inherited from the 15.S code, but not everything is there. I wouldn't be surprised to see something like EPC or even the NX-OS style ethanalyzer show up in the future (but don't hold your breath). For now I'd suggest NetDR and MPA ( http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/15-1SY/config_guide/sup2T/15_1_sy_swcg_2T/mini_protocol_analyzer.html) for now. -Pete On Tue, Apr 22, 2014 at 10:32 AM, Phil Mayers <[email protected]>wrote: > On 22/04/2014 13:58, Pete Lumbis wrote: > >> Peter, >> >> CPU span on sup2t is unfortunately not implemented. It sounds like there >> are both software and hardware limitations to making it happen so it may >> never show up. There's an internal but I'll work on pushing external >> (meaning currently it's pretty useless but give it 24-48 hours), >> CSCsz68416. >> > > That's a real shame, but thanks for flagging it up. I guess we should all > poke our account teams. > > Is there any reason this can't be done in software? As per my other email > I note the EPC-style CLI is sort-of there and working. Since the CPU sees > the packets it must surely be able to do something with them, and CPU SPAN > was really very, very useful on sup720. To lose it would be a shame. > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
