Specifications

© 2006 Cisco Systems, Inc.
All rights reserved.
Product Features 2-66
NAM / Traffic Analyzer v3.5 Tutorial
© 2006 Cisco Systems, Inc. All rights reserved.
Product Features 2-66
NAM / Traffic Analyzer v3.5 Tutorial
Basic NAM Configuration
Step 1: NetFlow Data Sources
Basic NAM Configuration
Step 1: NetFlow Data Sources
1. Configure NetFlow device to forward to NAM on UDP port 3000
2. Use Listening Mode to see who is sending NAM NDE traffic
3. Add NetFlow Device
a. Automatically creates NDE data source for all forwarded traffic
b. Alternatively create custom NDE data source for subset of all
forwarded NDE traffic
NetFlow
Device
A
B
C
Flow data exported
when enabling NetFlow
on interface A
NDE packets are
received by the NAM-
1/2 on a separate
internal NAM interface,
and on the NM-NAM
interface configured as
the management
interface
NDE packets are
received by the NAM-
1/2 on a separate
internal NAM interface,
and on the NM-NAM
interface configured as
the management
interface
• NetFlow Data Sources do not support all NAM monitoring features.
• Supported features – Applications, Hosts, Conversations, and DiffServ
• NetFlow Data Sources do not support all NAM monitoring features.
• Supported features – Applications, Hosts, Conversations, and DiffServ
Same for NAM-1, NAM-
2, and NM-NAM
Same for NAM-1, NAM-
2, and NM-NAM
Configuring NetFlow Data Sources
NetFlow Data Export is an alternative way to monitor local/remote WAN traffic on either type of NAM. NDE
monitoring can provide application, host, and conversation information for either the local device or remote
NetFlow enabled devices that have been configured to forward NDE packets to the NAM on UDP port 3000.
In its simplest form, NDE provides an aggregate view of traffic flow through a device at layer 3. However, with
more complex configurations, NDE records can be bundled by interface and direction. See the Command
Guide for the NetFlow device for more information on NetFlow and its configuration.
Once NDE packets are being forwarded to the NAM by a remote device, the NAM must add that device
before packets will be considered for monitoring. This step is similar to setting up a SPAN session. (The user
can also optionally create custom NDE data sources for a subset of the NDE flow from a device.) Like any
NAM data source, the NDE data sources at this point are only being accepted by the NAM, no processing of
packets takes place until monitoring is enabled for the individual data sources. This step will be covered in
detail later in this chapter, but first let’s look at the details of configuring NDE data sources on the NAM.
Note(s):
• NDE packets are received by the NAM-1/2 on a the internal NAM management interface
• NDE packets are received by the NM-NAM on the management interface. See Chapter 4 or the NM-
NAM Installation Guide for more on configuring the NM-NAM interfaces.