Information About SPAN
The SPAN feature is specific to switches in the Cisco MDS 9000 Family. It monitors network traffic through a Fibre Channel interface. Traffic through any Fibre Channel interface can be replicated to a special port called the SPAN destination port (SD port). Any Fibre Channel port in a switch can be configured as an SD port. Once an interface is in SD port mode, it cannot be used for normal data traffic. You can attach a Fibre Channel Analyzer to the SD port to monitor SPAN traffic.
SD ports do not receive frames, they only transmit a copy of the SPAN source traffic. The SPAN feature is nonintrusive and does not affect switching of network traffic for any SPAN source ports (see Figure 55-1).
Figure 55-1 SPAN Transmission
This section covers the following topics:
SPAN Sources
SPAN sources refer to the interfaces from which traffic can be monitored. You can also specify VSAN as a SPAN source, in which case, all supported interfaces in the specified VSAN are included as SPAN sources. When a VSAN as a source is specified, then all physical ports and PortChannels in that VSAN are included as SPAN sources. You can choose the SPAN traffic in the ingress direction, the egress direction, or both directions for any source interface:
-
Ingress source (Rx)—Traffic entering the switch fabric through this source interface is
spanned
or copied to the SD port (see Figure 55-2).
Figure 55-2 SPAN Traffic from the Ingress Direction
-
Egress source (Tx)—Traffic exiting the switch fabric through this source interface is spanned or copied to the SD port (see Figure 55-3).
Figure 55-3 SPAN Traffic from Egress Direction
IPS Source Ports
SPAN capabilities are available on the IP Storage Services (IPS) module. The SPAN feature is only implemented on the FCIP and iSCSI virtual Fibre Channel port interfaces, not the physical Gigabit Ethernet ports. You can configure SPAN for ingress traffic, egress traffic, or traffic in both directions for all eight iSCSI and 24 FCIP interfaces that are available in the IPS module.
Note You can configure SPAN for Ethernet traffic using Cisco switches or routers connected to the Cisco MDS 9000 Family IPS modules.
Allowed Source Interface Types
The SPAN feature is available for the following interface types:
-
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.
– 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
VSAN as a Source
SPAN sources refer to the interfaces from which traffic can be monitored. 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.
SPAN Sessions
Each SPAN session represents an association of one destination with a set of source(s) along with various other parameters that you specify to monitor the network traffic. One destination can be used by one or more SPAN sessions. You can configure up to 16 SPAN sessions in a switch. Each session can have several source ports and one destination port.
To activate any SPAN session, at least one source and the SD port must be up and functioning. Otherwise, traffic is not directed to the SD port.
Tip A source can be shared by two sessions, however, each session must be in a different direction—one ingress and one egress.
You can temporarily deactivate (suspend) any SPAN session. The traffic monitoring is stopped during this time.
Specifying Filters
You can perform VSAN-based filtering to selectively monitor network traffic on specified VSANs. You can apply this VSAN filter to all sources in a session (see Figure 55-14). Only VSANs present in the filter are spanned.
You can specify session VSAN filters that are applied to all sources in the specified session. These filters are bidirectional and apply to all sources configured in the session. Each SPAN session represents an association of one destination with a set of source(s) along with various other parameters that you specify to monitor the network traffic.
SD Port Characteristics
An SD port has the following characteristics:
-
Ignores BB_credits.
-
Allows data traffic only in the egress (Tx) direction.
-
Does not require a device or an analyzer to be physically connected.
-
Supports only 1 Gbps or 2 Gbps speeds. The auto speed option is not allowed.
-
Multiple sessions can share the same destination ports.
-
If the SD port is shut down, all shared sessions stop generating SPAN traffic.
-
The outgoing frames can be encapsulated in Extended Inter-Switch Link (EISL) format.
-
The SD port does not have a port VSAN.
-
SD ports cannot be configured using Storage Services Modules (SSMs).
-
The port mode cannot be changed if it is being used for a SPAN session.
Note If you need to change an SD port mode to another port mode, first remove the SD port from all sessions and then change the port mode using the switchport mode command.
SPAN Conversion Behavior
SPAN features (configured in any prior release) are converted as follows:
-
If source interfaces and source VSANs are configured in a given session, then all the source VSANs are removed from that session.
For example, before Cisco MDS SAN-OS Release 1.0(4):
No session filters configured
Once upgraded to Cisco MDS SAN-OS Release 1.1(1):
No session filters configured
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):
No session filters configured
Once upgraded to Cisco MDS SAN-OS Release 1.1(1):
Session 2 (inactive as no active sources) No session filters configured
Note 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).
Monitoring Traffic Using Fibre Channel Analyzers
You can use SPAN to monitor traffic on an interface without any traffic disruption. This feature is especially useful in troubleshooting scenarios in which traffic disruption changes the problem environment and makes it difficult to reproduce the problem. You can monitor traffic in either of the following two ways:
Monitoring 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 (see Figure 55-4).
Figure 55-4 Fibre Channel Analyzer Usage Without SPAN
This type of connection has the following limitations:
-
It requires you to physically insert the FC analyzer between the two network devices.
-
It disrupts traffic when the Fibre Channel analyzer is physically connected.
-
The analyzer captures data only on the Rx links in both port 1 and port 2. Port 1 captures traffic exiting interface fc1/1 and port 2 captures ingress traffic into interface fc1/1.
Monitoring with SPAN
Using SPAN you can capture the same traffic scenario (see Figure 55-4) without any traffic disruption. The Fibre Channel analyzer uses the ingress (Rx) link at port 1 to capture all the frames going out of the interface fc1/1. It uses the ingress link at port 2 to capture all the ingress traffic on interface fc1/1.
Using SPAN you can monitor ingress traffic on fc1/1 at SD port fc2/2 and egress traffic on SD port fc2/1. This traffic is seamlessly captured by the FC analyzer (see Figure 55-5).
Figure 55-5 Fibre Channel Analyzer Using SPAN
Single SD Port to Monitor Traffic
You do not need to use two SD ports to monitor bidirectional traffic on any interface (see Figure 55-5). You can use one SD port and one FC analyzer port by monitoring traffic on the interface at the same SD port fc2/1.
Figure 55-6 shows a SPAN setup where one session with destination port fc2/1 and source interface fc1/1 is used to capture traffic in both ingress and egress directions. This setup is more advantageous and cost effective than the setup shown in Figure 55-5. It uses one SD port and one port on the analyzer, instead of using a full, two-port analyzer.
Figure 55-6 Fibre Channel Analyzer Using a Single SD Port
To use this setup, the analyzer should have the capability of distinguishing ingress and egress traffic for all captured frames.
SD Port Configuration
The SD port in the destination switch enables the FC analyzer to receive the RSPAN traffic from the Fibre Channel tunnel. Figure 55-7 depicts an RSPAN tunnel configuration, now that tunnel destination is also configured.
Figure 55-7 RSPAN Tunnel Configuration
Note SD ports cannot be configured using Storage Services Modules (SSMs).
Mapping the FC Tunnel
The
tunnel-id-map
option specifies the egress interface of the tunnel at the destination switch (see Figure 55-8).
Figure 55-8 FC Tunnel Configuration
Creating VSAN Interfaces
Figure 55-9 depicts a basic FC tunnel configuration.
Figure 55-9 FC Tunnel Configuration
Note This example assumes that VSAN 5 is already configured in the VSAN database.
Remote SPAN
Note Remote SPAN is not supported on the Cisco Fabric Switch for HP c-Class BladeSystem and the Cisco Fabric Switch for IBM BladeSystem.
The Remote SPAN (RSPAN) feature enables you to remotely monitor traffic for one or more SPAN sources distributed in one or more source switches in a Fibre Channel fabric. The SPAN destination (SD) port is used for remote monitoring in a destination switch. A destination switch is usually different from the source switch(es) but is attached to the same Fibre Channel fabric. You can replicate and monitor traffic in any remote Cisco MDS 9000 Family switch or director, just as you would monitor traffic in a Cisco MDS source switch.
The RSPAN feature is nonintrusive and does not affect network traffic switching for those SPAN source ports. Traffic captured on the remote switch is tunneled across a Fibre Channel fabric which has trunking enabled on all switches in the path from the source switch to the destination switch. The Fibre Channel tunnel is structured using trunked ISL (TE) ports. In addition to TE ports, the RSPAN feature uses two other interface types (see Figure 55-10):
-
SD ports—A passive port from which remote SPAN traffic can be obtained by the FC analyzer.
-
ST ports—A SPAN tunnel (ST) port is an entry point port in the source switch for the RSPAN Fibre Channel tunnel. ST ports are special RSPAN ports and cannot be used for normal Fibre Channel traffic.
Figure 55-10 RSPAN Transmission
Advantages of Using RSPAN
The RSPAN features has the following advantages:
-
Enables nondisruptive traffic monitoring at a remote location.
-
Provides a cost effective solution by using one SD port to monitor remote traffic on multiple switches.
-
Works with any Fibre Channel analyzer.
-
Is compatible with the Cisco MDS 9000 Port Analyzer adapters.
-
Does not affect traffic in the source switch, but shares the ISL bandwidth with other ports in the fabric.
FC and RSPAN Tunnels
An FC tunnel is a logical data path between a source switch and a destination switch. The FC tunnel originates from the source switch and terminates at the remotely located destination switch.
RSPAN uses a special Fibre Channel tunnel (FC tunnel) that originates at the ST port in the source switch and terminates at the SD port in the destination switch. You must bind the FC tunnel to an ST port in the source switch and map the same FC tunnel to an SD port in the destination switch. Once the mapping and binding is configured, the FC tunnel is referred to as an RSPAN tunnel (see Figure 55-11).
Figure 55-11 FC and RSPAN Tunnel
ST Port Configuration
Once the FC tunnel is created, be sure to configure the ST port to bind it to the FC tunnel at the source switch. The FC tunnel becomes an RSPAN tunnel once the binding and mapping is complete.
Figure 55-12 depicts a basic FC tunnel configuration.
Figure 55-12 Binding the FC Tunnel
ST Port Characteristics
ST ports have the following characteristics:
-
ST ports perform the RSPAN encapsulation of the FC frame.
-
ST ports do not use BB_credits.
-
One ST port can only be bound to one FC tunnel.
-
ST ports cannot be used for any purpose other than to carry RSPAN traffic.
-
ST ports cannot be configured using Storage Services Modules (SSMs).
Creating Explicit Paths
You can specify an explicit path through the Cisco MDS Fibre Channel fabric (source-based routing), using the
explicit-path
option. For example, if you have multiple paths to a tunnel destination, you can use this option to specify the FC tunnel to always take one path to the destination switch. The software then uses this specified path even if other paths are available.
This option is especially useful if you prefer to direct the traffic through a certain path although other paths are available. In an RSPAN situation, you can specify the explicit path so the RSPAN traffic does not interfere with the existing user traffic. You can create any number of explicit paths in a switch (see Figure 55-13).
Figure 55-13 Explicit Path Configuration
Configuring SPAN
The SPAN feature is specific to switches in the Cisco MDS 9000 Family. It monitors network traffic through a Fibre Channel interface.
This section covers the following topics:
Configuring SD Ports for SPAN
To configure an SD port for SPAN monitoring, follow these steps:
|
|
|
Step 1
|
switch#
config t
|
Enters configuration mode.
|
Step 2
|
switch(config)#
interface fc9/1
|
Configures the specified interface.
|
Step 3
|
switch(config-if)#
switchport mode SD
|
Configures the SD port mode for interface fc9/1.
|
Step 4
|
switch(config-if)#
switchport speed 1000
|
Configures the SD port speed to 1000 Mbps.
|
Step 5
|
switch(config-if)#
no
shutdown
|
Enables traffic flow through this interface.
|
To configure a SPAN session, follow these steps:
|
|
|
Step 1
|
switch#
config t
|
Enters configuration mode.
|
Step 2
|
switch(config)#
span session 1
switch(config-span)#
|
Configures the specified SPAN session (1). If the session does not exist, it is created.
|
switch(config)#
no
span session 1
|
Deletes the specified SPAN session (1).
|
Step 3
|
switch(config-span)#
destination interface fc9/1
|
Configures the specified destination interface (fc 9/1) in a session.
|
switch(config-span)#
no
destination interface fc9/1
|
Removes the specified destination interface (fc 9/1).
|
Step 4
|
switch(config-span)#
source interface fc7/1
|
Configures the source (fc7/1) interface in both directions.
Note The Cisco MDS 9124 Fabric Switch does not support bi-directional SPAN sessions (Rx and Tx)
|
switch(config-span)#
no source interface fc7/1
|
Removes the specified destination interface (fc 7/1) from this session.
|
Step 5
|
switch(config-span)#
source interface sup-fc0
|
Configures the source interface (sup-fc0) in the session.
|
switch(config-span)#
source interface fc1/5 - 6, fc2/1 -3
|
Configures the specified interface ranges in the session.
|
switch(config-span)#
source vsan 1-2
|
Configures source VSANs 1 and 2 in the session.
|
switch(config-span)#
source interface port-channel 1
|
Configures the source PortChannel (port-channel 1).
|
switch(config-span)#
source interface fcip 51
|
Configures the source FCIP interface in the session.
|
switch(config-span)#
source interface iscsi 4/1
|
Configures the source iSCSI interface in the session.
|
switch(config-span)#
source interface svc1/1 tx traffic-type initiator
|
Configures the source SVC interface in the Tx direction for an initiator traffic type.
|
switch(config-span)#
no
source interface port-channel 1
|
Deletes the specified source interface (port-channel 1).
|
To configure a SPAN filter, follow these steps:
|
|
|
Step 1
|
switch#
config t
|
Enters configuration mode.
|
Step 2
|
switch(config)#
span session 1
switch(config-span)#
|
Configures the specified session (1).
|
Step 3
|
switch(config-span)#
source interface fc9/1 tx
|
Configures the source fc9/1 interface in the egress (Tx) direction.
|
switch(config-span)#
source filter vsan 1-2
|
Configures VSANs 1 and 2 as session filters.
|
switch(config-span)#
source interface fc7/1 rx
|
Configures the source fc7/1 interface in the ingress (Rx) direction.
|
To monitor network traffic using SD ports, follow these steps:
Step 1 Configure the SD port.
Step 2 Attach the SD port to a specific SPAN session.
Step 3 Monitor network traffic by adding source interfaces to the session.
To configure an SD port for SPAN monitoring using Device Manager, follow these steps:
Step 1 Right-click the port you want to configure and select
Configure
.
You see the general port configuration dialog.
Step 2 Under Mode, choose
SD
.
Step 3 Click
Apply
to accept the change.
Step 4 Close the dialog box.
Configuring SPAN max-queued-packets
When a SPAN destination port is oversubscribed or has more source traffic than the speed of the destination port, the source ports of the SPAN session will reduce in their throughput. The impact is proportional to the amount of source traffic flowing in. Lowering the max-queued-packets value from the default value of 15 to 1 prevents the impact on the source ports. It is necessary to reconsider the default value for this setting as it may impact the source interface throughput.
Restrictions
-
The span max-queued-packets can be changed only if no SPAN sessions are currently active on the switch.
-
If you are spanning the traffic going through an FCIP interface, SPAN copies may be dropped even if the SD interface has more bandwidth than the amount of traffic being replicated. To avoid SPAN drops, set the max-queued-packets to a higher value; for example, 100.
To configure SPAN max-queued-packets for a SPAN session, follow these steps:
|
|
|
Step 1
|
switch#
config t
|
Enters configuration mode.
|
Step 2
|
switch(config)#
span max-queued-packtes 1
switch(config-span)#
|
Configures the SPAN max-queued-packets.
|
By default, SPAN frames are dropped if the sum of the bandwidth of the source interfaces exceed the bandwidth of the destination port. With a higher value, the SPAN traffic has a higher probability of reaching the SPAN destination port instead of being dropped at the expense of data traffic throughput.
Creating SPAN Sessions
To create SPAN sessions, follow these steps:
Step 1 Choose Interface > SPAN. You see the SPAN dialog box.
Step 2 Click the Sessions tab.
Step 3 Click Create.
You see the Create SPAN Sessions dialog box.
Step 4 Choose the session ID (the ID range may vary depending on platform type and version) using the up or down arrows and click Create.
Step 5 Repeat Step 4 for each session you want to create.
Step 6 Enter the destination interface in the Dest Interface field for the appropriate session.
Step 7 Enter the filter VSAN list in the Filter VSAN List field for the appropriate session.
Step 8 Choose
active
or in
active
admin status in the Admin drop-down list.
Step 9 Click Apply to save your changes.
Step 10 Close the two dialog boxes.
Configuring SPAN for Generation 2 Fabric Switches
Cisco Generation 2 fabric switches (such as MDS 9124) support SPAN sessions in both directions, Rx and Tx.
Note While using Generation 2 fabric switches, you cannot create an additional active SPAN session when you already have one.
Restrictions
-
You can specify multiple SPAN source interfaces in Rx and Tx directions. However, the direction should be explicitly mentioned at the end of the command. The SPAN will reject any source interface configuration that fails to mention the direction.
-
You cannot mix ingress and egress interfaces in the same SPAN session. The SPAN will reject any configuration that mixes Rx ad Tx directions. However, you can specify multiple SPAN source interfaces in a single direction.
To configure for ingress SPAN sessions, follow these steps:
|
|
|
Step 1
|
switch#
config t
|
Enters configuration mode.
|
Step 2
|
switch(config)#
span session 1
switch(config-span)#
|
Configures the specified session (1).
|
Step 3
|
switch(config-span)#
destination interface fc1/1
|
Configures interface fc1/1 as the destination.
|
Step 4
|
switch(config-span)#
source interface fc1/2 rx
|
Configures the source interface fc1/2 in the ingress direction.
|
To configure for egress SPAN sessions, follow these steps:
|
|
|
Step 1
|
switch#
config t
|
Enters configuration mode.
|
Step 2
|
switch(config)#
span session 1
switch(config-span)#
|
Configures the specified session (1).
|
Step 3
|
switch(config-span)#
destination interface fc1/1
|
Configures interface fc1/1 as the destination.
|
Step 4
|
switch(config-span)#
source interface fc1/2 tx
|
Configures the source interface fc1/2 in the egress direction.
|
Examples
This example shows how to configure Cisco MDS 9124 for Multiple SPAN Interfaces
switch(config-span)# span session 1 switch(config-span)# destination interface fc1/1 switch(config-span)# source interface fc1/2 rx switch(config-span)# source interface fc1/2 tx
Generation 2 Fabric Switches support VSAN filters for one VSAN only in the egress direction; this restriction does not apply to the ingress direction. For example, if you have an interface that is a TE port, with an active VSAN of 1 to 5, and you specify a VSAN filter for VSAN 2, then only the traffic on VSAN 2 will be filtered.
switch(config-span)# span session 1 switch(config-span)# source filter vsan 2 switch(config-span)# destination interface fc1/1 switch(config-span)# source interface fc1/2 tx
However, if you specify the VSAN filter for VSANs 1 to 2, then traffic from all VSANs (1 to 5) is filtered, which makes the filter useless.
switch(config-span)# span session 1 switch(config-span)# source filter vsan 1-2 switch(config-span)# destination interface fc1/1 switch(config-span)# source interface fc1/2 tx
Editing SPAN Sources
To edit a SPAN source, follow these steps:
Step 1 Choose Interface > SPAN.
You see the SPAN dialog box.
Step 2 Click the Sources tab.
Step 3 Enter the VSAN list name in the VSAN List field.
Step 4 Click Edit Interface List.
You see the Source Interfaces dialog box.
Step 5 Click Create.
You see the Source Interfaces Interface Sources dialog box.
Step 6 Click the browse button to display the list of available FC ports.
Step 7 Choose a port and click OK.
Step 8 Click the direction (
receive
or
transmit
) you want.
Step 9 Click Create to create the FC interface source.
Step 10 Click Close in each of the three open dialog boxes.
Suspending and Reactivating SPAN Sessions
You can temporarily deactivate (suspend) any SPAN session. The traffic monitoring is stopped during this time.
To temporarily suspend or reactivate a SPAN session filter, follow these steps:
|
|
|
Step 1
|
switch#
config t
|
Enters configuration mode.
|
Step 2
|
switch(config)#
span session 1
switch(config-span)#
|
Configures the specified session (1).
|
Step 3
|
switch(config-span)#
suspend
|
Temporarily suspends the session.
|
switch(config-span)#
no suspend
|
Reactivates the session.
|
Deleting SPAN Sessions
To delete a SPAN session, follow these steps:
Step 1 Choose Interface > SPAN.
You see the SPAN dialog box.
Step 2 Click the Sessions tab.
Step 3 Click the SPAN session you want to delete.
Step 4 Click Delete.
The SPAN session is deleted.
Step 5 Close the dialog box.
Encapsulating Frames
The frame encapsulation feature is disabled by default. If you enable the encapsulation feature, all outgoing frames are encapsulated.
The
switchport encap eisl
command only applies to SD port interfaces. If encapsulation is enabled, you see a new line (
Encapsulation is eisl
) in the
show interface
SD_port_interface
command output.
To encapsulate outgoing frames (optional), follow these steps:
|
|
|
Step 1
|
switch#
config t
|
Enters configuration mode.
|
Step 2
|
switch(config)#
interface fc9/32
|
Configures the specified interface.
|
Step 3
|
switch(config-if)#
switchport mode SD
|
Configures the SD port mode for interface fc9/32.
|
Step 4
|
switch(config-if)#
switchport encap eisl
|
Enables the encapsulation option for this SD port.
|
switch(config-if)#
no
switchport encap eisl
|
Disables (default) the encapsulation option.
|
Configuring Fibre Channel Analyzers Using SPAN
To configure SPAN on the source and destination interfaces, follow these steps:
|
|
|
Step 1
|
switch#
config t
|
Enters configuration mode.
|
Step 2
|
switch(config)#
span session 1
switch(config-span)#
|
Creates the SPAN session 1.
|
Step 3
|
switch(config-span)##
destination interface fc2/1
|
Configures the destination interface fc2/1.
|
Step 4
|
switch(config-span)#
source interface fc1/1 rx
|
Configures the source interface fc1/1 in the ingress direction.
|
Step 5
|
switch(config)#
span session 2
switch(config-span)#
|
Creates the SPAN session 2.
|
Step 6
|
switch(config-span)##
destination interface fc2/2
|
Configures the destination interface fc2/2.
|
Step 7
|
switch(config-span)#
source interface fc1/1 tx
|
Configures the source interface fc1/1 in the egress direction.
|
To configure Fibre Channel Analyzers using SPAN for the example in Figure 55-5, follow these steps:
Step 1 Configure SPAN on interface fc1/1 in the ingress (Rx) direction to send traffic on SD port fc2/1 using session 1.
Step 2 Configure SPAN on interface fc1/1in the egress (Tx) direction to send traffic on SD port fc2/2 using session 2.
Step 3 Physically connect fc2/1 to port 1 on the Fibre Channel analyzer.
Step 4 Physically connect fc2/2 to port 2 on the Fibre Channel analyzer.
Configuring Single SD Port to Monitor Traffic
To configure SPAN on a single SD port, follow these steps:
|
|
|
Step 1
|
switch#
config t
|
Enters configuration mode.
|
Step 2
|
switch(config)#
span session 1
switch(config-span)#
|
Creates the SPAN session 1.
|
Step 3
|
switch(config-span)##
destination interface fc2/1
|
Configures the destination interface fc2/1.
|
Step 4
|
switch(config-span)#
source interface fc1/1
|
Configures the source interface fc1/1 on the same SD port.
|
Configuring RSPAN
The RSPAN tunnel begins in the source switch and terminates in the destination switch. This section assumes Switch S to be the source and Switch D to be the destination.
Prerequisites
-
In addition to the source and destination switches, the VSAN must also be configured in each Cisco MDS switch in the Fibre Channel fabric, if they exist.
To monitor network traffic using the RSPAN feature, follow these steps:
Step 1 Create VSAN interfaces in destination switch (Switch D) and source switch (Switch S) to facilitate the Fibre Channel tunnel (FC tunnel) creation.
Step 2 Enable the FC tunnel in each switch in the end-to-end path of the tunnel.
Step 3 Initiate the FC tunnel (in Switch S) and map the tunnel to the VSAN interface’s IP address (in Switch D) so all RSPAN traffic from the tunnel is directed to the SD port.
Step 4 Configure SD ports for SPAN monitoring in the destination switch (Switch D).
Step 5 Configure the ST port in the source switch (Switch S) and bind the ST port to the FC tunnel.
Step 6 Create an RSPAN session in the source switch (in Switch S) to monitor network traffic.
Verifying SPAN Configuration
To display the SPAN configuration information, perform one of the following tasks:
|
|
show span
|
Displays SPAN Sessions in a Brief Format
|
show span session 7
|
Displays a Specific SPAN Session in Detail
|
show span session
|
Displays ALL SPAN Sessions
|
show span drop-counters
|
Displays SPAN drop-counters for the SPAN Sessions
|
show span max-queued-packets
|
Displays SPAN max-queued-packets for the SPAN Sessions
|
show int fc9/32
|
Displays an SD Port Interface with Encapsulation Enabled
|
show interface brief
|
Displays ST Port Interface Information
|
show interface fc1/11
|
Displays Detailed Information for the ST Port Interface
|
show fc-tunnel
|
Displays the FC Tunnel Status
|
show fc-tunnel tunnel-id-map
|
Displays FC Tunnel Egress Mapping Information
|
show fc-tunnel explicit-path
|
Displays FC Tunnel Explicit Mapping Information
|
show interface fc-tunnel 200
|
Displays the FC Tunnel Interface
|
For detailed information about the fields in the output from these commands, refer to the
Cisco MDS 9000 Family Command Reference
.
This section includes the following topics:
Displaying SPAN Information
Use the
show span
command to display configured SPAN information. See Examples
55-1
to
55-6
.
Example 55-1 Displays SPAN Sessions in a Brief Format
switch# show span session brief -------------------------------------------------------- Session Admin Oper Destination -------------------------------------------------------- 7 no suspend active fc2/7 1 suspend inactive not configured 2 no suspend inactive fc3/1
Example 55-2 Displays a Specific SPAN Session in Detail
switch# show span session 7 No session filters configured
Example 55-3 Displays ALL SPAN Sessions
switch# show span session Session 1 (inactive as no destination) Destination is not specified Session filter vsans are 1 No session filters configured Session 3 (admin suspended) Destination is not configured Session filter vsans are 1-20 fc3/2, fc3/3, fc3/4, fcip 51, fc3/2, fc3/3, fc3/4, sup-fc0,
Example 55-4 Displays SPAN drop-counters for the SPAN Sessions
switch# show span drop-counters SPAN Drop-Counters for module 3 is: 0x0 SPAN Drop-Counters for module 7 is: 0x0
Note The show span drop-counters command displays the dropped counters. You can configure the show span max-queued-packets command only if the dropped counter value is greater than zero.
Example 55-5 Displays SPAN max-queued-packets for the SPAN Sessions
switch# show span max-queued-packets Drop-Threshold for SPAN sessions: 15
Note The default value for all the SPAN sessions is 15. The span max-queued-packets command can be issued only if the sessions are inactive.
Example 55-6 Displays an SD Port Interface with Encapsulation Enabled
Hardware is Fibre Channel Port WWN is 22:20:00:05:30:00:49:5e Receive Buffer Size is 2112 Encapsulation is eisl <---------------- Displays the enabled encapsulation status 5 minutes input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec 5 minutes output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec 0 frames input, 0 bytes, 0 discards 0 frames output, 0 bytes, 0 discards 0 input OLS, 0 LRR, 0 NOS, 0 loop inits
0 output OLS, 0 LRR, 0 NOS, 0 loop inits
Displaying RSPAN Information
Use the
show
commands to display configured RSPAN information. See Examples
55-7
to
55-13
.
Example 55-7 Displays ST Port Interface Information
switch# show interface brief ------------------------------------------------------------------------------- Interface Vsan Admin Admin Status Oper Oper Port-channel ------------------------------------------------------------------------------- fc1/1 1 auto on trunking TE 2 -- fc1/14 1 auto on trunking TE 2 -- fc1/15 1 ST on up ST 2 -- fc2/9 1 auto on trunking TE 2 port-channel 21 fc2/10 1 auto on trunking TE 2 port-channel 21 fc2/13 999 auto on up F 1 -- fc2/14 999 auto on up FL 1 -- fc2/15 1 SD -- up SD 2 -- fc2/16 1 auto on trunking TE 2 -- -------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------- Interface Status IP Address Speed MTU -------------------------------------------------------------------------------------- mgmt0 up 172.22.36.175/22 100 Mbps 1500 -------------------------------------------------------------------------------------- Interface Status IP Address Speed MTU-- -------------------------------------------------------------------------------------- vsan5 up 10.10.10.1/24 1 Gbps 1500 -------------------------------------------------------------------------------------- Interface Vsan Admin Status Oper Oper -------------------------------------------------------------------------------------- port-channel 21 1 on trunking TE 4 -------------------------------------------------------------------------------------- Interface Status Dest IP Addr Src IP Addr TID Explicit Path -------------------------------------------------------------------------------------- fc-tunnel 100 up 10.10.10.2 10.10.10.1 100
Example 55-8 Displays Detailed Information for the ST Port Interface
switch# show interface fc1/11 Hardware is Fibre Channel Port WWN is 20:0b:00:05:30:00:59:de Rspan tunnel is fc-tunnel 100 5 minutes input rate 248 bits/sec, 31 bytes/sec, 0 frames/sec 5 minutes output rate 176 bits/sec, 22 bytes/sec, 0 frames/sec 6862 frames input, 444232 bytes 6862 frames output, 307072 bytes 0 input OLS, 0 LRR, 0 NOS, 0 loop inits 0 output OLS, 0 LRR, 0 NOS, 0 loop inits
Example 55-9 Displays the FC Tunnel Status
Example 55-10 Displays FC Tunnel Egress Mapping Information
switch# show fc-tunnel tunnel-id-map tunnel id egress interface
Note Multiple tunnel IDs can terminate at the same interface.
Example 55-11 Displays FC Tunnel Explicit Mapping Information
switch# show fc-tunnel explicit-path Explicit path name: Alternate1 Explicit path name: User2
Example 55-12 Displays SPAN Mapping Information
switch# show span session Destination is fc-tunnel 100 No session filters configured
Example 55-13 Displays the FC Tunnel Interface
switch# show interface fc-tunnel 200 Dest IP Addr: 200.200.200.7 Tunnel ID: 200 Source IP Addr: 200.200.200.4 LSP ID: 1