For me it's hit or miss. For example, I can't catch anything in the buffer when setting my capture point to be a physical interface on the device. This is where it would be most useful for me. Also, if I do a tcp capture of every packet on the device, the capture buffer fills up at a *much* slower rate than it should, given the total pps through the box at the time of capture.
It's not a supported feature from all the documentation that I've read and the hit-or-miss'ness of it, operationally, makes it pretty useless. They should really do a better job of nuking features from the CLI that aren't supported. This just gives us false hope :( On May 2, 2014, at 10:08 AM, Spyros Kakaroukas <[email protected]> wrote: > That shouldn't be true, unless something changed in the very latest software > release. I've successfully used EPC on me3600x boxes quite a few times in the > past. > > My thoughts and words are my own. > > Kind Regards, > > Spyros > > -----Original Message----- > From: Jason Lixfeld [mailto:[email protected]] > Sent: Friday, May 02, 2014 5:02 PM > To: Spyros Kakaroukas > Cc: <[email protected]> > Subject: Re: [c-nsp] ME3600 PW SPAN > > I agree, but like any sort of remote SPAN, EPC is also not available on this > platform, sadly and surprisingly. > > Sent from my iPhone > >> On May 2, 2014, at 9:27 AM, Spyros Kakaroukas <[email protected]> >> wrote: >> >> I've done something similar in the past without any issues. It's not really >> convenient to do at scale though. Assuming you only want small situational >> dumps for troubleshooting and not a permanent copy of your traffic , >> embedded packet capture might serve you better. >> >> My thoughts and words are my own. >> >> Kind Regards, >> >> Spyros >> >> >> -----Original Message----- >> From: cisco-nsp [mailto:[email protected]] On Behalf Of >> Jason Lixfeld >> Sent: Friday, May 02, 2014 4:16 PM >> To: <[email protected]> >> Subject: [c-nsp] ME3600 PW SPAN >> >> Seeing as how the ME3600 has no useful remote span capabilities, I just >> tried to do a ghetto pseudowire span: >> >> 1. Connect a trunk port from some STP, PVST+ and CDP spewing test switch to >> gi0/1 on local ME3600 2. Monitor source gi0/1 on local ME3600 3. Monitor >> destination gi0/2 on local ME3600 4. Loop back gi0/2 to gi0/3 on local >> ME3600 5. EoMPLS Xconnect gi0/3 on local ME3600 to gi0/4 on remote ME3600 6. >> Connect wireshark box to gi0/4 of remote me3600 >> >> At first glance, this seemed to work ok. On the wireshark box, I was able >> to see STP and PVST BPDUs on multiple VLANs and CDP frames. >> >> What else should I check to make sure this isn't some fluke? >> >> ... Or has this been a common workaround that has been known to work >> perfectly since the dawn of time and I'm just late to the party? >> >> Sent from my iPhone >> _______________________________________________ >> cisco-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ >> >> >> This e-mail and any attachment(s) contained within are confidential and are >> intended only for the use of the individual to whom they are addressed. The >> information contained in this communication may be privileged, or exempt >> from disclosure. If the reader of this message is not the intended >> recipient, you are hereby notified that any dissemination, distribution, or >> copying of this communication is strictly prohibited. If you have received >> this communication in error, please notify the sender and delete the >> communication without retaining any copies. Rolaware Hellas SA is not >> responsible for, nor endorses, any opinion, recommendation, conclusion, >> solicitation, offer or agreement or any information contained in this >> communication. > > > This e-mail and any attachment(s) contained within are confidential and are > intended only for the use of the individual to whom they are addressed. The > information contained in this communication may be privileged, or exempt from > disclosure. If the reader of this message is not the intended recipient, you > are hereby notified that any dissemination, distribution, or copying of this > communication is strictly prohibited. If you have received this communication > in error, please notify the sender and delete the communication without > retaining any copies. Rolaware Hellas SA is not responsible for, nor > endorses, any opinion, recommendation, conclusion, solicitation, offer or > agreement or any information contained in this communication. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
