S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
To reference the explicit path, follow these steps:
switchS# config t
switchS(config)# interface fc-tunnel 100
switchS(config)# explicit-path Path1
This configuration explicitly specifies Path 1 to be used for the RSPAN traffic. Refer to RFC 3209 for
further details on explicit paths and source based routing.
Monitoring RSPAN Traffic
Once the session is configured, other SPAN sources for this session can also be configured as required.
fc1/1 is used to capture traffic in both ingress and egress directions.
To use this setup, the analyzer should have the capability of distinguishing ingress and egress traffic for
all captured frames.
RSPAN can be combined with the local SPAN feature so SD ports forward local SPAN traffic along with
remote SPAN traffic. Various SPAN source and tunnel scenarios are described in this section.
Single Source with One RSPAN Tunnel
The source Switch S and the destination Switch D are interconnected through a Fibre Channel fabric.
An RSPAN tunnel is configured as a destination interface for the SPAN session and the ST port forwards
SPAN traffic through the RSPAN tunnel (see
Cisco MDS 9000 Family CLI Configuration Guide
shows an RSPAN setup where one session with destination port fc2/1 and source interface
Fibre Channel Analyzer Using a Single SD Port to Monitor RSPAN Traffic
Enters configuration mode.
References the tunnel ID for Path1.
Links Path1 to the tunnel ID.
Monitoring Network Traffic Using SPAN
OL-16184-01, Cisco MDS SAN-OS Release 3.x