Skip to main content

'How to Enable Medianet for Cisco Devices'

This document provides a step-by-step guide to enable Medianet Performance Monitor on Cisco devices, allowing for visibility into various flow metrics, essential for optimizing audio and video streams.

Prerequisites

Ensure the following prerequisites are met before configuring 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 similar to Flexible MOTADATA_NETFLOW configuration and involves the 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

Define the destination to which MOTADATA_NETFLOW packets are to be exported:

flow exporter ObserveOps
destination {MOTADATA_NETFLOW_SERVER_IP} // AIOps Flow Explorer listener port
source FastEhternet0/0
transport udp 2055 // Default listener port for AIOps Flow Explorer
version 9
option exporter-stats timeout 60
template data timeout 60

Flow Record Configuration

Define records that correspond to Performance and regular Flexible MOTADATA_NETFLOW fields:

flow record ObserveOps
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
collect 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

The flow monitor caches all the traffic passing through the applied interface:

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

Flow Class Creation

Specify the filter that determines which flow traffic to monitor:

class-map ObserveOps 
match any

Policy Creation for Performance Monitor

Create the policy for Performance Monitor:

Router(Config)#policy-map type performance-monitor ObserveOps 
Router(config-pmap)#class ObserveOps
Router(config-pmap-c)#flow monitor ObserveOps
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

Attach the created policy to an interface for performance monitoring:

interface FastEhternet0/0
service-policy type performance-monitor input ObserveOps

Verify the policy applied details by running the following command:

show policy-map type performance-monitor interface FastEthernet0/0

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