Configuration Guidelines - Cisco 3032 Software Configuration Manual

Configuring SPAN and RSPAN
Table 30-1
Feature
Encapsulation type (destination port)
Ingress forwarding (destination port)
VLAN filtering
RSPAN VLANs
Configuring Local SPAN
These sections contain this configuration information:
•
•
•
•
SPAN Configuration Guidelines
Follow these guidelines when configuring SPAN:
•
•
•
•
•
•
•
•
•
•
Cisco Catalyst Blade Switch 3130 and 3032 for Dell Software Configuration Guide
30-12
Default SPAN and RSPAN Configuration (continued)
SPAN Configuration Guidelines, page 30-12
Creating a Local SPAN Session, page 30-13
Creating a Local SPAN Session and Configuring Incoming Traffic, page 30-15
Specifying VLANs to Filter, page 30-16
On each switch stack, you can configure a maximum of 2 source sessions and 64 RSPAN destination
sessions. A source session is either a local SPAN session or an RSPAN source session.
For SPAN sources, you can monitor traffic for a single port or VLAN or a series or range of ports
or VLANs for each session. You cannot mix source ports and source VLANs within a single SPAN
session.
The destination port cannot be a source port; a source port cannot be a destination port.
You cannot have two SPAN sessions using the same destination port.
When you configure a switch port as a SPAN destination port, it is no longer a normal switch port;
only monitored traffic passes through the SPAN destination port.
Entering SPAN configuration commands does not remove previously configured SPAN parameters.
You must enter the no monitor session {session_number | all | local | remote} global configuration
command to delete configured SPAN parameters.
For local SPAN, outgoing packets through the SPAN destination port carry the original
encapsulation headers—untagged, ISL, or IEEE 802.1Q—if the encapsulation replicate keywords
are specified. If the keywords are not specified, the packets are sent in native form. For RSPAN
destination ports, outgoing packets are not tagged.
You can configure a disabled port to be a source or destination port, but the SPAN function does not
start until the destination port and at least one source port or source VLAN are enabled.
You can limit SPAN traffic to specific VLANs by using the filter vlan keyword. If a trunk port is
being monitored, only traffic on the VLANs specified with this keyword is monitored. By default,
all VLANs are monitored on a trunk port.
You cannot mix source VLANs and filter VLANs within a single SPAN session.
Chapter 30
Default Setting
Native form (untagged packets).
Disabled
On a trunk interface used as a source port, all VLANs are
monitored.
None configured.
Configuring SPAN and RSPAN
OL-12247-04