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.
To configure adminitrator parameters for a Mediatrace performance monitoring profile, use the admin-params command in monitoring profile configuration mode. To return to the default setting, use the no form of this command.
admin-params
no admin-params
This command has no arguments or keywords.
Monitoring profile configuration (config-mt-prof-perf)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
This command enters admin parameters configuration mode and enables you to configure administrator parameters for a performance monitoring profile. You can configure the sampling interval.
The following example shows how to configure administrator parameters for a performance monitoring profile:
Router(config)# mediatrace profile perf-monitor v-mon-4
Router(config-mt-prof-perf)# admin-params
Router(config-mt-prof-perf-params)#sampling-interval 10
|
|
---|---|
mediatrace profile perf-monitor |
Configures Mediatrace performance monitoring profiles. |
To clear ongoing Mediatrace polls, use the clear mediatrace incomplete-sessions command in privileged EXEC mode.
clear mediatrace incomplete-sessions
This command has no arguments or keywords.
Privileged EXEC (#)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
This command clears ongoing Mediatrace polls. This command must be entered in different session.
The following example clears incomplete Mediatrace sessions:
Router# clear mediatrace incomplete-sessions
|
|
---|---|
mediatrace schedule |
Schedules Mediatrace sessions. |
To configure the clock rate for samples taken of Real-Time Transport Protocol (RTP) metrics for a Mediatrace performance monitoring profile, use the clock-rate command in RTP parameters configuration mode. To return to the default setting, use the no form of this command.
clock-rate {type-number | type-name | default} rate
no clock-rate {type-name | default}
The clock rate is set to 96000 Hz
RTP parameters configuration (config-mt-prof-perf-rtp-params)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
Each payload type has a specific clock rate associated with it. However, because the clock rate can vary depending on the payload codec type, a keyword is provided to set the expected clock rate.
The available values for type-name and type-number are celb (25), cn (13), dvi4 (5) (8000 Hz as described in RFC 3551, RTP Profile for Audio and Video Conferences with Minimal Control), dvi4-2 (6) (8000 Hz as described in RFC 3551), dvi4-3 (16) (DVI4 Dipol 11025 Hz), dvi4-4 (17) DVI4 Dipol 22050 Hz), g722 (9), g723 (4), g728 (15), g729 (18), gsm (3), h261 (31), h263 (34), jpeg (26), l16 (11) (L16 channel 1), l16-2 (10) (L16 channel 2), lpc (7), mp2t (33), mpa (14), mpv (32), nv (28), pcma (8), pcmu (0), qcelp (12).
The following example shows how to configure the clock rate for a performance monitoring profile:
Router(config)# mediatrace profile perf-monitor v-mon-4
Router(config-mt-prof-perf)# metric-list rtp
Router(config-mt-prof-perf-rtp-params)#clock-rate gsm 10000
|
|
---|---|
mediatrace profile perf-monitor |
Configures Mediatrace performance monitoring profiles. |
To configure the IP address of the destination node for the flow, use the dest-ip command in flow configuration mode. To remove the configuration for the destination node, use the no form of this command.
dest-ip ip-address dest-port port
no dest-ip ip-address
ip-address |
IP address of the destination node for the flow. |
dest-port port |
Specifies the port number of the destination node for the flow. |
No destination node for the flow is configured.
Flow configuration (config-mt-flowspec)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
When specifying the IP address of the destination node for the flow, you must also specify the port number.
The following example shows how to configure the IP address of the destination node for the flow:
Router(config)# mediatrace flow-specifier flow-4
Router(config-mt-flowspec)# dest-ip 10.10.10.4 dest-port 4800
|
|
---|---|
mediatrace flow-specifier |
Configures Mediatrace flow specifier. |
To configure the interval between samples taken of metrics, use the frequency command in session parameters configuration mode. To return to the default setting, use the no form of this command.
frequency {frequency | on-demand} inactivity-timeout seconds
no frequency
The frequency is set to 120 seconds
The inactivity-timeout is set to 360 seconds.
Session parameters configuration (config-mt-sesparam)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
The value of the inactivity-timeout should be three times the value of the frequency.
The following example shows how to configure the frequency for a session parameters:
Router(config)# mediatrace session-params sess-4
Router(config-mt-sesparam)# frequency 20 inactivity-timeout 20
|
|
---|---|
mediatrace session-params |
Configures parameters for Mediatrace sessions. |
To configure the number of history buckets retained for metrics collected for a Mediatrace session, use the history command in session parameters configuration mode. To return to the default setting, use the no form of this command.
history data-sets-kept buckets
no history data-sets-kept
data-sets-kept buckets |
Number of history buckets retained. The default is 3. The maximum value is 10. |
The number of history buckets retained is set to three.
Session parameters configuration (config-mt-sesparam)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
The maximum number of history buckets allowed is 10.
The following example shows how to configure the number of history buckets retained for a session parameters:
Router(config)# mediatrace session-params sess-4
Router(config-mt-sesparam)# history data-sets-kept 1
|
|
---|---|
mediatrace session-params |
Configures parameters for Mediatrace sessions. |
To specify which metrics are monitored for a Mediatrace flow-specifier or path-specifier profile, use the ip-protocol command in flow configuration mode. To return to the default setting, use the no form of this command.
ip-protocol {tcp | udp}
no ip-protocol
tcp |
Specifies that TCP metrics are monitored. |
udp |
Specifies that UDP metrics are monitored. |
The UDP metrics are monitored.
Flow configuration (config-mt-flowspec)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
If no protocol is specified, UDP metrics are monitored.
The following example shows how to specify that UDP metrics are monitored for a flow-specifier profile:
Router(config)# mediatrace flow-specifier flow-4
Router(config-mt-flowspec)# ip-protocol tcp
|
|
---|---|
mediatrace flow-specifier |
Configures Mediatrace flow specifier. |
To configure the maximum number of dropouts allowed when sampling Real-Time Transport Protocol (RTP) metrics for a Mediatrace performance monitoring profile, use the max-dropout command in RTP parameters configuration mode. To return to the default setting, use the no form of this command.
max-dropout number
no max-dropout
number |
Maximum number of allowed dropouts. The default is 10. The maximum value is 20. |
The maximum number of allowed dropouts is set to 10.
RTP parameters configuration (config-mt-prof-perf-rtp-params)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
The definition of maximum dropouts is the maximum number of packets to ignore ahead the current packet in terms of sequence number.
The following example shows how to configure the maximum number of allowed dropouts for a performance monitoring profile:
Router(config)# mediatrace profile perf-monitor v-mon-4
Router(config-mt-prof-perf)# metric-list rtp
Router(config-mt-prof-perf-rtp-params)# max-dropout 4
|
|
---|---|
mediatrace profile perf-monitor |
Configures Mediatrace performance monitoring profiles. |
To configure the maximum number of reorders allowed when sampling Real-Time Transport Protocol (RTP) metrics for a Mediatrace performance monitoring profile, use the max-reorder command in RTP parameters configuration mode. To return to the default setting, use the no form of this command.
max-reorder number
no max-reorder
number |
Maximum number of allowed reorders. The default is 5. The maximum value is 20. |
The maximum number of allowed reorders is set to 5.
RTP parameters configuration (config-mt-prof-perf-rtp-params)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
The definition of maximum rereorders is the maximum number of packets to ignore behind the current packet in terms of sequence number.The maximum value for the maximum number of allowed reorders is 20.
The following example shows how to configure the maximum number of allowed reorders for a performance monitoring profile:
Router(config)# mediatrace profile perf-monitor v-mon-4
Router(config-mt-prof-perf)# metric-list rtp
Router(config-mt-prof-perf-rtp-params)# max-reorder 4
|
|
---|---|
mediatrace profile perf-monitor |
Configures Mediatrace performance monitoring profiles. |
To configure Mediatrace sessions, use the mediatrace command in global configuration mode. To remove Mediatrace sessions, use the no form of this command.
mediatrace session-number
no mediatrace session-number
session-number |
ID number of the mediatrace session to configure. |
No Mediatrace sessions are configured.
Global configuration (config)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
This command enters Mediatrace session configuration mode and enables you to associate the following Mediatrace profile configurations with the session:
•Path-specifier profile
•Session-params profile
•Flow-specifier profile
•System profile
•Perf-monitor profile
The following example shows how to enter Mediatrace session configuration mode:
Router(config)# mediatrace 4
To enable the Mediatrace Initiator, use the mediatrace initiator command in global configuration mode. To disable the Mediatrace Initiator, use the no form of this command.
mediatrace initiator {source-ip ip-address | source-interface interface-name} [force] [max-sessions number]
no mediatrace initiator [force]
The Mediatrace Initiator is disabled.
When the Mediatrace Initiator is enabled, the maximum number of mediatrace sessions is set to 20.
Global configuration (config)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
Mediatrace Initiator is disabled by default. Therefore, no Mediatrace services are available until you issue this command for the Mediatrace Initiator. Before you can use Mediatrace, you must issue this command on one of the nodes in the media path and issue the mediatrace responder command on all nodes that you want to support Mediatrace.
Tip When you enable the Mediatrace Initiator, you must specify a local interface or an address on a local interface. For large deployments, The use of the source-interface keyword is recommended.
You can also use this command to set the maximum sessions that can be started by the Mediatrace Initiator. The upper limit for the maximum number of mediatrace sessions is platform-dependant.
The following example shows how to enable the Mediatrace Initiator on the local interface with an IP address of 10.10.2.2:
Router(config)# mediatrace initiator source-ip 10.10.2.2
|
|
---|---|
mediatrace profile perf-monitor |
Configures Mediatrace performance monitoring profiles. |
To enable the Mediatrace Responder, use the mediatrace responder command in global configuration mode. To disable the Mediatrace Responder, use the no form of this command.
mediatrace responder [max-sessions number]
no mediatrace responder
max-sessions number |
(Optional) Sets the maximum number of Mediatrace sessions. |
The Mediatrace Responder are disabled.
The maximum number of mediatrace sessions is set to 20.
Global configuration (config)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
Mediatrace Responder is disabled by default. Therefore, no Mediatrace services are available until you issue this command for the Mediatrace Responder. Before you can use Mediatrace, you must issue the mediatrace initiator command on one of the nodes in the media path and issue this command on all nodes that you want to support Mediatrace.
You can also use this command to set the maximum sessions that can be used by the Mediatrace Responder. The upper limit for the maximum number of mediatrace sessions is platform-dependant.
The following example shows how to enable the Mediatrace Responder on a node with an IP address of 10.10.10.4:
Router(config)# mediatrace responder max-sessions 12
|
|
---|---|
mediatrace profile perf-monitor |
Configures Mediatrace performance monitoring profiles. |
To configure the path-specifier profile for Mediatrace, use the mediatrace path-specifier command in global configuration mode. To remove the path specifier profile, use the no form of this command.
mediatrace path-specifier name [disc-proto rsvp] destination-ip ip-address [port number]
no mediatrace path-specifier name
No path-specifier profile is configured.
Global configuration (config)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
After using this command to enter path configuration mode, you can configure the source address and port of the path.
You can associate a path-specifier profile with one or more actual Mediatrace sessions when they are configured.
The following example shows how to configure a path-specifier profile with a destination address of 10.10.2.8:
Router(config)# mediatrace path-specifier path-2 destination ip 10.10.2.8
|
|
---|---|
mediatrace |
Configures Mediatrace sessions. |
To perform an on-demand fetch of data, use the mediatrace poll command in privileged EXEC mode.
mediatrace poll {session number | {[timeout value] path-specifier {name path-name} | [disc-proto rsvp] destination ip-address [port number]} [source ip-address [port number]] [ip-protocol {tcp | udp}] } {app-health | hops | system [profile system-profile-name] | [configless] perf-monitor [profile profile-name]} {flow-specifier name | source-ip ipaddress source-port number dest-ip ipaddress dest-port numbern ip-protocol {tcp | udp}}}
The timeout is 60 seconds.
Privileged EXEC (#)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
For existing Performance Monitor profiles, the minimum value of the timeout allowed will depend on the sampling-interval configured in profile. If default perf-monitor profile is used then default value of sampling-interval is 30 second so minimum timeout value is 60 seconds.
The following examples show some ways you can use the mediatrace poll command to perform an on-demand fetch of data from the hops on a specific path:
•To retrieve data using a pre-configured session. In this case, no other parameters have to be specified inline. The pre-configured session must be have the frequency type set to on-demand.
•To retrieve the system data, hop or video monitoring information from hops along the specified path. You can specify the path as a pre-configured path-specifier or an inline path specification, in case you do not have config mode privileges. Note that by default, Cisco Mediatrace tries to configure nodes along the path to report passive monitoring metrics, and then waits for a configurable amount of time before going out again to collect the data.
•The configless keyword can be used to fetch data from the nodes along a media path, which already have Performance Monitor policies configured using the Performance Monitor commands. Some key things to keep in mind when fetching data using this method are that:
–The default perf-monitor profile or associated perf-monitor profile will have a sampling interval. If the sampling interval of the static policy does not match the one in the associated perf-monitor profile, no data is returned.
–If there is no Performance Monitor policy configured on a Responder node, the Cisco Mediatrace Responder does not try to configure Performance Monitor and simply reports error to the Mediatrace Initiator.
If Cisco Mediatrace is not collecting all of the data that you want:
•Use the show mediatrace session command 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 sessions command to determine the status of the nodes being monitored.
•Use the debug mediatrace command to view error messages.
Note For examples of poll output, see the end of this section.
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-address port number destination ip-address port number ip-protocol udp system
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 number dest-ip ip-address dest-port number 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 number dest-ip ip-address dest-port number 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 number dest-ip ip-address dest-port number 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 number dest-ip ip-address dest-port number ip-protocol tcp
The following example shows how to fetch the default set of RTP metrics from an existing static policy configured on the Responders. This command does not configure the Performance Monitor, so for more information, see Configuring 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 number dest ip-address port number 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
|
|
---|---|
mediatrace profile perf-monitor |
Configures Mediatrace performance monitoring profiles. |
To configure a Mediatrace performance monitoring profile, use the mediatrace profile perf-monitor command in global configuration mode. To remove a performance monitoring profile, use the no form of this command.
mediatrace profile perf-monitor name
no mediatrace profile perf-monitor name
name |
Name used to identify the profile. |
No Mediatrace performance monitoring profile is configured.
Global configuration (config)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
After using this command to enter perf-prof configuration mode, you can configure the following optional parameters:
•Sampling interval
•Clock rate
•Maximum number of dropouts
•Maximum number of reorders
•Minimum number of sequential errors
You can associate a performance monitoring profile with one or more actual Mediatrace sessions when they are configured.
The following example shows how to configure a performance monitoring profile:
Router(config)# mediatrace profile perf-monitor v-mon-4
Router(config-mt-prof-perf)# metric-list rtp
Router(config-mt-prof-perf-rtp-params)# clock-rate 84
Router(config-mt-prof-perf-rtp-params)# max-dropout 2
Router(config-mt-prof-perf-rtp-params)# max-reorder 4
Router(config-mt-prof-perf-rtp-params)# min-sequential 2
Router(config-mt-prof-perf-rtp-params)# exit
Router(config-mt-prof-perf)# admin-params
Router(config-mt-prof-perf-params)# sampling-interval 20
|
|
---|---|
mediatrace flow-specifier |
Configures Mediatrace flow specifier. |
To configure a system-data monitoring profile, use the mediatrace profile system command in global configuration mode. To remove a system profile, use the no form of this command.
mediatrace profile system name
no mediatrace profile system name
name |
Name used to identify the profile. |
No Mediatrace system-data profile is configured.
Global configuration (config)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
After using this command to enter system-data profile configuration mode, you can configure which of the following types of system data are monitored:
•Interface
•CPU
•Memory
You can associate a system-data monitoring profile with one or more actual Mediatrace sessions when they are configured.
The following example shows how to configure a sysem-data monitoring profile:
Router(config)# mediatrace profile system system-8
Router(config-sys-prof)# metric-list CPU MEMORY
|
|
---|---|
mediatrace profile perf-monitor |
Configures Mediatrace performance monitoring profiles. |
To configure when a Mediatrace session will occur, use the mediatrace schedule command in global configuration mode. To remove a Mediatrace schedule, use the no form of this command.
mediatrace schedule session ID [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring]
no mediatrace schedule session ID
No schedule is specified for the session and it is in the pending state.
Global configuration (config)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
The following example shows how to configure a session schedule that will start now and last 60 seconds:
Router(config)# mediatrace schedule 22 life 60 now
|
|
---|---|
mediatrace session-number |
Configures a Mediatrace session. |
To configure session-parameters, use the mediatrace session-params command in global configuration mode. To remove the session-parameters configuration, use the no form of this command.
mediatrace session-params name
no mediatrace session-params name
name |
Name used to identify the profile. |
No session-parameters profile is configured.
Global configuration (config)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
After using this command to enter session-parameters configuration mode, you can configure the following parameters:
•Sampling frequency
•Inactivity timeout
•Number of historical data sets kept
•Response timeout
•Route change reaction time
You can associate a session-parameters profile with one or more actual Mediatrace sessions when they are configured.
The following example shows how to configure a session-parameters profile:
Router(config)# mediatrace session-params session-4
Router(config-mt-sesparam)# frequency 20 inactivity-timeout 40
Router(config-mt-sesparam)# history data-sets-kept 2
Router(config-mt-sesparam)# response-timeout 20
Router(config-mt-sesparam)# route-change reaction-time 4
|
|
---|---|
mediatrace profile perf-monitor |
Configures Mediatrace performance monitoring profiles. |
To specify monitoring parameters for a Mediatrace performance monitoring profile, use the metric-list command in monitoring profile configuration mode. To return to the default setting, use the no form of this command.
metric-list {tcp | rtp}
no metric-list {tcp | rtp}
tcp |
Configures monitoring parameters for TCP packets. |
rtp |
Configures monitoring parameters for Real-Time Transport Protocol (RTP) packets. |
The RTP metrics are monitored.
Monitoring profile configuration (config-mt-prof-perf)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
This command specifies whether TCP packet or RTP packet are monitored and enters monitoring parameters configuration mode for a performance monitoring profile. For RTP, you can configure the following parameters:
•Clock rate
•Maximum number of dropouts allowed
•Maximum number of packet allowed to be received out of order
•Minimum number of packets in a sequence used to classify a RTP flow
The following example shows how to configure monitoring parameters for RTP packets:
Router(config)# mediatrace profile perf-monitor v-mon-4
Router(config-mt-prof-perf)# metric-list rtp
Router(config-mt-prof-perf-rtp-params)# clock-rate 84
Router(config-mt-prof-perf-rtp-params)# max-dropout 2
Router(config-mt-prof-perf-rtp-params)# max-reorder 4
Router(config-mt-prof-perf-rtp-params)# min-sequential 2
|
|
---|---|
mediatrace profile perf-monitor |
Configures Mediatrace performance monitoring profiles. |
To specify which metrics are monitored for a Mediatrace system-data profile.use the metric-list command in system profile configuration mode. To return to the default setting, use the no form of this command.
metric-list {intf | cpu | memory}
no metric-list {intf | cpu | memory}
intf |
(Optional) Monitor interface metrics. |
cpu |
(Optional) Monitor CPU metrics. |
memory |
(Optional) Monitor memory metrics. |
The interface metrics are monitored.
System profile configuration (config-mt-prof-sys)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
If no metric list is specified, Interface metrics are monitored.
The following example shows how to specify that CPU metrics are monitored:
Router(config)# mediatrace profile system sp-4
Router(config-mt-prof-sys)# metric-list cpu
|
|
---|---|
mediatrace profile system |
Configures Mediatrace system profiles. |
To configure the minimum number of packets in a sequence used to classify a Real-Time Transport Protocol (RTP) flow for a Mediatrace performance monitoring profile, use the min-sequential command in RTP parameters configuration mode. To return to the default setting, use the no form of this command.
min-sequential number
no min-sequential number
number |
Minimum number of packets in a sequence used to classify a RTP flow. |
The minimum number of packets in a sequence is set to 5.
RTP parameters configuration (config-mt-prof-perf-rtp-params)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
The maximum value for the minimum number of packets in a sequence used to classify a RTP flow is 10.
The following example shows how to configure the minimum number of packets in a sequence used to classify a RTP flow for a performance monitoring profile:
Router(config)# mediatrace profile perf-monitor v-mon-4
Router(config-mt-prof-perf)# metric-list rtp
Router(config-mt-prof-perf-rtp-params)# min-sequential 4
|
|
---|---|
mediatrace profile perf-monitor |
Configures Mediatrace performance monitoring profiles. |
To associate a Mediatrace path-specifier profile with a Mediatrace session, use the path-specifier command in session configuration mode. To remove the association, use the no form of this command.
path-specifier name
no path-specifier name
name |
Name used to identify the profile. |
No path-specifier profile is configured.
Session configuration (config-mt-session)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
You can associate a path-specifier profile with one or more actual Mediatrace sessions.
The following example shows how to associate a Mediatrace path-specifier profile to a Mediatrace session:
Router(config)# mediatrace 4
Router(config-mt-session)# path-specifier ps-4
|
|
---|---|
mediatrace |
Configures a Mediatrace session. |
To associate a performance monitoring profile and a flow-specifier profile with a Mediatrace session, use the profile perf-monitor command in session configuration mode. To remove the association, use the no form of this command.
profile perf-monitor pm-name flow-specifier fs-name
no profile perf-monitor pm-name flow-specifier fs-name
No performance monitoring profile is configured.
Session configuration (config-mt-session)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
You can associate a performance monitoring profile with one or more actual Mediatrace sessions.
The following example shows how to associate a Mediatrace performance monitoring profile to a Mediatrace session:
Router(config)# mediatrace 4
Router(config-mt-session)# profile perf-monitor pm-4 flow-specifier fs-2
|
|
---|---|
mediatrace |
Configures a Mediatrace session. |
To associate a Mediatrace system profile to a Mediatrace session, use the profile system command in session configuration mode. To remove the association, use the no form of this command.
profile system name
no profile system name
name |
Name used to identify the profile. |
No system profile is configured.
Session configuration (config-mt-session)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
You can associate a system profile with one or more actual Mediatrace sessions.
The following example shows how to associate a Mediatrace system profile to a Mediatrace session:
Router(config)# mediatrace 4
Router(config-mt-session)# profile system sprofile-4
|
|
---|---|
mediatrace |
Configures a Mediatrace session. |
To configure the number of seconds the Mediatrace Initiator will wait for the Responder to provide metrics, use the response-timeout command in session parameters configuration mode. To return to the default setting, use the no form of this command.
response-timeout seconds
no response-timeout seconds
seconds |
The number of seconds the Mediatrace Initiator will wait for the Responder to provide metrics. |
The response-timeout is set to 60 seconds.
Session parameters configuration (config-mt-sesparam)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
The maximum value for the response-timeout is 65535 seconds. The response timeout should be less than the frequency.
The following example shows how to configure the response-timeout for a session parameters:
Router(config)# mediatrace session-params sess-4
Router(config-mt-sesparam)# response-timeout 20
|
|
---|---|
mediatrace session-params |
Configures parameters for Mediatrace sessions. |
To configure the number of seconds the Mediatrace Initiator will wait for a response to a route change notification, use the route change command in session parameters configuration mode. To return to the default setting, use the no form of this command.
route-change reaction-time seconds
no route-change reaction-time seconds
seconds |
Number of seconds the Mediatrace Initiator will wait for a response to a route change notification. |
The route change reaction time is set to 5 seconds.
Session parameters configuration (config-mt-sesparam)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
The maximum value for the route change reaction time is 60 seconds.
The following example shows how to configure the route change reaction time for a session parameters:
Router(config)# mediatrace session-params sess-4
Router(config-mt-sesparam)# route-change reaction-time 20
|
|
---|---|
mediatrace session-params |
Configures parameters for Mediatrace sessions. |
To configure the interval, in seconds, between samples taken of metrics for a Mediatrace performance monitoring profile, use the sampling-interval command in admin parameters configuration mode. To return to the default setting, use the no form of this command.
sampling-interval seconds
no sampling-interval seconds
seconds |
Number of seconds between samples are taken of metrics. |
The sampling interval is set to 30 minutes.
Admin parameters configuration (config-mt-prof-perf-params)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
The sampling interval can set to a maximum of 30 minutes.
The following example shows how to configure the sampling interval for a performance monitoring profile:
Router(config)# mediatrace profile perf-monitor v-mon-4
Router(config-mt-prof-perf)# admin-params
Router(config-mt-prof-perf-params)#sampling-interval 10
|
|
---|---|
mediatrace profile perf-monitor |
Configures Mediatrace performance monitoring profiles. |
To associate a Mediatrace session-params profile to a Mediatrace session, use the session-params command in session configuration mode. To remove the association, use the no form of this command.
session-params name
no session-params name
name |
Name used to identify the profile. |
Session configuration (config-mt-session)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
You can associate a session-params profile with one or more actual Mediatrace sessions.
The following example shows how to associate a Mediatrace session-params profile to a Mediatrace session:
Router(config)# mediatrace 4
Router(config-mt-session)# session-params sp-4
|
|
---|---|
mediatrace |
Configures a Mediatrace session. |
To display the parameters configured for flow-specifier profiles, use the show mediatrace flow-specifier command in privileged EXEC mode.
show mediatrace flow-specifier [name]
name |
(Optional) Name used to identify the profile. |
All flow-specifier profiles are displayed.
Privileged EXEC (#)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
If no flow-specifier profile name is entered with this command, all profiles are displayed.
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
Table 8 describes the significant fields shown in the display.
|
|
---|---|
mediatrace flow-specifier |
Configures Mediatrace monitoring flow specifier. |
To display the parameters configured for the Mediatrace Initiator profile, use the show mediatrace initiator command in privileged EXEC mode.
show mediatrace initiator
This command has no arguments or keywords.
Privileged EXEC (#)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
There is only one Mediatrace Initiator profile that can be displayed.
The following example displays the Mediatrace 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.
Table 9 describes the significant fields shown in the display.
|
|
---|---|
mediatrace path-specifier |
Configures Mediatrace monitoring path specifier. |
To display the parameters configured for path-specifier profiles, use the show mediatrace path-specifier command in privileged EXEC mode.
show mediatrace path-specifier [name]
name |
(Optional) Name used to identify the profile. |
All path-specifier profiles are displayed.
Privileged EXEC (#)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
If no path-specifier profile name is entered with this command, all profiles are displayed.
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
Table 12 describes the significant fields shown in the display.
|
|
---|---|
mediatrace path-specifier |
Configures Mediatrace monitoring path specifier. |
To display the parameters configured for system-data profiles, use the show mediatrace profile system command in privileged EXEC mode.
show mediatrace profile system [name]
name |
(Optional) Name used to identify the profile. |
All system-data profiles are displayed.
Privileged EXEC (#)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
If no system-data profile name is entered with this command, all profiles are displayed.
The following example displays system-data profiles:
Router# show mediatrace profile system
System Profile: sys-1
Metric List: intf
Table 11 describes the significant fields shown in the display.
|
|
---|---|
System Profile |
Name assigned to the profile. |
Metric List |
Whether metrics are collected for interfaces, CPUs, or memory. |
|
|
---|---|
mediatrace profile perf-monitor |
Configures Mediatrace performance monitoring profiles. |
To display the parameters configured for performance monitoring profiles, use the show mediatrace profile perf-monitor command in privileged EXEC mode.
show mediatrace profile perf-monitor [name]
name |
(Optional) Name used to identify the profile. |
All performance monitoring profiles are displayed.
Privileged EXEC (#)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
If no performance monitoring profile name is entered with this command, all profiles are displayed.
The following example displays performance 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
Table 12 describes the significant fields shown in the display.
|
|
---|---|
mediatrace profile perf-monitor |
Configures Mediatrace performance monitoring profiles. |
To display application health information for the Mediatrace Responder, use the show mediatrace responder app-health command in privileged EXEC mode.
show mediatrace responder app-health
This command has no arguments or keywords.
Privileged EXEC (#)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
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
Table 13 describes the significant fields shown in the display.
|
|
---|---|
mediatrace session-params |
Configures parameters for Mediatrace sessions. |
To display session information for the Mediatrace Responder, use the show mediatrace responder sessions command in privileged EXEC mode.
show mediatrace responder sessions [global-session-id | brief | details]
The detailed session information is displayed for the Mediatrace Responder
Privileged EXEC (#)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
If no session ID is entered with this command, inforamtion for all sessions is displayed.
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
Table 14 describes the significant fields shown in the display.
|
|
---|---|
mediatrace session-params |
Configures parameters for Mediatrace sessions. |
To display information for Mediatrace sessions, use the show mediatrace session command in privileged EXEC mode.
show mediatrace session [config | data | hops | stats]
Privileged EXEC (#)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
You must have at least one active session before most session information can be displayed.
The following example displays session configuration information:
Router# show mediatrace session config
Session Index: 1
Global Session Id: 0
---------------------------
Session Details:
Path-Specifier: ps1
Session Params: sp1
Collectable Metrics Profile: s1
Flow Specifier: fs1
Schedule:
Operation frequency (seconds): 120 (not considered if randomly scheduled)
Next Scheduled Start Time: Pending trigger
Group Scheduled : FALSE
Randomly Scheduled : FALSE
Life (seconds): 3600
Entry Ageout (seconds): never
Recurring (Starting Everyday): FALSE
Status of entry (SNMP RowStatus): notInService
Table 16 describes the significant fields shown in the display.
|
|
---|---|
mediatrace session-params |
Configures parameters for Mediatrace sessions. |
To display the parameters configured for Mediatrace sessions, use the show mediatrace session-params command in privileged EXEC mode.
show mediatrace session-params [name]
name |
(Optional) Name used to identify the profile. |
All session profiles are displayed.
Privileged EXEC (#)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
If no session profile name is entered with this command, all profiles are displayed.
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
Table 16 describes the significant fields shown in the display.
|
|
---|---|
mediatrace session-params |
Configures parameters for Mediatrace sessions. |
To configure the IP address of the source node for the flow, use the source-ip command in flow configuration mode. To remove the configuration for the source node, use the no form of this command.
source-ip ip-address [source-port port]
no source-ip ip-address [source-port port]
ip-address |
IP address of the source node for the flow. |
source-port port |
Port number of the source node for the flow. |
Flow configuration (config-mt-flowspec)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
When specifying the IP address of the source node for the flow, the port number is optional.
The following example shows how to configure the IP address of the source node for the flow:
Router(config)# mediatrace flow-specifier flow-4
Router(config-mt-flowspec)# source-ip 10.10.10.4
|
|
---|---|
mediatrace flow-specifier |
Configures Mediatrace flow specifier. |
To configure the IP address of the source node for the path, use the source-ip command in path configuration mode. To remove the configuration for the source node, use the no form of this command.
source ip ip-address [port port]
no source ip ip-address [port port]
ip-address |
IP address of the source node for the path. |
port port |
Port number of the source node for the path. |
Path configuration (config-mt-path)
|
|
---|---|
15.1(3)T |
This command was introduced. |
12.2(58)SE |
This command was integrated into Cisco IOS Release 12.2(58)SE. |
When specifying the IP address of the source node for a path, the port number is optional.
The following example shows how to configure the IP address of the source node for the path:
Router(config)# mediatrace path-specifier path-4
Router(config-mt-path)# source ip 10.10.10.4
|
|
---|---|
mediatrace path-specifier |
Configures Mediatrace path specifiers |