Guidelines And Limitations For Erspan - Cisco Nexus 7000 Series Configuration Manual

Configuring ERSPAN

Guidelines and Limitations for ERSPAN

ERSPAN has the following configuration guidelines and limitations:
• For ERSPAN session limits, see the Cisco Nexus 7000 Series NX-OS Verified Scalability Guide.
• All ERSPAN replication is performed in the hardware. The supervisor CPU is not involved.
• Control plane traffic generated by Supervisor 2 can be ERSPAN encapsulated but cannot be filtered by
• Control plane packets generated by Supervisor 1 cannot be ERSPAN encapsulated or filtered by an
• ERSPAN and ERSPAN ACLs are not supported on F1 Series modules. For the VDCs that have F1
• ERSPAN source sessions are supported on F2 Series and F2e (enhanced) Series modules. Beginning
• ERSPAN source, destination, and ACL sessions are supported on M Series modules.
• The decapsulation of generic routing encapsulation (GRE) or ERSPAN packets received on an F1 Series
• ERSPAN and ERSPAN ACL sessions are terminated identically at the destination router.
• ERSPAN is not supported for management ports.
• A destination port can be configured in only one ERSPAN session at a time.
• You cannot configure a port as both a source and destination port.
• A single ERSPAN session can include mixed sources in any combination of the following:
• Destination ports do not participate in any spanning tree instance or Layer 3 protocols.
• When an ERSPAN session contains source ports or VLAN sources that are monitored in the transmit
an ERSPAN ACL.
ERSPAN ACL.
Series modules only, you can configure ERSPAN source and destination sessions and ERSPAN ACL
source sessions but never come up.
with Cisco NX-OS Release 6.2(2), ERPSPAN destination sessions are also supported on these modules.
However, ERSPAN ACL sessions are not supported on F2 Series and F2e Series modules.
module is not supported.
◦ Ethernet ports or port channels but not subinterfaces
◦ VLANs (ingress only)
◦ The inband interface or port channels to the control plane CPU
ERSPAN does not monitor any packets that are generated by the supervisor, regardless
Note
of their source.
or transmit and receive direction, packets that these ports receive might be replicated to the ERSPAN
destination port even though the packets are not actually transmitted on the source ports. Some examples
of this behavior on source ports are as follows:
◦ Traffic that results from flooding
◦ Broadcast and multicast traffic
Cisco Nexus 7000 Series NX-OS System Management Configuration Guide
Guidelines and Limitations for ERSPAN
333