Medianet Reporting


What is Cisco Medianet?

Cisco's Medianet is an end-to-end architecture that is capable analyzing voice, video and data traffic and report on loss, latency and jitter thereby helping you optimize rich media applications.It enables you to monitor the flow of packets in your network and become aware of any issues that might impact the flow before it starts to significantly impact the performance of the application in question. Performance monitoring is especially important for video traffic because high quality interactive video traffic is highly sensitive to network issues. Even minor issues that may not affect other applications can have dramatic effects on video quality.

 

NetFlow Analyzer uses this feature of Cisco's Medianet to report on the rich media traffic. It helps you to become 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 the media traffic. These reports help you isolate network issues with regard to rich media applications and determine the quality of media traffic.

How do I Enable Cisco Medianet Performance Monitor?

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, and packet loss events and round-trip times (RTT) for data streams.

 

1. Prerequisites for Configuring Cisco Performance Monitor


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

2. Configuration Components of Cisco Performance Monitor

To configure Cisco Performance Monitor, configure many of the same basic elements that you normally configure for Flexible NetFlow:

Medianet

 

3. Configuring a Flow Exporter for Cisco Performance Monitor


Flow exporters are used to send the data that you collect with Cisco Performance Monitor to a remote system such as a NetFlow Collection Engine. Flow exporters use user datagram protocol (UDP) as the transport protocol and use the Version 9 export format.

To configure a flow exporter for the flow monitor, in order to export the data that is collected by Cisco Performance Monitor to a remote system for further analysis and storage, perform the following optional task. For Cisco Performance Monitor, flow exporters are configured the same way as they are configured for Cisco IOS Flexible NetFlow.

 

Summary Steps

  1. enable

  2. configure terminal

  3. flow exporter exporter-name

  4. description description

  5. destination {ip-address | hostname} [vrf vrf-name]

  6. export-protocol netflow-v9

  7. dscp dscp

  8. source interface-type interface-number

  9. option {exporter-stats | interface-table | sampler-table} [timeout seconds]

  10. output-features

  11. template data timeout seconds

  12. transport udp udp-port

  13. ttl seconds

  14. end

 

4. Configuring a Flow Record for Cisco Performance Monitor


The basic concepts and techniques for configuring a flow record for Cisco Performance Monitor are the same as flow records for Flexible NetFlow. The flow record specifies how the data collected data is aggregated and presented. The only significant difference is that, for Cisco Performance Monitor, the command includes type performance-monitor.

 

