Information About Span And Rspan - Cisco Catalyst 2960 series Configuration Manual

• SPAN sessions do not interfere with the normal operation of the switch. However, an oversubscribed
• When SPAN or RSPAN is enabled, each packet being monitored is sent twice, once as normal traffic
• You can configure SPAN sessions on disabled ports; however, a SPAN session does not become active
• The switch does not support a combination of local SPAN and RSPAN in a single session.
RSPAN
The restrictions for RSPAN are as follows:
• RSPAN does not support BPDU packet monitoring or other Layer 2 switch protocols.
• The RSPAN VLAN is configured only on trunk ports and not on access ports. To avoid unwanted traffic
• RSPAN VLANs are included as sources for port-based RSPAN sessions when source trunk ports have
• If you enable VTP and VTP pruning, RSPAN traffic is pruned in the trunks to prevent the unwanted
• To use RSPAN, the switch must be running the LAN Base image.

Information About SPAN and RSPAN

SPAN and RSPAN
You can analyze network traffic passing through ports or VLANs by using SPAN or RSPAN to send a copy
of the traffic to another port on the switch or on another switch that has been connected to a network analyzer
or other monitoring or security device. SPAN copies (or mirrors) traffic received or sent (or both) on source
ports or source VLANs to a destination port for analysis. SPAN does not affect the switching of network
traffic on the source ports or VLANs. You must dedicate the destination port for SPAN use. Except for traffic
that is required for the SPAN or RSPAN session, destination ports do not receive or forward traffic.
Only traffic that enters or leaves source ports or traffic that enters or leaves source VLANs can be monitored
by using SPAN; traffic routed to a source VLAN cannot be monitored. For example, if incoming traffic is
SPAN destination, for example, a 10-Mb/s port monitoring a 100-Mb/s port, can result in dropped or
lost packets.
and once as a monitored packet. Monitoring a large number of ports or VLANs could potentially generate
large amounts of network traffic.
unless you enable the destination port and at least one source port or VLAN for that session.
◦ An RSPAN source session cannot have a local destination port.
◦ An RSPAN destination session cannot have a local source port.
◦ An RSPAN destination session and an RSPAN source session that are using the same RSPAN
VLAN cannot run on the same switch or switch stack.
in RSPAN VLANs, make sure that the VLAN remote-span feature is supported in all the participating
switches.
active RSPAN VLANs. RSPAN VLANs can also be sources in SPAN sessions. However, since the
switch does not monitor spanned traffic, it does not support egress spanning of packets on any RSPAN
VLAN identified as the destination of an RSPAN source session on the switch.
flooding of RSPAN traffic across the network for VLAN IDs that are lower than 1005.
Consolidated Platform Configuration Guide, Cisco IOS Release 15.2(4)E (Catalyst 2960-X Switches)
Information About SPAN and RSPAN
473