Белая книга для Cisco Cisco Prime Infrastructure 3.0

 

 

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. 

Page 8 of 68 

 

All information is aggregated and then exported through open export formats such as NetFlow Version 9 and 

IPFIX. Classic NetFlow (also called Traditional NetFlow) and NetFlow Version 5 are not suitable for AVC because 

they can only report Layer 3 and Layer 4 information. 

NetFlow Version 9 and IPFIX are industry standards for acquiring operational data from IP networks to allow 

network planning, monitoring traffic analysis, and IP accounting. Flexible NetFlow has the capability to customize 
the traffic analysis parameters for customer’s specific requirements. 

By utilizing the Flexible NetFlow infrastructure, users have complete control of what information needs to be 

collected and how it is aggregated, by defining what is called an FNF record. An FNF record consists of FNF keyed 

fields and nonkeyed fields. 

Keyed fields are all fields that need to be unique in order for a new FNF cache entry to be created. How keyed 

fields are chosen depends on what information is of interest to users: 

● 

Collect application usage: Keyed field is the NBAR2 application 

● 

Collect traffic between two endpoints: Keyed fields are source and destination IP addresses 

● 

Collect application usage between two endpoints: Keyed fields are source, destination IP addresses, and 

NBAR2 application 

Nonkeyed fields provide other information of interest into the FNF record. Nonkeyed fields typically are information 

such as byte count, packet count, input and output interfaces, and performance metrics such as latency or jitter. 

Metric providers are responsible to collect and calculate metrics. Some metric providers are simple and collect 

stateless metrics per packet. Some other metric providers could be more complex and require keeping states and 

collecting metrics per flow, making some transformation at export time or even doing more sophisticated 

calculation in the route processor. 

Performance collection includes traffic statistics, URL collection, application response time, and also media 

monitoring such as voice or video. 

The volume of information collected by AVC necessitates the need for a management platform to show the 

information in an easy-to-understand manner. Different types of reports are possible for different use-cases. Today, 

there are several vendors with reporting tools compatible with AVC. The recommended management platform from 

Cisco is Cisco Prime Infrastructure, which will be referenced throughout this document.