Default Span And Rspan Configuration; Configuring Local Span; Span Configuration Guidelines; Creating A Local Span Session - Cisco Catalyst 2975 Software Configuration Manual

Ios release 12.2(55)se
Hide thumbs Also See for Catalyst 2975:
Table of Contents

Advertisement

Chapter 27
Configuring SPAN and RSPAN

Default SPAN and RSPAN Configuration

Table 27-1
Table 27-1
Feature
SPAN state (SPAN and RSPAN)
Source port traffic to monitor
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:
OL-19720-02
shows the default SPAN and RSPAN configuration.
Default SPAN and RSPAN Configuration
SPAN Configuration Guidelines, page 27-11
Creating a Local SPAN Session, page 27-12
Creating a Local SPAN Session and Configuring Incoming Traffic, page 27-14
Specifying VLANs to Filter, page 27-16
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 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.
Default Setting
Disabled.
Both received and sent traffic (both).
Native form (untagged packets).
Disabled
On a trunk interface used as a source port, all VLANs are
monitored.
None configured.
Catalyst 2975 Switch Software Configuration Guide
Configuring SPAN and RSPAN
27-11

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents