cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Medianet: Mediatrace Overview Part 1

3714
Views
5
Helpful
4
Comments
Beginner

This is a multipart blog that describes mediatrace and how it can be used to assist network managers with isolating a complex mulitimedia IP network. Part one will demonstrate mediatrace, part two will discuss mediatrace configuration options, and part three will discuss how troubleshooting with mediatrace.

The Medianet performance monitoring capability allows network administrators take a peak at video performance on a specific router to isolate poor video performance. This implies the network operator has identified the problem that is related to a specific device or network link. Although traditional IP troubleshooting tools such as traceroute and ping can help identify routing issues or network degradation, these tools do not provide enough data to network administrators to determine how voice and video performs on their networks. The Cisco medianet feature mediatrace can provide a hop-by-hop performance view of an IP flow.

In our lab, we're streaming a RTP video session of a clock to a PC as indicated by the arrows in the diagram shown below. The rotation of the seconds hand generates a video frame update on the remote PC every second.

The lab topology shown here illustrates video flow hop by hop.

Screen shot 2011-03-09 at 5.05.58 PM.png

The trace route command line utility provides the network operator a view of the network hop an IP packet traverses. Although the ping utility can show the round trip time an ICMP packet takes to traverse the network, it can also indicate network latency problems however the output does not have enough information to help isolate the specific hop of network problem. 

Traditionally, these tools are useful to determine network connectivity and routing hops, but it does not provide enough information to network operators about network performance. Traceroute and ping uses ICMP packets that may not necessarily support quality of service classification or policies.

Screen shot 2011-03-09 at 5.08.21 PM.png

For the purpose of demonstration, all routers in the lab topology is configured to support mediatrace. Since the source of the one-way video session originates from R2 LAN, a mediatrace poll session is triggered to identify performance-monitoring metrics on all the network hops the video stream traverses.

Performance-monitor is a Cisco IOS feature that measures various media flows packet performance, generates SNMP and Syslog alerts based on user-defineable quality thresholds, and can report on multiple management interfaces.  When performance monitoring is enabled on a standalone router it can measure ingress and egress media flow performance on a particular interface or service policy.  When video performance measurements for a specific flow is collected across multiple routers, the results of the output from each device can be analyzed and define how video flows perform across each network hop.

The mediatrace polling output shown below provides a detailed report of video streaming performance statistics. Network operators should be able to derive from this output the following information to help identify issues that can contribute to the IP video stream.

-           Network hop the video stream is traversing.

-           Video Stream Bit Rate

-           IP/RTP Packet Loss

-           QoS DSCP marking

-           IP Protocol Type

Mediatrace Performance Monitoring Poll

R2#mediatrace poll session 1

Started the data fetch operation.

Waiting for data from hops.

This may take several seconds to complete...

Data received for hop 0

Data received for hop 1

Data received for hop 2

Data fetch complete.

Results:

Data Collection Summary:

  Request Timestamp: 13:11:21.607 EST Wed Mar 9 2011

  Request Status: Completed

  Number of hops responded (includes success/error/no-record): 3

  Number of hops with valid data report: 3

  Number of hops with error report: 0

  Number of hops with no data record: 0

