22
Catalyst6000 Family Network Analysis Module Installation and Configuration Note
78-10406-05
Configuring the NAM
Using SPAN as a Traffic Source
Note You can configure SPAN as a traffic source using both the CLI and the NAM Traffic Analyzer
application.
To direct SPAN traffic to the NAM for monitoring, configure port 1 on the NAM as the SPAN destination
port. You cannot use ports on the NAM module as SPAN source ports.
The NAM can analyze Ethernet VLAN traffic from Ethernet or Fast Ethernet SPAN source ports. You
can also specify an Ethernet VLAN as the SPAN source.
The NAM can analyze Ethernet traffic from Ethernet, Fast Ethernet, Gigabit Ethernet, trunk port, or Fast
EtherChannel SPAN source ports. You can also specify an Ethernet VLAN as the SPAN source.
To use the SPAN source port as a traffic source for the NAM, set port 1 on the NAM as the SPAN
destination port. You cannot set port 2 on the NAM as a SPAN source port.
Refer to the Catalyst 6000 Family IOS Software Configuration Guide at the following website for more
information on SPAN:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/index.htm
For more information on configuring SPAN, refer to the switch software configuration guide.
To enable SPAN on the NAM, perform one of these tasks:
This example shows how to enable SPAN on the NAM:
Router#show monitor
Session 1
---------
Source Ports:
RX Only: None
TX Only: None
Both: None
Task Command
Set the source interfaces and
VLANs for the monitor session.
Router (config)# monitor session {session_number} {source
{interface type slot/port} | {vlan vlan_ID}} [, | - | rx | tx | both]
Enable port 1 of the NAM as a
SPAN destination.
Router (config)# monitor session {session_number} {destination
{interface type slot/port} [, | - ] | {vlan vlan_ID}}
Disable the monitor session. Router (config)# no monitor session session_number
Filter the SPAN session so that
only certain VLANs are seen from
switch port trunks.
Router (config)# monitor session {session_number} {filter
{vlan_ID} [, | - ]}
Show current monitor sessions. Router # show monitor session {session_number}