SPAN Destination ports and VLAN Membership
Recently at work, a discussion sprouted up around how to handle/configure local session Switched Port Analyzer (SPAN) destination ports. A suggestion was made to create a new VLAN just for these SPAN destination ports and place them there. The justification was that they would be out of VLAN 1, and easily identifiable. Personally I thought it was a waste of a VLAN for a few simple SPAN destination ports, as SPAN destination ports do not participate in spanning tree, and do not forward traffic. However, ultimately in this case it was a good decision due to security requirements.Some key characteristics to know about SPAN destination ports:
- A destination port can be a physical port that is assigned to an EtherChannel group, even if the EtherChannel group has been specified as a SPAN source. The port is removed from the group while it is configured as a SPAN destination port.
- The port does not transmit any traffic except that traffic required for the SPAN session unless learning is enabled.
- The state of the destination port is up/down by design. The interface shows the port in this state in order to make it evident that the port Continue reading





