About SPAN
SPAN analyzes all traffic between source ports by directing the SPAN session traffic to a destination port with an external analyzer attached to it.
You can define the sources and destinations to monitor in a SPAN session on the local device.
SPAN Sources
The interfaces from which traffic can be monitored are called SPAN sources. Sources designate the traffic to monitor. SPAN sources include the following:
-
Ethernet ports
-
Port-channels
A single SPAN session can include mixed sources in any combination of the above.
Characteristics of SPAN source ports:
-
A port configured as a source port cannot be configured as a destination port.
SPAN Destinations
SPAN destinations refer to the interfaces that monitor source ports. Destination ports receive the copied traffic from SPAN sources. SPAN destinations include the following:
-
Ethernet ports in either access or trunk mode
-
Port channels in either access or trunk mode
Characteristics of SPAN destination ports:
-
A port configured as a destination port cannot also be configured as a source port.
-
A destination port can be configured in only one SPAN session at a time.
-
Destination ports do not participate in any spanning tree instance. SPAN output includes bridge protocol data unit (BPDU) Spanning Tree Protocol hello packets.
SPAN Sessions
You can create SPAN sessions to designate sources and destinations to monitor.
See the Cisco Nexus 3550-T NX-OS Verified Scalability Guide for information on the number of supported SPAN sessions.
This figure shows a SPAN configuration. Packets on two ethernet ports are copied to destination port, ethernet 1/5. Only traffic in the direction specified is copied.
High Availability
The SPAN feature supports stateless and stateful restarts. After a reboot, the running configuration is applied.