[c-nsp] SPAN on 6500

[Tim Stevenson]

Hi Chuck,
You're correct, if you first configure the span dest as a .1q trunk, 
the SPANned traffic will go out vlan tagged (regardless of whether 
the original traffic actually had a vlan tag or not).

You might want to check this (old but still relevant) doc on cco:
http://bock-bock.cisco.com/~tstevens/White_Papers/virtual-span/virtual-span.pdf

Hope that helps,
Tim



At 08:16 AM 1/13/2011, Church, Charles muttered:

>All,
>
>
>
>                 I'm running into some issues with SPAN session limitations
>on 6500 (SXI on a VSS pair).  After reading this doc:
>
><http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configu>http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configu
>ration/guide/span.html
>
>
>
>I'm lead to believe that if I make the destination interface a trunk, a span
>source of say VLANs 10 and 20 will leave the destination port with those
>VLAN tags intact.  This appears to match the 'encapsulation replicate' that
>is present on the 3560s.  My end goal is to use 2 3560 switches off of the
>6500s to distribute SPAN sessions to 4 separate entities.  Switch A will get
>a SPAN session off of the 6500 consisting of VLAN groups X and Y.  Switch B
>will get a SPAN session off of the 6500 consisting of VLAN groups X and Z.
>Switch A will span VLAN group X to a certain destination port, and group Y
>to another.  Switch B will do a similar thing with VLAN groups X and Z.  I'm
>assuming normal local SPAN.  I think the relies on the SPAN off of the 6500
>to keep the VLAN tags intact.  Can anyone confirm if my assumption is
>correct?
>
>
>
>Thanks,
>
>
>
>Chuck
>
>
>
>_______________________________________________
>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/




Tim Stevenson, tstevens at cisco.com
Routing & Switching CCIE #5561
Distinguished Technical Marketing Engineer, Cisco Nexus 7000
Cisco - http://www.cisco.com
IP Phone: 408-526-6759
********************************************************
The contents of this message may be *Cisco Confidential*
and are intended for the specified recipients only.