Cisco Cisco Prime Infrastructure 3.0 White Paper
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 47 of 83
The following table shows how the application-specific dashlets get populated in Cisco Prime Assurance:
Dashlet Category
Dashlet Name
NAM
Medianet
NetFlow
PA
NBAR2
Application
Application Configuration
Y
Y
Y
Y
Y
Application ART Analysis
Y
Y
App Server Performance
Y
Y
Application Traffic Analysis
Y
Y
Y
Y
Top N Clients (In and Out)
Y
Y
Worst N Clients by Transaction Time
Y
Y
Worst N Sites by Transaction Time
Y
Y
KPI Metric Comparison
Y
Y
Y
DSCP Classification
Y
Y
Number of Clients Over Time
Y
Y
Top Application Traffic Over Time
Y
Y
Top N Applications
Y
Y
Y
Top N Clients (In and Out)
Y
Y
Y
Average Packet Loss
Y
Y
Client Conversations
Y
Y
Client Traffic
Y
Y
IP Traffic Classification
Y
Y
Top N Applications
Y
Y
DSCP Classification
Y
Y
RTP Conversations Details
Y
Y
Top N RTP Streams
Y
Y
Voice Call Statistics
Y
Y
Worst N RTP Streams by Jitters
Y
Y
Worst N RTP Streams by MOS
Y
Worst N Sites by MOS
Y
Worst N Site to Site Connections by KPI
Y
Y
Y
NetFlow
Once we have verified that NetFlow is enabled on devices and directed to Cisco Prime Infrastructure, we are now
ready to turn on monitoring for NetFlow. Just as for Device and Interface Health, all it takes is provisioning the
appropriate monitoring template and deploying it. You can start out by going to Design > Monitoring
Configuration > Features > Flexible NetFlow, choosing the templates based on what was discussed in an earlier
NetFlow section, filling out the appropriate details, and saving the template. The template will be instantiated with
the new name as specified in the header under My Templates.
You can then navigate to Deploy > Monitoring Deployment. Look for the template you just created. In this case
it’s called “RTP-Branch-NetFlows”. Looking at the figure below, templates with an orange ball with a right arrow are
it’s called “RTP-Branch-NetFlows”. Looking at the figure below, templates with an orange ball with a right arrow are
already deployed, and the templates with a green ball with a right arrow are the ones that are still not deployed.
Once the template is deployed, dashlets should start populating the data after a couple of polling cycles.