Manualshelf

Specifications

ManualsBrandsCisco ManualsHome building and DecorNetwork Analysis Module 6000
251252253254255256257258259260
© 2006 Cisco Systems, Inc.
All rights reserved.
Scenarios 3-39
NAM / Traffic Analyzer v3.5 Tutorial
© 2006 Cisco Systems, Inc. All rights reserved.
Scenarios 3-39
NAM / Traffic Analyzer v3.5 Tutorial
Scenario 3
DiffServ Host Statistics (VLAN 100)
Scenario 3
DiffServ Host Statistics (VLAN 100)
Verify that traffic from these
hosts are eligible to
send/receive application
traffic using DSCP 26.
Verify that traffic from these
hosts are eligible to
send/receive application
traffic using DSCP 26.
Monitor > DiffServ > Host Stats
Verify that the listed
hosts are using expected
protocols and conversing
with expected servers.
Verify that the listed
hosts are using expected
protocols and conversing
with expected servers.
DiffServ Host Statistics
An alternate method to viewing DiffServ would be to look at all hosts transmitting for a given DSCP value. To
look at which hosts are sending packets with certain DSCP values set, Dean does the following:
Step 1. Select Monitor > DiffServ > Host Stats. The DiffServ Application Statistics screen is displayed.
Step 2. Select VLAN 100-QoSsearch from the Data Source-Profile pull-down list.
Step 3. Select the DSCP value you wish to view from the Aggregation pull-down list (DSCP-26). Notice
that this list contains all possible aggregations (DSCP values with labels in the profile), not just
the ones with traffic.
To further validate these hosts for DSCP-26, Dean clicks on the hosts to view which protocol they are using
and with which server they are communicating. Again as expected, all conversations using DSCP-26 are
with the Call Manager and use a voice related protocol.
Because Dean knows that voice-over-IP (VoIP) traffic is very sensitive to variations in network performance,
he decides to monitor the Cisco CallManagers for response times to see how well the new network and the
DiffServ implementation is supporting voice traffic. Slow response times could indicate improperly configured
QoS mechanisms or a slow server.
Note: To collect ART statistics, the Switched Port Analyzer (SPAN) source must include both directions in
order to see both the request and response packets.