Cisco Nexus 5000 Series Switch CLI Software Configuration Guide (OL-16597-01, July 2009)

• Cannot be a destination port.
• Each source port can be configured with a direction (ingress, egress, or both) to monitor. For VLAN,
VSAN, port channel, and SAN port channel sources, the monitored direction can only be ingress and
applies to all physical ports in the group. The rx/tx option is not available for VLAN or VSAN SPAN
sessions.
• Source ports can be in the same or different VLANs or VSANs.
• For VLAN or VSAN SPAN sources, all active ports in the source VLAN or VSAN are included as
source ports.
• The switch supports a maximum of two egress SPAN source ports.
SPAN Destinations
SPAN destinations refer to the interfaces that monitors source ports. The Cisco Nexus 5000 Series switch
supports Ethernet and Fibre Channel interfaces as SPAN destinations.
Dest SPANSource SPAN
EthernetEthernet
Fibre ChannelFibre Channel
Ethernet (FCoE)Fibre Channel
Fibre ChannelVirtual Fibre Channel
Ethernet (FCoE)Virtual Fibre Channel
Characteristics of Destination Ports
Each local SPAN session must have a destination port (also called a monitoring port) that receives a copy of
traffic from the source ports, VLANs, or VSANs. A destination port has these characteristics:
• Can be any physical port, Ethernet, Ethernet (FCoE), or Fibre Channel, and virtual Fibre Channel ports
cannot be destination ports.
• Cannot be a source port.
• Cannot be a port channel or SAN port channel group.
• Does not participate in spanning tree while the SPAN session is active.
• Is excluded from the source list and is not monitored if it belongs to a source VLAN of any SPAN
session.
• Receives copies of sent and received traffic for all monitored source ports. If a destination port is
oversubscribed, it can become congested. This congestion can affect traffic forwarding on one or more
of the source ports.
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
674 OL-16597-01
Configuring SPAN
SPAN Destinations