Summary Steps

  1. enable

  2. configure terminal

  3. flow record type performance-monitor record-name

  4. match ipv4 {destination {address | prefix [minimum-mask mask]} | protocol | source {address | prefix [minimum-mask mask]}
    1. match ipv4 source address
    2. match ipv4 destination address
    3. match transport source-port
    4. match transport destination-port
    5. collect routing forwarding-status
    6. collect ipv4 dscp
    7. collect ipv4 ttl
    8. collect ipv4 source mask
    9. collect ipv4 destination mask
    10. collect transport packets expected counter
    11. collect transport packets lost counter
    12. collect transport packets lost rate
    13. collect transport round-trip-time
    14. collect transport event packet-loss counter
    15. collect transport rtp jitter mean
    16. collect transport rtp jitter minimum
    17. collect transport rtp jitter maximum
    18. collect interface input
    19. collect interface output
    20. collect counter bytes
    21. collect counter packets
    22. collect timestamp interval
    23. collect application media bytes counter
    24. collect application media bytes rate
    25. collect application media packets counter
    26. collect application media packets rate
    27. collect application media event
    28. collect monitor event
  5. End

5. Configuring a Flow Monitor for Cisco Performance Monitor

 

The basic concepts for configuring a flow monitor for Cisco Performance Monitor are the same as flow monitors for Flexible NetFlow. Each flow monitor has a separate cache assigned to it and requires a record to define the contents and layout of its cache entries.

 

When you configure a flow monitor, you must use either:

Restrictions


To modify a flow record, you must remove it from all flow monitors it is associated with.


Summary Steps

  1. enable

  2. configure terminal

  3. flow monitor type performance-monitor monitor-name

  4. description description

  5. exporter exporter-name

  6. record {record-name | default-rtp | default-tcp}

  7. end

6. Configuring a Flow Class for Cisco Performance Monitor

 

The basic concepts and techniques for configuring a class for Cisco Performance Monitor are the same as for any other type of class. The class specifies the filter that determines which flow traffic to monitor. The filter is configured using various match commands in class-map mode.

 

If you do not already have a flow monitor configured, you can either:

Note: Nested class maps are not supported. In other words, you cannot use the class-map command while in class-map configuration mode (config-cmap).


Summary Steps

  1. enable

  2. configure terminal

  3. class-map class-name

  4. description description

  5. match {access-group {access-group |name access-group-name} | any| cos cos-value | destination-address mac address | discard-class class-number | dscp dscp-value | flow {direction | sampler} | fr-de | fr-dlci dlci-number | input-interface interface-name | ip {rtp starting-port-number port-range | precedence | dscp} | mpls experimental topmost number | not match-criterion | packet length {max maximum-length-value [min minimum-length-value] | min minimum-length-value [max maximum-length-value]} | precedence {precedence-criteria1 | precedence-criteria2 | precedence-criteria3 | precedence-criteria4} | protocol protocol-name | qos-group qos-group-value | source-address mac address-destination | vlan {vlan-id | vlan-range | vlan-combination}}

  6. rename class-name

  7. end

 

 

7. Configuring a Flow Policy for Cisco Performance Monitor Using an Existing Flow Monitor

 

The basic concepts and techniques for configuring a class for Cisco Performance Monitor are the same as for any other type of class. The class specifies which flow monitor is included. The only significant difference is that, for Cisco Performance Monitor, the policy-map command includes type performance-monitor.


If you do not already have a flow monitor configured or do not want to use any of your existing flow monitors for a new class, you can configure it using the flow monitor inline option and specifying which flow record and flow exporter are included.

Summary Steps

  1. enable

  2. configure terminal

  3. policy-map type performance-monitor policy-name

  4. class {class-name | class-default}

  5. flow monitor monitor-name

  6. monitor metric ip-cbr

  7. rate layer3 {byte-rate {bps | kbps | mbps | gbps} | packet}

  8. exit

  9. monitor metric rtp

  10. clock-rate{type-number | type-name | default} rate

  11. max-dropout number

  12. max-reorder number

  13. min-sequential number

  14. ssrc maximum number

  15. exit

  16. monitor parameters

  17. flows number

  18. interval duration number

  19. history number

  20. timeout number

  21. exit

  22. react ID {media-stop | mrv | rtp-jitter-average | transport-packets-lost-rate}

  23. action {snmp | syslog}

  24. alarm severity {alert | critical | emergency | error | info}

  25. alarm type {discrete | grouped {count number | percent number}

  26. threshold value {ge number | gt number | le number | lt number | range rng-start rng-end}

  27. description description

  28. end

8. Applying a Cisco Performance Monitor Policy to an Interface Using an Existing Flow Policy

Before it can be activated, a Cisco Performance Monitor policy must be applied to at least one interface. To activate a Cisco Performance Monitor policy, perform the following required task.


Summary Steps

  1. enable
  2. configure terminal
  3. interface type number
  4. service-policy type performance-monitor {input | output} policy-name
  5. end

Medianet Reports

The Medianet report displays traffic IN and traffic OUT details based on media volume, round trip time, packet loss and jitter. Clicking on the drop down box will help you choose the desired metrics for the report. You can also choose to group the reports based on source, destination, application or none of these. Click " Show Top" to view individual reports for media volume, round trip time, packet loss and jitter or choose "All reports" to view all the metrics as a single reports. Click on the " " icon in the table below the graph to view graphical details of the specific resource.

 

Media Volume: The time-line graph gives at-a-glance view of the top 3 contributors(IP address) of media traffic. The pie chart represents the percentage of rich media traffic to other traffic in the network. The table below the displays the source/destination/application that has sent/received maximum number of media packets and volume of media traffic in the network. It also reports the percentage of media traffic when compared to general traffic. Clicking on the respective source/destination/application will open the detail reports page that lists the traffic details of the source/destination/application selected.

 

RTT: The time-line graph gives at-a-glance view of the top 3 IP address with high round trip time(RTT). The pie chart represents the percentage of rich media traffic to other traffic in the network. The table below the displays the source/destination/application and their respective RTT. Clicking on the respective source/destination/application will open the detail reports page that lists the traffic details of the source/destination/application selected.

 

Jitter Avg: The time-line graph gives at-a-glace view of the transport jitter average of the top 3 IP address.The pie chart represents the percentage of rich media traffic to other traffic in the network. The table below the displays the source/destination/application and their maximum, minimum, and average jitter values. Clicking on the respective source/destination/application will open the detail reports page that lists the traffic details of the source/destination/application selected.

 

Packet Lost: The time-line graph gives at-a-glace view of the media packets lost by the top 3 IP address. The pie chart represents the percentage of rich media traffic to other traffic in the network. The table below the displays the source/destination/application and the number of packets lost along with the rate of packet loss. Clicking on the respective source/destination/application will open the detail reports page that lists the traffic details of the source/destination/application selected.

 

All Reports: The time-line graph gives at-a-glance view of the top 3 contributors(IP address) of media traffic. The pie chart represents the percentage of rich media traffic to other traffic in the network. The table below the displays the source/destination/application that has sent/received maximum number of media packets, the volume of media traffic, maximum, minimum, and average jitter values, number of packets lost, the rate of packet loss. Clicking on the respective source/destination/application will open the detail reports page that lists the traffic details of the source/destination/application selected.

 

Detail Report:

The Detail report provides a complete view about the resource selected. The Media Volume graph is a bar-graph that details on the volume of media traffic sent/received by a specific resource during the selected time period. It also shows the RTT and Jitter average of the resource selected in the given time period. The table below the graph lists the Source, Destination, Application, Media Packets, Media Volume, RTT, Jitter Max, Jitter Min, Jitter Average, Packet Lost, Packet Lost Rate of the resource.

Copyright © 2012, ZOHO Corp. All Rights Reserved.
ManageEngine