Local SPAN, RSPAN, and ERSPAN Configuration Guidelines and Restrictions
Local SPAN, RSPAN, and ERSPAN Configuration Guidelines and
Restrictions
These sections describe local SPAN, RSPAN, and ERSPAN configuration guidelines and restrictions:
•
•
•
•
•
•
Feature Incompatiblities
These feature incompatibilities exist with local SPAN, RSPAN, and ERSPAN:
•
•
•
•
•
SPAN destination ports can participate in IEEE 802.3Z Flow Control.
Note
Catalyst Supervisor Engine 32 PISA Cisco IOS Software Configuration Guide, Release 12.2ZY
48-6
Feature Incompatiblities, page 48-6
Local SPAN, RSPAN, and ERSPAN Session Limits, page 48-7
Local SPAN, RSPAN, and ERSPAN Guidelines and Restrictions, page 48-7
VSPAN Guidelines and Restrictions, page 48-8
RSPAN Guidelines and Restrictions, page 48-9
ERSPAN Guidelines and Restrictions, page 48-9
With a PFC3, EoMPLS ports cannot be SPAN sources. (CSCed51245)
A port-channel interface (an EtherChannel) can be a SPAN source, but you cannot configure active
member ports of an EtherChannel as SPAN source ports. Inactive member ports of an EtherChannel
can be configured as SPAN sources but they are put into the suspended state and carry no traffic.
A port-channel interface (an EtherChannel) cannot be a SPAN destination.
You cannot configure active member ports of an EtherChannel as SPAN destination ports. Inactive
member ports of an EtherChannel can be configured as SPAN destination ports but they are put into
the suspended state and carry no traffic.
Because SPAN destination ports drop ingress traffic, these features are incompatible with SPAN
destination ports:
Private VLANs
–
IEEE 802.1X port-based authentication
–
Port security
–
Spanning tree protocol (STP) and related features (PortFast, PortFast BPDU Filtering, BPDU
–
Guard, UplinkFast, BackboneFast, EtherChannel Guard, Root Guard, Loop Guard)
VLAN trunk protocol (VTP)
–
Dynamic trunking protocol (DTP)
–
IEEE 802.1Q tunneling
–
Chapter 48
Configuring Local SPAN, RSPAN, and ERSPAN
OL-11439-03