Specifications

© 2006 Cisco Systems, Inc.
All rights reserved.
Product Features 2-101
NAM / Traffic Analyzer v3.5 Tutorial
© 2006 Cisco Systems, Inc. All rights reserved.
Product Features 2-101
NAM / Traffic Analyzer v3.5 Tutorial
Enabling Traffic Monitoring
DiffServ Overview – Aggregation Groups
Enabling Traffic Monitoring
DiffServ Overview – Aggregation Groups
Aggregation Group 4
Aggregation Group 4
Aggregation Group 3
Aggregation Group 3
Aggregation Group 1
Aggregation Group 1
Aggregation Group 2
Aggregation Group 2
DSCP0
DSCP0
DSCP1
DSCP1
DSCP2
DSCP2
DSCP3
DSCP3
DSCP4
DSCP4
DSCP5
DSCP5
DSCP6
DSCP6
DSCP7
DSCP7
DSCP8
DSCP8
DSCP9
DSCP9
DSCP10
DSCP10
DSCP11
DSCP11
DSCP12
DSCP12
DSCP13
DSCP13
DSCP14
DSCP14
DSCP15
DSCP15
User
User
-
-
Defined Profile
Defined Profile
DiffServ Monitoring: Aggregation Groups
Enabling DiffServ monitoring is a simple process when you understand the steps and terms used in the
configuration process. First, just two steps are involved in enabling DiffServ:
• Creating a user-defined profile
• Enabling DiffServ monitoring for a specific data source using a defined profile
A profile consists of one or more aggregation groups. An aggregation group is one or more DSCPs that use
the same aggregation group name. It is simply a way of combining individual DSCPs into groups for
consolidated reporting. What criteria you use to combine individual DSCPs into groups is up to you, because
it affects how the NAM reports the data. To define aggregation groups and profiles, you must first identify
what traffic has been assigned to the 64 DSCPs (0–63) you want to monitor for. When you know which
DSCPs have been assigned, you can then put them into aggregation groups, if you choose. You can also
use a non-aggregation scheme that essentially creates a single aggregation group for each DSCP. This
setup allows the Traffic Analyzer to report on each DSCP individually.