Csm Source Ports; Allowed Source Interface Types; Vsan As A Source; Guidelines To Configure Vsans As A Source - Cisco DS-X9530-SF1-K9 - Supervisor-1 Module - Control Processor Configuration Manual

SPAN Sources
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 .

CSM Source Ports

SPAN capabilities are available on the Caching Services Module (CSM).
Refer to the Cisco MDS 9000 Family SAN Volume Controller Configuration Guide for more information.

Allowed Source Interface Types

The SPAN feature is available for the following interface types:
•
•
•
•

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:
•
•
•
Cisco MDS 9000 Family Configuration Guide
43-4
Physical ports such as F ports, FL ports, TE ports, E ports, and TL ports.
Interface sup-fc0 (traffic to and from the supervisor):
The Fibre Channel traffic from the supervisor module to the switch fabric through the sup-fc0
–
interface is called ingress traffic. It is spanned when sup-fc0 is chosen as an ingress source port.
The Fibre Channel traffic from the switch fabric to the supervisor module through the sup-fc0
–
interface is called egress traffic. It is spanned when sup-fc0 is chosen as an egress source port.
PortChannels
All ports in the PortChannel are included and spanned as sources.
–
You cannot specify individual ports in a PortChannel as SPAN sources. Previously configured
–
SPAN-specific interface information is discarded.
IPS module specific Fibre Channel interfaces.
iSCSI interfaces
–
– FCIP interfaces
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.
Chapter 43 Monitoring Network Traffic Using SPAN
OL-6973-03, Cisco MDS SAN-OS Release 2.x