Monitoring Rspan Traffic; Sample Scenarios; Single Source With One Rspan Tunnel - Cisco AP776A - Nexus Converged Network Switch 5020 Configuration Manual

Remote SPAN
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:
Command
Step 1
switchS# config t
Step 2
switchS(config)# interface fc-tunnel 100
Step 3
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.
Figure 51-15
fc1/1 is used to capture traffic in both ingress and egress directions.
Figure 51-15
TX
RX
To use this setup, the analyzer should have the capability of distinguishing ingress and egress traffic for
all captured frames.

Sample Scenarios

RSPAN can be combined with the local SPAN feature so SD ports forward local SPAN traffic along with
Note
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
51-28
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
Source switch
Cisco MDS
9000 switch
fc1/1
ST port
Chapter 51
Purpose
Enters configuration mode.
References the tunnel ID for Path1.
Links Path1 to the tunnel ID.
Fibre Channel
TE port
fabric
Figure 51-16).
Monitoring Network Traffic Using SPAN
destination switch
Cisco MDS
9000 switch
SD port
fc2/1
FC analyzer
OL-18084-01, Cisco MDS NX-OS Release 4.x