Advanced Monitoring
Cisco Prime Infrastructure consumes a lot of information from various different sources, including NAM, NetFlow, NBAR, medianet, PerfMon, and Performance Agent. The following table depicts the sources of the data for the site dashlets used by Prime Infrastructure:
Table 10-1 Site Dashlet Data Sources
|
|
|
|
|
|
Application Usage Summary |
y |
y |
y |
y |
y |
Top N Application Groups |
y |
y |
y |
y |
y |
Top N Applications |
y |
y |
y |
y |
y |
Top N Applications with Most Alarms |
y |
y |
y |
y |
y |
Top N Clients (In and Out) |
y |
y |
y |
y |
y |
Top N VLANs |
y |
_ |
y |
y |
_ |
Worst N RTP Streams by Packet Loss |
y |
y |
_ |
_ |
_ |
Worst N Clients by Transaction Time |
y |
_ |
_ |
y |
_ |
The following table shows how Prime Infrastructure populates the application-specific dashlets:
Table 10-2 Application-Specific Dashlet Data Sources
|
|
|
|
|
|
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 |
_ |
Enabling NetFlow Monitoring
After NetFlow has been enabled on devices and directed to Prime Infrastructure, you can enable monitoring for NetFlow. Just as for Device and Interface Health, you just need to provision the appropriate monitoring template and deploy it.
Step 1
Choose Design > Configuration > Monitor Configuration > Features > NetFlow.
Step 2
Select one of the NetFlow templates, enter the appropriate details, and save the template. Your new template will be stored in My Templates.
Step 3
Choose Deploy > Monitoring Deployment and deploy the template you just created. After a couple of polling cycles, dashlets should start populating the data.
WAN Optimization
Cisco Wide Area Application Services (WAAS) devices and software help you to ensure high-quality WAN end-user experiences across applications at multiple sites. For various scenarios for deploying WAAS in your network, see:
http://wwwin.cisco.com/dss/adbu/waas/collateral/Using NAM in a WAAS Deployment.pdf
After you have deployed your WAAS changes at candidate sites, you can navigate to Operate > Monitoring Dashboards > Detail Dashboards > WAN Optimization to validate the return on your optimization investment. From this dashboard, you can click:
- View Multi-Segment Analysis to monitor WAAS-optimized WAN traffic.
- Conversations to see individual client/server sessions.
- Site to Site to see aggregated site traffic.
The following table describes the key WAAS monitoring dashlets:
Table 10-3 Key WAAS Monitoring Dashlets
|
|
Average Concurrent Connections (Optimized versus Pass-through) |
Graphs the average number of concurrent client and pass-through connections over a specified time period. |
Multi-segment Analysis |
Displays WAAS traffic across multiple segments in a conversation or between sites. |
Multi-segment Network Time (Client LAN-WAN - Server LAN) |
Graphs the network time between the multiple segments. |
Transaction Time (Client Experience) |
Graphs average client transaction times (in milliseconds) for the past 24 hours, with separate lines for optimized traffic and pass-through traffic (in which optimization is disabled). With optimization enabled, you should see a drop in the optimized traffic time when compared to the pass-through time. |
Traffic Volume and Compression Ratio |
Graphs the bandwidth reduction ratio between the number of bytes before compression and the number of bytes after compression. |