20-11
Catalyst2950 Desktop Switch Software Configuration Guide
78-11380-05
Chapter20 Configuring SPAN and RSPAN Configuring RSPAN
You should create an RSPAN VLAN before configuring an RSPAN source or destination session.
If you enable VTP and VTP pruning, RSPAN traffic is pruned in the trunks to pre v ent th e unwant ed
flooding of RSPAN traffic across the network for VLAN-IDs that are lower than 1005.
Creating an RSPAN Session
First create an RSPAN VLAN that does not exist for the RSP AN sessio n in an y of th e switc hes tha t will
participate in RSPAN. With VTP enabled in the network, you can create the RSPAN VLAN in one
switch, and VTP propagates it to the other switches in the VTP domain for VLAN-IDs that are lower
than 1005.
Use VTP pruning to get efficient flow of RSPAN tra ffic, or manually delete the RSPAN VLAN from all
trunks that do not need to carry the RSPAN traffic.
After creating the RSPAN VLAN, begin in privileged EXEC mode, and follow these steps to start an
RSPAN source session and to specify the source (monitored) ports and the destination RSPAN VLAN.
Command Purpose
Step1 configure terminal Enter global configuration mode.
Step2 no monitor session {session_number | all |
local | remote}Clear any existing RSPAN configuration for the session.
For session_number, specify the session number identified with this
RSPAN session.
Specify all to remove all RSPAN sessions, local to remove all local
sessions, or remote to remove all remote SPAN sessions.
Step3 monitor session session_number source
interface interface-id [, | -] [both | rx | tx]Specify the RSPAN session and the source port (monitored port).
For session_number, specify the session number identified with this
RSPAN session.
For interface-id, specify the source port to monitor. Valid interfaces
include physical interfaces and port-channel logical interfaces
(port-channel port-channel-number).
(Optional) [, | -] Specify a series or range of interfaces. Enter a space
after the comma; enter a space before and aft er th e hyph en .
(Optional) Specify the direction of traffic to monitor. If you do not
specify a traffic direction, the source interface sends both sent and
received traffic.
bothMonitor both received and sent traffic.
rxMonitor received traffic.
txMonitor sent traffic.