Specifications

© 2006 Cisco Systems, Inc.
All rights reserved.
Product Features 2-27
NAM / Traffic Analyzer v3.5 Tutorial
© 2006 Cisco Systems, Inc. All rights reserved.
Product Features 2-27
NAM / Traffic Analyzer v3.5 Tutorial
Planning for NAM Deployment
Defining Data Sources and Reporting Requirements
Planning for NAM Deployment
Defining Data Sources and Reporting Requirements
RMON???
Mini-RMON???
SMON???
DSMON???
ART???
Ports???
VLANs???
Cisco EtherChannel
tunnel???
NetFlow???
Switch???
Host stats?
Voice monitoring?
QoS?
VLAN traffic stats?
Conversation
Pair stats?
Defining Data Sources and Reporting Requirements
The NAMs are capable of receiving data from a number of sources for analysis by the Traffic Analyzer
software, as such, data source selection requires careful consideration. The user must first determine what
information is desired from the analysis software, and which data must be collected to get the desired
reports. Properly determining the data to collect to meet end-users monitoring and reporting needs is
perhaps the very crux of network management. The success of your NAM implementation depends on a
clear understanding of these end-users needs and how to provide the data via the NAM. To gain a better
understanding of this issue, consider the following questions:
• What data does the NAM collect?
• Where can it collect data from, and does NAM placement affect the data collection?
• What reporting does the NAM offer?
These planning and deployment issues are covered in this chapter, and the scenarios in Chapter 3 illustrate
how to deploy, configure, and use the NAM to solve real-world problems. First, however, we discuss what
the NAM collects and where it collects it from. This discussion will help you answer the questions posed
above.