Detailed Report of collected data:

    Number of Mediatrace hops in the path: 3

    Mediatrace Hop Number: 0 (host=R2, ttl=255)

      Metrics Collection Status: Success

      Reachability Address: 10.87.80.50

      Ingress Interface: None

      Egress Interface: Tu1

      Metrics Collected:

        Flow Sampling Start Timestamp: 13:09:21

        Loss of measurement confidence: FALSE                  

        Media Stop Event Occurred: FALSE                       

        IP Packet Drop Count (pkts): 0                         

        IP Byte Count (KB): 32198.739                          

        IP Packet Count (pkts): 24821                          

        IP Byte Rate (Bps): 536645                             

        Packet Drop Reason: 0                                  

        IP DSCP: 40                                            

        IP TTL: 63                                             

        IP Protocol: 17                                        

        Media Byte Rate Average (Bps): 528371                  

        Media Byte Count (KB): 31702.319                       

        Media Packet Count (pkts): 24821                       

        RTP Interarrival Jitter Average (usec): 4303           

        RTP Packets Lost (pkts): 0                             

        RTP Packets Expected (pkts): 24811                     

        RTP Packet Lost Event Count: 0                         

        RTP Loss Percent (%): 0.00                             

    Mediatrace Hop Number: 1 (host=R3-1, ttl=254)

      Metrics Collection Status: Success

      Reachability Address: 10.87.93.45

      Ingress Interface: Tu0

      Egress Interface: Tu0

      Metrics Collected:

        Flow Sampling Start Timestamp: 13:09:21

        Loss of measurement confidence: FALSE                  

        Media Stop Event Occurred: FALSE                       

        IP Packet Drop Count (pkts): 0                         

        IP Byte Count (KB): 32198.739                          

        IP Packet Count (pkts): 24821                          

        IP Byte Rate (Bps): 536645                             

        Packet Drop Reason: 0                                  

        IP DSCP: 40                                            

        IP TTL: 62                                             

        IP Protocol: 17                                        

        Media Byte Rate Average (Bps): 528371                  

        Media Byte Count (KB): 31702.319                       

        Media Packet Count (pkts): 24821                       

        RTP Interarrival Jitter Average (usec): 4776           

        RTP Packets Lost (pkts): 0                             

        RTP Packets Expected (pkts): 24811                     

        RTP Packet Lost Event Count: 0                         

        RTP Loss Percent (%): 0.00                             

    Mediatrace Hop Number: 2 (host=R1, ttl=253)

      Metrics Collection Status: Success

      Reachability Address: 10.87.80.148

      Ingress Interface: Tu1

      Egress Interface: Gi0/1

      Metrics Collected:

        Flow Sampling Start Timestamp: 13:09:21

        Loss of measurement confidence: FALSE                  

        Media Stop Event Occurred: FALSE                       

        IP Packet Drop Count (pkts): 0                         

        IP Byte Count (KB): 32172.000                          

        IP Packet Count (pkts): 24802                          

        IP Byte Rate (Bps): 536200                             

        Packet Drop Reason: 0                                  

        IP DSCP: 40                                            

        IP TTL: 61                                             

        IP Protocol: 17                                        

        Media Byte Rate Average (Bps): 527932                  

        Media Byte Count (KB): 31675.960                       

        Media Packet Count (pkts): 24802                       

        RTP Interarrival Jitter Average (usec): 4517           

        RTP Packets Lost (pkts): 0                             

        RTP Packets Expected (pkts): 24792                     

        RTP Packet Lost Event Count: 0                         

        RTP Loss Percent (%): 0.00                             

The mediatrace allows system CPU and memory polling that can help identify over utilization problems that can contribute to poor video streaming performance. Traditionally, network administrators must rely on independent Network Management Systems to help correlate system CPU and Memory over utilization to poor video experience.

The mediatrace CPU poll results show CPU utilization for all network hops where video IP stream traverses.

Mediatrace CPU Poll

R2#mediatrace poll path-specifier source 10.87.93.154 port 5000 destination 10.87.93.164 port 4356 ip-protocol tcp system profile CPU      

Started the data fetch operation.

Waiting for data from hops.

This may take several seconds to complete...

Data received for hop 0

Data received for hop 1

Data received for hop 2

Data fetch complete.

Results:

Data Collection Summary:

  Request Timestamp: 13:59:34.938 EST Wed Mar 9 2011

  Request Status: Completed

  Number of hops responded (includes success/error/no-record): 3

  Number of hops with valid data report: 3

  Number of hops with error report: 0

  Number of hops with no data record: 0

