Guidelines And Limitations For F2/F2E Series Modules - Cisco Nexus 7000 Series Configuration Manual

Configuring SPAN

Guidelines and Limitations for F2/F2e Series Modules

• For certain rate limit and packet size values on F Series modules, M2 Series modules, and Supervisor
• SPAN sampling is supported only on F Series modules.
• Traditional SPAN sessions support traffic from the F Series and M Series modules. Extended SPAN
• When the supervisor inband interface is monitored in the transmit direction on F2 Series modules, a
• Multiple SPAN destinations are not supported when an F Series module is present in a VDC. If multiple
• A FabricPath core port is not supported as a SPAN destination when an F Series module is present in a
• SPAN source functionality on satellite ports and host interface port channels is not supported when the
• When using SPAN sessions on F1 Series or F2 Series modules, ensure that the total amount of source
• VLANs containing FEX interfaces can be a SPAN source, but the ingress traffic through the F2 Series
• F2 Series modules support FEX, but they do not support FEX SPAN. Therefore, the FEX interfaces
• You can span Fabric port channels on F2 Series modules.
• Layer 3 multicast egress packets cannot be spanned on F2 Series modules.
• MTU truncation and the SPAN rate limit are supported on F Series and M2 Series modules and Supervisor
• For F2 Series modules, ingress FEX packets spanned through the Fabric port channel have 6 fewer bytes
• For F2 Series modules, egress SPAN packets of all traffic that ingresses on Layer 2 ports (including
• For F2 Series modules using SPAN destination port channels, SPAN traffic is distributed among the
2, the SPAN packet rate is less than the configured value because of the internal accounting of packet
sizes and internal headers.
sessions support traffic only from the F Series and M2 Series modules.
12-byte SHIM header is inserted after SMAC in SPAN packets.
SPAN destinations are configured in a SPAN session, the session is disabled until the F Series module
is powered down or moved to another VDC or the multiple SPAN destinations are reduced to a single
destination.
VDC. However, a FabricPath core port can be configured as a SPAN source interface.
FEX is connected to F2 or F2e Series modules.
traffic in a given session is less than or equal to the capacity of the SPAN destination interface or port
channel for that session. If the SPAN source traffic exceeds the capacity of the SPAN destination, packet
drops might occur on the SPAN source interfaces. This guideline does not apply to F2e, F3 or M3 Series
modules.
module-based FEX ports cannot be captured.
connected through the F2 Series modules cannot be made SPAN sources.
2. These features are not supported on M1 Series modules.
than the configured MTU size because the VNTag header is removed on the SPAN destination.
edge-to-edge traffic) have 16 fewer bytes than the configured MTU size because a MAC-in-MAC header
is added internally and removed at the SPAN destination.
member ports. However, the distribution pattern can be different from that of regular (non-SPAN
destination) port channels. For example, you can have even load distribution for regular port channels
but uneven load distribution (or no load balancing) for SPAN destination port channels.
Guidelines and Limitations for F2/F2e Series Modules
Cisco Nexus 7000 Series NX-OS System Management Configuration Guide
289