Cisco Medianet (Performance Monitor ) Configuration

{}



In continuation to Cisco Medianet Introduction blog, This
blog explains the configuration of Cisco routers to export Medianet related
information . In the latest IOS version,
Cisco adds Performance Monitor parameter to its NetFlow export. So, with
NetFlow traffic analysis, we gain bandwidth monitoring and performance monitor
of business critical application.

Cisco Performance Monitor:-

The performance impact on business critical application on
the network is due to the following parameters jitter, latency, packet loss, low RTT. The Cisco Performance Monitor will
help to monitor Jitter, Latency, Packet Loss and RTT for each flow packets
exported from the router.

Performance Monitoring is important for Video traffic
because the delivery of LIVE video should be with high definition and zero
delay. As mentioned in the earlier post, voice & video traffic would
quadruple by the end of 2012. So, video traffic should be given high priority
when it comes to quality and performance.

Cisco Medianet in NetFlow Analyzer :-

This feature helps you to monitor and analyze voice, video
and data traffic and report on loss, latency and jitter thereby helping you
optimize rich media applications. NetFlow Analyzer uses this feature of Cisco’s
Medianet to report on the rich media traffic. It makes you aware of the volume
and quality of media traffic in your network bandwidth. NetFlow Analyzer
reports on the volume of media traffic, round trip time, packet loss and jitter
along with the source, destination or application that is responsible for media
traffic. These reports help you isolate network issues with regard to rich
media applications and determine the quality of media traffic.

Prerequisite:-

  1. The Device
    should run Cisco IOS which supports Cisco Performance Monitor

IOS version :- 12.4(13r)T or above

Software
Version :-
15.1(3)T or above.

  1. 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 192.0.2.1 // 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 device for Cisco Medianet.
We will explain about each report generated by Cisco Medinet in our next
blog.

For 30 Day Trial, click Download now.

Thanks and Regards

Praveen Kumar

You Can Learn More About the ManageEngine Product Line By Going to manageengine.optrics.com

The original article/video can be found at Cisco Medianet (Performance Monitor ) Configuration

Leave a Reply

Your email address will not be published. Required fields are marked *