Monitoring Traffic Using Fibre Channel Analyzers; Without Span - Cisco AP776A - Nexus Converged Network Switch 5020 Configuration Manual
Cisco mds 9000 family cli configuration guide - release 4.x (ol-18084-01, february 2009)
Hide thumbs
Also See for AP776A - Nexus Converged Network Switch 5020:
- Command reference manual (1640 pages) ,
- Configuration manual (1486 pages) ,
- Reference (886 pages)
Table of Contents
Advertisement
Monitoring Traffic Using Fibre Channel Analyzers
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
•
Note
Monitoring Traffic Using Fibre Channel Analyzers
You can use SPAN to monitor traffic on an interface without any traffic disruption. This feature is
specially useful in troubleshooting scenarios where traffic disruption changes the problem environment
and makes it difficult to reproduce the problem.
Without SPAN
You can monitor traffic using interface fc1/1 in a Cisco MDS 9000 Family switch that is connected to
another switch or host. You need to physically connect a Fibre Channel analyzer between the switch and
the storage device to analyze the traffic through interface fc1/1 as shown in
Cisco MDS 9000 Family CLI Configuration Guide
51-12
No session filters configured
Ingress (rx) sources are
fc1/3,
Egress (tx) sources are
fc1/3,
Session 1 had both source interfaces and source VSANs before the upgrade. After the upgrade, the
source VSANs were removed (rule 1).
If interface level VSAN filters are configured in source interfaces, then the source interfaces are also
removed from the session. If this interface is configured in both directions, it is removed from both
directions.
For example, before Cisco MDS SAN-OS Release 1.0(4):
Session 2 (active)
Destination is fc1/9
No session filters configured
Ingress (rx) sources are
vsans 12
fc1/6 (vsan 1-20),
Egress (tx) sources are
fc1/6 (vsan 1-20),
Once upgraded to Cisco MDS SAN-OS Release 1.1(1):
Session 2 (inactive as no active sources)
Destination is fc1/9
No session filters configured
No ingress (rx) sources
No egress (tx) sources
The deprecated configurations are removed from persistent memory once a switchover or a new
startup configuration is implemented.
Session 2 had a source VSAN 12 and a source interface fc1/6 with VSAN filters specified in Cisco
MDS SAN-OS Release 1.0(4). When upgraded to Cisco MDS SAN-OS Release 1.1(1) the following
changes are made:
The source VSAN (VSAN 12) is removed (rule 1).
–
The source interface fc1/6 had VSAN filters specified—it is also removed (rule 2).
–
Chapter 51
Monitoring Network Traffic Using SPAN
Figure
51-5.
OL-18084-01, Cisco MDS NX-OS Release 4.x
Hide quick links:
Advertisement
Table of Contents
Troubleshooting
