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
VSAN as a Source
When a VSAN as a source is specified, then all physical ports and PortChannels in that VSAN are
included as SPAN sources. A TE port is included only when the port VSAN of the TE port matches the
source VSAN. A TE port is excluded even if the configured allowed VSAN list may have the source
VSAN, but the port VSAN is different.
You cannot configure source interfaces (physical interfaces, PortChannels, or sup-fc interfaces) and
source VSANs in the same SPAN session.
Guidelines to Configure VSANs as a Source
The following guidelines apply when configuring VSANs as a source:
Allowed list =
VSAN 2 as source
Cisco MDS 9000 Family CLI Configuration Guide
Traffic on all interfaces included in a source VSAN is spanned only in the ingress direction.
If a VSAN is specified as a source, you cannot perform interface-level SPAN configuration on the
interfaces that are included in the VSAN. Previously configured SPAN-specific interface
information is discarded.
If an interface in a VSAN is configured as a source, you cannot configure that VSAN as a source.
You must first remove the existing SPAN configurations on such interfaces before configuring
VSAN as a source.
Interfaces are only included as sources when the port VSAN matches the source VSAN.
displays a configuration using VSAN 2 as a source:
All ports in the switch are in VSAN 1 except fc1/1.
Interface fc1/1 is the TE port with port VSAN 2. VSANs 1, 2, and 3 are configured in the
VSAN 1 and VSAN 2 are configured as SPAN sources.
VSAN as a Source
For this configuration, the following apply:
VSAN 2 as a source includes only the TE port fc1/1 that has port VSAN 2.
VSAN 1 as a source does not include the TE port fc1/1 because the port VSAN does not match
"Configuring an Allowed-Active List of VSANs" section on page 15-6
Port VSAN Membership" section on page
Cisco MDS 9000 switch
Monitoring Network Traffic Using SPAN
OL-16184-01, Cisco MDS SAN-OS Release 3.x