The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains information about and instructions for configuring Cisco Mediatrace.
Cisco Mediatrace enables you to isolate and troubleshoot network degradation problems for data streams. Although it can be used to monitor any type of flow, it is primary used with video flows. It can also be used for non-flow related monitoring along a media flow path.
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
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:
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.
You can collect the following categories of metrics using Mediatrace:
The individual metrics under each of these categories are listed the appropriate section below.
Information can be retrieved from Mediatrace by using in either:
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:
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:
Therefore, the next section describes how to perform the following tasks in order to configure a Cisco 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:
For each node you want to monitor using Cisco Mediatrace, you must enable at least the Cisco Mediatrace Responder. You must also enable the Cisco Mediatrace Initiator for all nodes that you want to initiate Mediatrace sessions or polls.
Use the show mediatrace responder app-healthcommand to verify whether the responder is collecting events, requests, and other Cisco Mediatrace related statistics properly.
For more information about this command, see the How to Troubleshoot and Monitor a Cisco Mediatrace Session.
Cisco Mediatrace provides pre-packaged video-monitoring profiles that contain all of the parameter settings you need to start a video media monitoring session. You can also configure your own video-monitoring profiles on the Mediatrace Initiator.
To initiate a new video media monitoring session, you can associate one of these profiles with a Cisco Mediatrace session when you configure it.
Use the show mediatrace profile perf-monitor command to verify that the parameter values for your pre-packaged video-monitoring profiles are set correctly.
For more information about this command, see the How to Troubleshoot and Monitor a Cisco Mediatrace Session.
Cisco Mediatrace provides pre-packaged system-data monitoring profiles that contain all of the parameter settings you need to start a system-data monitoring session. You can also configure your own system-data monitoring profiles. To initiate a new system-data monitoring session, you can associate one of these profiles with a Cisco Mediatrace session when you configure it.
Use the show mediatrace profile systemcommandto verify that the parameter values for your pre-packaged system-data profiles are set correctly.
For more information about this command, see the How to Troubleshoot and Monitor a Cisco Mediatrace Session.
A Cisco Mediatrace session configuration requires a path-specifier profile which defines the parameters that are used to discover the network hops that will be monitored for troubleshooting. The RSVP transport protocol, specified by optional disc-proto keyword, is used to do this hop discovery. The parameter values for the flow-specifier should match the values for the media flow that will be traced.
Use the show mediatrace path-specifier command to verify that the parameter values for your path-specifier profiles are set correctly.
For more information about this command, see the How to Troubleshoot and Monitor a Cisco Mediatrace Session.
A Cisco Mediatrace session configuration requires a flow-specifier profile which defines the source IP address, destination IP address, source port, destination port, and protocol that identifies a flow. You can associate a profile with an actual Cisco Mediatrace session later when you configure it
For RTP media flows, select UDP as protocol.
Use the show mediatrace flow-specifier command to verify that the parameter values for your flow-specifier profiles are set correctly.
For more information about this command, see the How to Troubleshoot and Monitor a Cisco Mediatrace Session.
A Cisco Mediatrace session configuration requires a session-params profile, which defines the characteristics of a Cisco Mediatrace session and help it to operate smoothly. You can associate a profile with an actual Cisco Mediatrace session later when you configure it
Use the show mediatrace session-paramcommand to verify that the parameter values for your session-parameters profiles are set correctly.
For more information about this command, see the How to Troubleshoot and Monitor a Cisco Mediatrace Session.
The Cisco Mediatrace session configuration links the various profiles to a session. Only one of each type of profile can be associated with a Cisco Mediatrace session.
Use the show mediatrace sessioncommand to display the parameter settings for a specific session or all sessions.
Use the show mediatrace responder app-health command and the show mediatrace responder sessionscommand to determine the status of the nodes being monitored.
If Cisco Mediatrace is not collecting all of the data that you want, use the debug mediatracecommand.
For more information about these commands, see the How to Troubleshoot and Monitor a Cisco Mediatrace Session.
Once you have configured a Cisco Mediatrace session, you can schedule it to begin when you want to start collecting the data. If the Cisco Mediatrace session is designed to collect performance monitoring metrics, it goes out to enable the Performance Monitor when the session begins.
Use the show mediatrace sessioncommand to verify that the intended values are set for the parameters for a specific session or all sessions.
Use the show mediatrace responder app-health command and the show mediatrace responder sessionscommand to determine the status of the nodes being monitored.
If Cisco Mediatrace is not collecting all of the data that you want, use the debug mediatracecommand.
For more information about these commands, see the How to Troubleshoot and Monitor a Cisco Mediatrace Session.
You can clear incomplete mediatrace sessions on the Initiator by using the clear mediatrace incomplete-sessionscommand as described below. This coammand also cleans up all Performance Monitor settings that were configured by Cisco Mediatrace. For sessions created by the config commands, use the no mediatrace schedulecommand. The cleanup triggers a "session teardown" message to RSVP followed by a cleanup of the local mediatrace sessions database.
To check the status of your Cisco Mediatrace session, use the show mediatrace responder sessionscommand.
For more information about these commands, see the How to Troubleshoot and Monitor a Cisco Mediatrace Session.
Cisco Mediatrace polls are used to perform an on-demand fetch of data from the hops on a specific path. Some examples of how it can be used are:
If Cisco Mediatrace is not collecting all of the data that you want:
Tip |
For examples of poll output, see Configuration Examples for Cisco Mediatrace. |
The following example shows how to fetch the default system metrics when the source IP address, source port, and destination port are not known. Cisco Mediatrace uses the best local IP address as source IP address to find which hops are using RSVP.
mediatrace poll path dest ip-address system
The following example shows how to fetch the default system metrics when the source and destination port numbers are not known. RSVP finds the hop between the specified source and destination.
mediatrace poll path source ip-address dest ip-address system
The following example shows how to fetch the default system metrics when the source and destination port numbers are known. RSVP finds the hop using this information.
mediatrace poll path source-ip ip-address source - port nnnn dest-ip ip-address dest - port nnnn ip-protocol udp system
The following example shows how to fetch the default set of RTP metrics when the source and destination port numbers are not known. Cisco Mediatrace uses the path source and destination IP addresses to find the hops as well as filter the Performance Monitor data.
mediatrace poll path source ip-address dest ip-address perf-monitor
The following example shows how to fetch the default set of RTP metrics. Cisco Mediatrace uses the path parameters to discover hops and uses the inline flow specifier profile as a filter for Performance Monitor data.
mediatrace poll path source ip-address dest ip-address perf-monitor source-ip ip-address source - port nnnn dest-ip ip-address dest - port nnnn ip-protocol udp
The following example shows how to fetch the default set of TCP metrics. Cisco Mediatrace uses the path parameters to discover hops and uses the inline flow-specifier profile as a filter for Performance Monitor data.
mediatrace poll path source ip-address dest ip-address perf-monitor source-ip ip-address source - port nnnn dest-ip ip-address dest - port nnnn ip-protocol tcp
The following example shows how to fetch the default set of RTP metrics. Cisco Mediatrace uses the best local IP address as source IP address for finding hops on the path and uses the inline flow specifier profile as a filter for Performance Monitor data.
mediatrace poll path dest ip-address perf-monitor source-ip ip-address source - port nnnn dest-ip ip-address dest - port nnnn ip-protocol udp
The following example shows how to fetch the default set of TCP metrics. Cisco Mediatrace uses the best local IP address as source IP address for finding hops on the path and uses the inline flow-specifier profile as a filter for Performance Monitor data.
mediatrace poll path dest ip-address perf-monitor source-ip ip-address source - port nnnn dest-ip ip-address dest - port nnnn ip-protocol tcp
The following example shows how to fetch the default set of RTP metrics from the static policy that is already configured on the hops. The command does not configure the Performance Monitor. Cisco Mediatrace uses the path parameters to discover hops and use the inline flow specifier profile as a filter for Performance Monitor data.
mediatrace poll path source ip-address dest ip-address configless perf-monitor flow-specifier source ip-address port nnnn dest ip-address port nnnn ip-protocol udp
This example shows the output is produced by the following hops poll command:
mediatrace poll path-specifier source 10.10.130.2 destination 10.10.132.2 hops
Started the data fetch operation.
Waiting for data from hops.
This may take several seconds to complete...
Data received for hop 1
Data received for hop 2
Data fetch complete.
Results:
Data Collection Summary:
Request Timestamp: 22:47:56.788 PST Fri Oct 29 2010
Request Status: Completed
Number of hops responded (includes success/error/no-record): 2
Number of hops with valid data report: 2
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: 2
Mediatrace Hop Number: 1 (host=responder1, ttl=254)
Reachability Address: 10.10.12.3
Ingress Interface: Gi0/1
Egress Interface: Gi0/2
Mediatrace Hop Number: 2 (host=responder2, ttl=253)
Reachability Address: 10.10.34.3
Ingress Interface: Gi0/1
Egress Interface: Gi0/2
Use the show commands described in this section to troubleshoot to monitor a Cisco Mediatrace session.
Tip |
For sample outputs, see the Examples section, in this chapter. |
Note |
For a complete description of the output for the following show commands, see the Cisco Media Monitoring Command Reference. |
The following example displays video-monitoring profiles:
Router# show mediatrace profile perf-monitor
Perf-monitor Profile: vprof-4
Metric List: rtp
RTP Admin Parameter:
Max Dropout: 5
Max Reorder: 5
Min Sequential: 5
Admin Parameter:
Sampling Interval (sec): 30
The following example displays system-data profiles:
Router# show mediatrace profile system System Profile: sys-1 Metric List: intf
The following example displays flow-specifier profiles:
Router# show mediatrace flow-specifier flow-1 Flow Specifier: flow-1 Source address/port: Destination address/port: Protocol: udp
The following example displays path-specifier profiles:
Router# show mediatrace path-specifier flow-1 Path Configuration: ps1 Destination address/port: 10.10.10.1 Source address/port: 10.10.10.4 Gateway address/vlan: Discovery protocol: rsvp
The following example displays the initiator profile:
Router# show mediatrace initiator Version: Mediatrace 1.0 Mediatrace Initiator status: enabled Source IP: 1.1.1.1 Number of Maximum Allowed Active Session: 127 Number of Configured Session: 1 Number of Active Session : 0 Number of Pending Session : 0 Number of Inactive Session : 1 Note: the number of active session may be higher than max active session because the max active session count was changed recently.
The following example displays session profiles:
Router# show mediatrace session-params
Session Parameters: s-1
Response timeout (sec): 60
Frequency: On Demand
Inactivity timeout (sec): 300
History statistics:
Number of history buckets kept: 3
Route change:
Reaction time (sec): 5
The following example displays Mediatrace session statistics:
Router# show mediatrace session stats 2
Session Index: 2
Global Session Id: 86197709
Session Operation State: Active
Operation time to live: Forever
Data Collection Summary:
Request Timestamp: 23:55:04.228 PST Fri Oct 29 2010
Request Status: Completed
Number of hops responded (includes success/error/no-record): 2
Number of hops with valid data report: 2
Number of hops with error report: 0
Number of hops with no data record: 0
Detailed Report of collected data:
Last Route Change Timestamp:
Route Index: 0
Number of Mediatrace hops in the path: 2
Mediatrace Hop Number: 1 (host=responder1, ttl=254)
Metrics Collection Status: Success
Reachability Address: 10.10.12.3
Ingress Interface: Gi0/1
Egress Interface: Gi0/2
Note |
The rest of the data for hop 1 is similar to the data for hop 2, as shown below. |
Mediatrace Hop Number: 2 (host=responder2, ttl=253) Metrics Collection Status: Success Reachability Address: 10.10.34.3 Ingress Interface: Gi0/1 Egress Interface: Gi0/2 Metrics Collected: Collection timestamp: 23:55:04.237 PST Fri Oct 29 2010 Octet input at Ingress (KB): 929381.572 Octet output at Egress (MB): 1541.008502 Pkts rcvd with err at Ingress (pkts): 0 Pkts errored at Egress (pkts): 0 Pkts discarded at Ingress (pkts): 0 Pkts discarded at Egress (pkts): 0 Ingress i/f speed (mbps): 1000.000000 Egress i/f speed (mbps): 1000.000000
The following example displays Mediatrace session configuration information:
Router# show mediatrace session config 2
Global Session Id: 93642270
---------------------------
Session Details:
Path-Specifier: ps1
Session Params: sp1
Collectable Metrics Profile: intf1
Flow Specifier:
Schedule:
Operation frequency (seconds): 30 (not considered if randomly scheduled)
Next Scheduled Start Time: Start Time already passed
Group Scheduled : FALSE
Randomly Scheduled : FALSE
Life (seconds): Forever
Entry Ageout (seconds): never
Recurring (Starting Everyday): FALSE
Status of entry (SNMP RowStatus): Active
History Statistics:
Number of history Buckets kept: 10
The following example displays Mediatrace session hops:
show mediatrace session hops 2
Session Index: 2
Global Session Id: 93642270
Session Operation State: Active
Data Collection Summary:
Request Timestamp: 13:40:32.515 PST Fri Jun 18 2010
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:
Last Route Change Timestamp:
Route Index: 0
Number of Mediatrace hops in the path: 3
Mediatrace Hop Number: 1 (host=responder1, ttl=254)
Ingress Interface: Gi0/1
Egress Interface: Gi1/0
Mediatrace Hop Number: 2 (host=responder2, ttl=253)
Ingress Interface: Gi0/1
Egress Interface: Gi1/0
Mediatrace Hop Number: 3 (host=responder3, ttl=252)
Ingress Interface: Gi0/1
Egress Interface: Gi0/2
The following example displays Mediatrace session data:
Router# show mediatrace session data 2
Session Index: 2
Global Session Id: 35325453
Session Operation State: Active
Bucket index: 1
Data Collection Summary:
Request Timestamp: 13:02:47.969 PST Fri Jun 18 2010
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:
Last Route Change Timestamp:
Route Index: 0
Number of Mediatrace hops in the path: 3
Mediatrace Hop Number: 1 (host=responder1, ttl=254)
Metrics Collection Status: Success
Ingress Interface: Gi0/1
Egress Interface: Gi1/0
Metrics Collected:
Collection timestamp: 13:04:57.781 PST Fri Jun 18 2010
Octet input at Ingress (KB): 10982.720
Octet output at Egress (KB): 11189.176
Pkts rcvd with err at Ingress (pkts): 0
Pkts errored at Egress (pkts): 0
Pkts discarded at Ingress (pkts): 0
Pkts discarded at Egress (pkts): 0
Ingress i/f speed (mbps): 1000.000000
Egress i/f speed (mbps): 1000.000000
Mediatrace Hop Number: 2 (host=responder2, ttl=253)
Metrics Collection Status: Success
Ingress Interface: Gi0/1
Egress Interface: Gi1/0
Metrics Collected:
Collection timestamp: 13:04:57.792 PST Fri Jun 18 2010
Octet input at Ingress (MB): 1805.552836
Octet output at Egress (MB): 1788.468650
Pkts rcvd with err at Ingress (pkts): 0
Pkts errored at Egress (pkts): 0
Pkts discarded at Ingress (pkts): 0
Pkts discarded at Egress (pkts): 0
Ingress i/f speed (mbps): 1000.000000
Egress i/f speed (mbps): 1000.000000
The following example displays application health information for the Mediatrace responder:
Router# show mediatrace responder app-health
Mediatrace App-Health Stats:
Number of all requests received: 0
Time of the last request received:
Initiator ID of the last request received: 0
Requests dropped due to queue full: 0
Responder current max sessions: 45
Responder current active sessions: 0
Session down or tear down requests received: 0
Session timed out and removed: 0
HOPS requests received: 0
VM dynamic polling requests received: 0
VM dynamic polling failed: 0
VM configless polling requests received: 0
VM configless polling failed: 0
SYSTEM data polling requests received: 0
SYSTEM data polling requests failed: 0
APP-HEALTH polling requests received: 0
Route Change or Interface Change notices received: 0
Last time Route Change or Interface Change:
Unknown requests received: 0
The following example displays brief session information for the Mediatrace responder:
Router# show mediatrace responder sessions brief
Local Responder configured session list:
Current configured max sessions: 45
Current number of active sessions: 0
session-id initiator-name src-ip src-port dst-ip dst-port det-l
2 host-18 10.10.10.2 200 10.10.10.8 200
The topology for this example includes:
In this example, there is an RTP traffic stream from the source (address=10.10.130.2, port=1000, to the destination (address=10.10.132.2, port=2000).
The basic configuration of the Mediatrace responder is as follows:
mediatrace responder snmp-server community public RO
The basic configuration of the Mediatrace initiator is as follows:
mediatrace initiator source-ip 10.10.12.2 mediatrace profile system intf1 mediatrace profile perf-monitor rtp1 mediatrace path-specifier path1 destination ip 10.10.132.2 port 2000 source ip 10.10.130.2 port 1000 mediatrace flow-specifier flow1 source-ip 10.10.130.2 source-port 1000 dest-ip 10.10.132.2 dest-port 2000 mediatrace session-params sp1 response-timeout 10 frequency 60 inactivity-timeout 180 mediatrace 1 path-specifier path1 session-params sp1 profile perf-monitor rtp1 flow-specifier flow1 mediatrace schedule 1 life forever start-time now mediatrace 2 path-specifier path1 session-params sp1 profile system intf1 mediatrace schedule 2 life forever start-time now
For more information about configuring the products in the Medianet product family, see the other chapter in this guide or see the Cisco Media Monitoring Configuration Guide.
Related Topic |
Document Title |
---|---|
Design, configuration, and troubleshooting resources for Cisco Mediatrace and other Cisco Medianet 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. |
IP addressing commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples |
Cisco Media Montoring Command Reference |
Standard |
Title |
---|---|
No new or modified standards are supported, and support for existing standards has not been modified |
-- |
MIB |
MIBs Link |
---|---|
No new or modified MIBs are supported, and support for existing MIBs has not been modified |
-- |
RFC1 |
Title |
---|---|
RFC 2205 |
RSVP: Resource ReSerVation Protocol |
Description |
Link |
---|---|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 1 | Feature Information for Cisco Mediatrace |
Feature Name |
Releases |
Feature Information |
---|---|---|
Cisco Mediatrace 1.0 |
15.1(3)T 12.2(58)SE |
This feature enables you to isolate and troubleshoot network degradation problems for data streams. The following commands were introduced or modified by this feature: admin-params, clear mediatrace, incomplete-sessions, clock-rate (RTP parameters), dest-ip (flow), frequency (session parameters), history (session parameters), ip-protocol (flow), max-dropout, max-reorder, mediatrace, mediatrace initiator, mediatrace responder, mediatrace path-specifier, mediatrace poll, mediatrace profile perf-monitor, mediatrace profile system, mediatrace schedule, mediatrace session-params, metric-list (monitoring profile), metric-list (system profile), min-sequential, path-specifier, profile perf-monitor, profile system, response-timeout (session parameters), route-change reaction-time, sampling-interval, session-params, show mediatrace flow-specifier, show mediatrace initiator, show mediatrace path-specifier, show mediatrace profile system, show mediatrace profile perf-monitor, show mediatrace responder app-health, show mediatrace responder sessions, show mediatrace session, show mediatrace session-params, source-ip (flow), and source ip (path). |
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.