Configuring Span Sources - Cisco Catalyst 4500 series Administration Manual

Hide thumbs Also See for Catalyst 4500 series:
Table of Contents

Advertisement

Configuring SPAN

Configuring SPAN Sources

To configure the source for a SPAN session, perform this task:
Command
Switch(config)# [no] monitor session
{session_number} {source {interface
interface_list | {vlan vlan_IDs | cpu
[queue queue_ids] } [rx | tx | both]
This example shows how to configure SPAN session 1 to monitor bidirectional traffic from source
interface Fast Ethernet 5/1:
Switch(config)# monitor session 1 source interface fastethernet 5/1
This example shows how to configure sources with differing directions within a SPAN session:
Switch(config)# monitor session 1 source interface fa2/3 rx
Switch(config)# monitor session 1 source interface fa2/2 tx
Switch(config)#
Software Configuration Guide—Release IOS XE 3.6.0E and IOS 15.2(2)E
58-8
Chapter 58
Configuring SPAN and RSPAN
Purpose
Specifies the SPAN session number (1 through 6),
the source interfaces (FastEthernet or
GigabitEthernet), VLANs (1 through 4094),
whether traffic received or sent from the CPU is
copied to the session destination, and the traffic
direction to be monitored.
For session_number, specifies the session number
identified with this RSPAN session (1 through 6).
For interface-list, specifies the source port to
monitor. Valid interfaces include physical
interfaces and port-channel logical interfaces
(port-channel port-channel-number).
For vlan_IDs, specifies the source VLAN.
For queue_ids, specifies the queue(s) involved.
(Optional) [, | -] Specifies a series or range of
interfaces. Enter a space after the comma; enter a
space before and after the hyphen.
(Optional) Specifies the direction of traffic to
monitor. If you do not specify a traffic direction,
the source interface sends both transmitted (Tx)
and received (Rx) traffic. Only received traffic
can be monitored on additional source ports.
Rx—Monitor received traffic.
Tx—Monitor transmitted traffic.
both—Monitor both received and transmitted
traffic (bidirectional).
Queues may be identified either by number or by
name. Queue names may subsume multiple
numbered queues for convenience.
Use the no keyword to restore the defaults.
OL_28731-01

Advertisement

Table of Contents
loading

Table of Contents