[c-nsp] ME3600 PW SPAN

[Spyros Kakaroukas]

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:cisco-nsp-bounces at puck.nether.net] On Behalf Of Jason Lixfeld
Sent: Friday, May 02, 2014 4:16 PM
To: <cisco-nsp at puck.nether.net>
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  cisco-nsp at puck.nether.net 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.