Cisco MediaNet Netflow Configuration steps for NetProfiler visibility.

http://www.cisco.com/c/en/us/solutions/collateral/enterprise/enterprise-medianet/guide_C07-729420.html

IMPORTANT: If you are going to enable medianet, best to disable basic flow above (otherwise redundant and confusing), NetProfiler ONLY supports the Packet Loss and Jitter metrics via Netflow and Jitter metrics via IPFIX. The below 3rd-party configuration is just a sample (that may include additional fields that NetProfiler will not utilize) and we recommend that you refer to vendor specific documentation. Check the text "(Accepted by NetProfiler)" for the fields that NetProfiler supports. 

Prerequisites: 

Ensure supported IOS

So how do you know if your router supports it?
The quickest way to find out if a router meets the requirements is to check the Cisco Feature Navigator. Filter on performance monitor, then add the Performance Monitor (Phase 1) feature and click Continue.
This will allow you to choose your device to further investigate. You are given a list of IOS versions that support this feature and the memory/flash required to run it.

Does the current IOS version support Performance monitoring? 15.1.3(T) is not enough. It must be a build with support (e.g. Advanced Enterprise Services).

There are 4 things you need to check on your router:

1. Does the router meet the minimum RAM requirements for Performance monitoring or does it require an upgrade?
2. Does the router meet the minimum Flash requirements?
3. If the router is a second generation router, does it have the data license installed?

Important IOS CLI commands to help answer the above questions:

Show version - This will give you the version of IOS that is running. It will also contain the amount of RAM installed on the router.
Show flash - This will give you a listing of what is on the local flash and how much flash is installed.
Show License -This will tell you if a license is in use or not.
license boot module c1900 technology-package datak9 - In config mode, this installs the data license on routers 88x,89x,19xx,29xx,39xx series ISRs. The portion in red may be different on different routers. Requires a reboot.

Okay, so you've gone through all this and found that yes, your router does support the Medianet Performance Monitor.
So what next?
Well, with Cisco's Performance Monitor and a NetFlow Analyzer that supports it, you can now analyze voice, video, and data traffic and report on loss, latency and jitter, providing the depth of information NetFlow has been providing for other applications as well.

Network-based application discovery is Cisco's way to recognize certain common applications by inspecting the packet headers. For example, with nbar enabled, a Cisco router will identify an RTP packet/flow as opposed to thinking it is just some UDP packets.

Enable NBAR protocol discovery

interface g0/0
ip nbar protocol-discovery

Best to do either basic or medianet, shouldn't need to do both or will be redundant.

Step 1. Define the Exporter

The exporter is used by the flow monitor tag (export-to-profiler) and gives more details about the destination IP, port, source port, etc.

! Create custom record for medianet export
flow record type performance-monitormymedianetrecord

! Use match to identify which attributes denote a unique flow
match ipv4 protocol
match ipv4 source address
match ipv4 destination address
match transport source-port
match transport destination-port

! define what metrics to collect
collect routing forwarding-status
collect ipv4 dscp
collect ipv4 ttl
collect ipv4 source mask
collect ipv4 destination mask
collect transport packets expected counter
collect transport packets lost counter   >>>>>> (Accepted by NetProfiler)
collect transport packets lost rate
collect transport round-trip-time
collect transport event packet-loss counter
collect transport rtp jitter mean   >>>>>> (Accepted by NetProfiler)
collect transport rtp jitter minimum
collect transport rtp jitter maximum
collect interface input
collect interface output
collect counter bytes
collect counter packets
collect timestamp interval
collect application media bytes counter
collect application media byptes rate
collect application media packets counter
collect application media packets rate
collect application media event
collect monitor event

Step 2. Define the Flow Monitor

The monitor tells it which record type to use and where to export the results. You will still need to apply it to an interface to work.

flow monitor type performance-monitor mymedianetmonitor
description monitor performance of media
record mymedianetrecord (or use record default-rtp)
exporter netprofiler
!

Step 3. Create a Policy Map

A Policy map connects the monitor (recall this binds the record and exporter) to the class. The policy map is what is applies to an interface.
You can and should use the previously defined classes created (for QoS) to match VoIP traffic.

policy-map type performance-monitor mymedianetpolicy