Detailed Report of collected data:

    Number of Mediatrace hops in the path: 3

    Mediatrace Hop Number: 0 (host=R2, ttl=255)

      Metrics Collection Status: Success

      Reachability Address: 10.87.80.50

      Ingress Interface: None

      Egress Interface: Tu1

      Metrics Collected:

        Collection timestamp: 13:59:34.941 EST Wed Mar 9 2011

        One min CPU utilization (%): 30                        

        Five min CPU utilization (%): 35                       

    Mediatrace Hop Number: 1 (host=R3, ttl=254)

      Metrics Collection Status: Success

      Reachability Address: 10.87.93.45

      Ingress Interface: Tu0

      Egress Interface: Tu0

      Metrics Collected:

        Collection timestamp: 13:59:34.752 EST Wed Mar 9 2011

        One min CPU utilization (%): 6                         

        Five min CPU utilization (%): 7                        

    Mediatrace Hop Number: 2 (host=R1, ttl=253)

      Metrics Collection Status: Success

      Reachability Address: 10.87.80.148

      Ingress Interface: Tu1

      Egress Interface: Gi0/1

      Metrics Collected:

        Collection timestamp: 13:59:34.956 EST Wed Mar 9 2011

        One min CPU utilization (%): 22                        

        Five min CPU utilization (%): 27                       

The mediatrace RAM poll results show system memory utilization on all routers along the network hop where the video stream traverses.

Mediatrace Memory Poll

R2#mediatrace poll path-specifier source 10.87.93.154 port 5000 destination 10.87.93.164 port 4356 ip-protocol tcp system profile RAM

Started the data fetch operation.

Waiting for data from hops.

This may take several seconds to complete...

Data received for hop 0

Data received for hop 1

Data received for hop 2

Data fetch complete.

Results:

Data Collection Summary:

  Request Timestamp: 14:02:16.219 EST Wed Mar 9 2011

  Request Status: Completed

  Number of hops responded (includes success/error/no-record): 3

  Number of hops with valid data report: 3

  Number of hops with error report: 0

  Number of hops with no data record: 0

Detailed Report of collected data:

    Number of Mediatrace hops in the path: 3

    Mediatrace Hop Number: 0 (host=R2, ttl=255)

      Metrics Collection Status: Success

      Reachability Address: 10.87.80.50

      Ingress Interface: None

      Egress Interface: Tu1

      Metrics Collected:

        Collection timestamp: 14:02:16.223 EST Wed Mar 9 2011

        Processor memory utilization (%): 13                   

    Mediatrace Hop Number: 1 (host=R3, ttl=254)

      Metrics Collection Status: Success

      Reachability Address: 10.87.93.45

      Ingress Interface: Tu0

      Egress Interface: Tu0

      Metrics Collected:

        Collection timestamp: 14:02:16.220 EST Wed Mar 9 2011

        Processor memory utilization (%): 9                    

    Mediatrace Hop Number: 2 (host=R1, ttl=253)

      Metrics Collection Status: Success

      Reachability Address: 10.87.80.148

      Ingress Interface: Tu1

      Egress Interface: Gi0/1

      Metrics Collected:

        Collection timestamp: 14:02:16.236 EST Wed Mar 9 2011

        Processor memory utilization (%): 13  

Stay tuned for mediatrace part 2 where we will discuss mediatrace configuration options. Until then, more information regarding mediatrace implementation can be found here:

Mediatrace Configuration Guide

http://www.cisco.com/en/US/docs/ios/media_monitoring/configuration/guide/mm_mediatrace.html

Mediatrace Command Reference

http://www.cisco.com/en/US/docs/ios/media_monitoring/configuration/guide/mm_mediatrace.html

Medianet: Video Monitoring

https://supportforums.cisco.com/community/netpro/network-infrastructure/others/blog/2011/02/13/medianet--video-monitoring-1

4 Comments
Beginner

comment add

Beginner

Mr. Yu, will this feature support be intergrated into other platforms in the future?

Beginner

Hi Erik,

Mediatrace is currently supported on Cisco 89x, 29xx, and 39xx ISR platforms. This feature will eventually make its way across Cisco's enterprise portfolio this year.

Here are some of software requirements to enable this feature:

Cisco 29XX/39xx ISR - IOS 15.1(3)T or Later with UC or Data package license

Cisco 89X ISR - IOS 15.1(3)T or Later universal image with advance IP feature license

regards,

Eric

Beginner

Hi,

    I have configured mediatrace session in a router which acts as both initiator and responder , since for the path I have given I have this router only but it send me error data only .

Error says :

Mediatrace Hop Number: 0 (host=cisco2081, ttl=255)

Metrics Collection Status: Fail (16, Responder missing snmp community string error) .

I have the snmp community string but still I have the same error ?

CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards