How to enable Medianet for Cisco devices?

    The Cisco Medianet Performance Monitor provides per-flow, per-hop visibility into flow metrics such as packet loss and network jitter for audio and video streams, packet loss and round-trip times (RTT) for data streams. To configure your Cisco routers for exporting Medianet related information, follow the step below:


    The following prerequisites must be met before you can configure Cisco Performance Monitor:

    • The device should run Cisco IOS version 12.4(13r)T or above and support Cisco Performance Monitor. The software version should be 15.1(3)T or above.
    • IPv4 Traffic.
    • The networking device must be configured for IPv4 routing.
    • Cisco Express Forwarding or distributed Cisco Express Forwarding must be enabled on your router and on any interfaces on which you want to enable Cisco Performance Monitor.

    Configuring Cisco Performance Monitor:

    The configuration for Cisco Performance Monitor is quite similar to Flexible NetFlow configuration. This involves following steps:

    1. Configuring Flow Exporter
    2. Configuring Flow Record
    3. Configuring Flow Monitor
    4. Creating Class
    5. Creating Policy for performance monitor
    6. Attaching the policy to monitored interfaces

    Flow Exporter Configuration

    The flow exporter defines the destination to which NetFlow packets has to exported.
    flow exporter ManageEngine
    destination // NetFlow Analyzer listener port
    source FastEhternet0/0
    transport udp 9996 // Default listener port for NetFlow Analyzer
    version 9
    option exporter-stats timeout 60
    template data timeout 60

    Flow Record Configuration

    Here we are going to define records that corresponds to Performance and regular Flexible NetFlow fields.
    flow record ManageEngine
    match ipv4 protocol
    match ipv4 source address
    match ipv4 destination address
    match transport source-port
    match transport destination-port
    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
    collect transport packets lost rate
    collect transport round-trip-time
    collect transport event packet-loss counter
    collect transport rtp jitter mean
    collect transport rtp jitter minimum
    collect transport rtp jitter maximum
    collect interface input
    collector interface output
    collect counter bytes
    collect counter packets
    collect timestamp interval
    collect application media bytes counter
    collect application media bytes rate
    collect application media packets counter
    collect application media packets rate
    collect application media event
    collect monitor event

    Flow Monitor Configuration

    A flow monitor is the one that caches all the traffic passing through the applied interface and the flow exporter will export all the traffic as UDP datagram to NetFlow Analyzer server.

    flow monitor ManageEngine
    description Ipv4Monitor
    exporter ManageEngine
    record ManageEngine
    timeout active 60
    timeout inactive 60

    Flow Class Creation

    A Class is the one which specifies the filter that determines which flow traffic to monitor.

    Class-map ManageEngine
    match any

    Policy Creation for Performance Monitor

    Policy creation for Performance Monitor is shown below.

    Router(Config)#policy-map type performance-monitor ManageEngine
    Router(config-pmap)#class ManageEngine
    Router(config-pmap-c)#Flow monitor ManageEngine
    Router(config-pmap-C)#monitor metric rtp
    Router(config-pmap-c-mrtp) clock-rate 8 9600
    Router(config-pmap-c-mrtp) max-dropout 2
    Router(config-pmap-c-mrtp) max-reorder 4
    Router(config-pmap-c-mrtp)# min-sequential 2
    Router(config-pmap-c-mrtp)# ssrc maximum 20
    Router(config-pmap-c)# monitor parameters
    Router(config-pmap-c-mparam)# flows 40
    Router(config-pmap-c-mparam)# history 4
    Router(config-pmap-c-mparam)# timeout 20
    Router(config-pmap-c)# react 41 rtp-jitter-average

    Attaching the Policy to Interface

    The created policy is now been attached to an interface for performance monitoring:

    interface FastEhternet0/0
    service-policy type performance-monitor input ManageEngine
    You can verify the policy applied details by running following command:
    show policy-map type performance-monitor interface FastEthernet0/0

    Once the router is configured as mentioned above, you are ready to monitor devices for Cisco Medianet.