Information About Configuring Cisco Mediatrace
Overview of Cisco Mediatrace
Note |
Mediatrace is no longer supported on M&T train. For performance monitoring, see Configuring Cisco Performance Monitor chapter. |
Cisco Mediatrace helps to isolate and troubleshoot network degradation problems by enabling a network administrator to discover an IP flow’s path, dynamically enable monitoring capabilities on the nodes along the path, and collect information on a hop-by-hop basis. This information includes, among other things, flow statistics, and utilization information for incoming and outgoing interfaces, CPUs, and memory, as well as any changes to IP routes or the Cisco Mediatrace monitoring state.
This information can be retrieved in either of two ways:
-
By issuing an exec command to perform an on-demand collection of statistics from the hops along a media flow. During this one-shot operation, the hops along the media flow are discovered and shown to you, along with a set of other specified information.
-
By configuring Cisco Mediatrace to start a recurring monitoring session at a specific time and on specific days. The session can be configured to specify which metrics to collect, and how frequently they are collected. The hops along the path are automatically discovered as part of the operation.
After collecting the metrics you specified, you can view a report on the metrics.
Cisco Mediatrace is part of the Cisco Medianet family of products. For more information about the design, configuration, and troubleshooting of Mediatrace when used in conjunction with other Cisco products, including a Quick Start Guide and Deployment Guide, see the Cisco Medianet Knowledge Base Portal, located at http://www.cisco.com/web/solutions/medianet/knowledgebase/index.html.
Metrics That You Can Collect Using Cisco Mediatrace
You can collect the following categories of metrics using Mediatrace:
-
Common Metrics for Each Responder
-
System Metrics: TCP Profile
-
System Metrics: RTP Profile
-
System Metrics: INTF Profile
-
System Metrics: CPU Profile
-
System Metrics: MEMORY Profile
-
App-Health Metrics: MEDIATRACE-HEALTH Profile
-
Metrics for the Mediatrace Request Summary from Initiator
The individual metrics under each of these categories are listed the appropriate section below.
Metics for Mediatrace Request Summary from Initiator
-
Request Timestamp
-
Request Status
-
Number of Hops Responded
-
Number of Hops with Valid Data
-
Number of Hops with Error
-
Number of hops with no data record
-
Last Route Change Timestamp
-
Route Index
Common Metrics for Each Responder
-
Metrics Collection Status
-
Reachability address
-
Ingress Interface
-
Egress Interface
-
Mediatrace IP TTL
-
Hostname
-
Mediatrace Hop Count
Perf-Monitor Metrics: TCP Profile
-
Flow Sampling Start Timestamp
-
Loss of measurement confidence
-
Media Stop Event Occurred
-
IP Packet Drop Count
-
IP Byte Count
-
IP Packet Count
-
IP Byte Rate
-
IP DSCP
-
IP TTL
-
IP Protocol
-
Media Byte Count
-
TCP Connect Round Trip Delay
-
TCP Lost Event Count
Perf-Monitor Metrics: RTP Profile
-
Flow Sampling Start Timestamp
-
Loss of measurement confidence
-
Media Stop Event Occurred
-
IP Packet Drop Count
-
IP Byte Count
-
IP Packet Count
-
IP Byte Rate
-
Packet Drop Reason
-
IP DSCP
-
IP TTL
-
IP Protocol
-
Media Byte Rate Average
-
Media Byte Count
-
Media Packet Count
-
RTP Interarrival Jitter Average
-
RTP Packets Lost
-
RTP Packets Expected (pkts):
-
RTP Packet Lost Event Count:
-
RTP Loss Percent
System Metrics: INTF Profile
-
Collection timestamp
-
Octet input at Ingress
-
Octet output at Egress
-
Packets received with errors at Ingress
-
Packets with errors at Egress
-
Packets discarded at Ingress
-
Packets discarded at Egress
-
Ingress interface speed
-
Egress interface speed
System Metrics: CPU Profile
-
CPU Utilization (1min)
-
CPU Utilization (5min)
-
Collection timestamp
System Metrics: MEMORY Profile
-
Processor memory utilization %
-
Collection timestamp
App-Health Metrics: MEDIATRACE-HEALTH Profile
-
Requests Received
-
Time Last Request Received
-
Initiator of Last Request
-
Requests Dropped
-
Max Concurrent Sessions supported
-
Sessions currently active
-
Sessions Teared down
-
Sessions Timed out
-
Hop Info Requests Received
-
Performance Monitor Requests Received
-
Performance Monitor Requests failed
-
Static Policy Requests Received
-
Static Policy Requests Failed
-
System Data Requests Received
-
System Data Requests Failed
-
Application Health Requests Received
-
Local route change events
-
Time of last route change event
-
Number of unknown requests received
Overview of Configuring Cisco Mediatrace
Information can be retrieved from Mediatrace by using in either:
-
A pre-scheduled, recurring monitoring session.
-
An one-shot, on-demand collection of statistics, known as a Mediatrace poll.
Before you can implement a Mediatrace session or poll, you enable Mediatrace on each network node that you want to collect flow information from. You must enable the Mediatrace Initiator on the network node that you will use to configure, initiate, and control the Mediatrace sessions or polls. On each of the network nodes that you want top collect information from, you must enable the Mediatrace Responder.
To configure a Cisco Mediatrace session, you can set session parameters by associating either of two types of pre-packaged profiles with the session:
-
video-monitoring profiles
-
system-data profiles
You can also configure your own parameters for a Cisco Mediatrace session by configuring the following types of profiles and associating them with the session:
-
Path-specifier profile
-
Flow-specifier profile
-
Sessions-parameters profile
Therefore, the next section describes how to perform the following tasks in order to configure a Cisco Mediatrace session:
-
Enable mediatrace
-
Setup a video-monitoring profile
-
Setup a system-data profile
-
Setup a path-specifier profile
-
Setup a flow-specifier profile
-
Setup a sessions-params profile
-
Associate profiles with a mediatrace session
-
Schedule a mediatrace session
The next section also describes how to execute a mediatrace poll, which is an on-demand fetch of data from the hops on a specific path.
In addition, the next section describes how to manage mediatrace sessions by performing the following tasks:
-
Clear incomplete Cisco Mediatrace sessions
-
Troubleshoot a Cisco Mediatrace session
Limitations
- Mediatrace does not support IPv6.
- Resource Reservation Protocol (RSVP) does not forward an incoming Path message on the same interface (i.e., through the interface from where it receives the path message). It displays an error some message on the console, “ingress interface = egress interface”. But the Path is sent out on the incoming interface in case of an Performance Routing (PfR) border router.