Configuring Cisco Mediatrace

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.

• Metrics That You Can Collect Using 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:

1. Enable mediatrace
2. Setup a video-monitoring profile
3. Setup a system-data profile
4. Setup a path-specifier profile
5. Setup a flow-specifier profile
6. Setup a sessions-params profile
7. Associate profiles with a mediatrace session
8. 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

1.    enable

2.    configure terminal

3.    mediatrace initiator {source-ip ip-address | source-interface interface-name} [force] [max-sessions number ]

4.    mediatrace responder [max-sessions number ]

5.    end

• Troubleshooting Tips
  

1.    enable

2.    configure terminal

3.    mediatrace profile perf-monitor name

4.    admin-params

5.    sampling-interval seconds

6.    exit

7.    metric-list {tcp | rtp}

8.    clock-rate {type-number | type-name} rate

9.    max-dropout number

10.    max-reorder number

11.    min-sequential number

12.    end

• Troubleshooting Tips
  

1.    enable

2.    configure terminal

3.    mediatrace profile system name

4.    metric-list {intf | cpu | memory}

5.    end

• Troubleshooting Tips
  

1.    enable

2.    configure terminal

3.    mediatrace path-specifier name disc- proto rsvp destination ip ip-address port nnnn

4.    source ip ip-address port nnnn

5.    l2-params gateway ip-address vlan vlan-id

6.    end

• Troubleshooting Tips
  

1.    enable

2.    configure terminal

3.    mediatrace flow-specifier name

4.    source-ip ip-address source-port port

5.    dest- ip ip-address dest-port port

6.    ip-protocol {tcp | udp}

7.    end

• Troubleshooting Tips
  

1.    enable

2.    configure terminal

3.    mediatrace session-params name

4.    response-timeout seconds

5.    frequency {frequency | on-demand} inactivity-timeout seconds

6.    history buckets

7.    route-change reaction-time seconds

8.    end

• Troubleshooting Tips
  

1.    enable

2.    configure terminal

3.    mediatrace session-number

4.    path-specifier name

5.    session-params name

6.    profile system name

7.    profile perf-monitor name flow-specifier name

8.    end

• Troubleshooting Tips
  

1.    enable

2.    configure terminal

3.    mediatrace schedule session ID [life {forever | secs}] [start-time {hh:mm:[:ss][month day| day month] | pending | now | after hh:mm:ss}] [ageout secs] [recurring]

4.    end

• Troubleshooting Tips
  

1.    enable

2.    clear mediatrace incomplete-sessions

3.    end

• Troubleshooting Tips
  

1.    enable

2.    mediatrace poll {session number |{[timeout value] path-specifier{name path-name}|[disc-proto rsvp] destination ip ip-address [port nnnn]}[source ip ip-address [port nnnnn]] [protocol{tcp| udp}]} {app-health| hops| system[profile system-profile-name]|

3.    end

• Troubleshooting Tips
  
• Examples
  

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.

1.    enable

2.    configure terminal

3.    show mediatrace profile perf-monitor [name]

4.    show mediatrace profile system [name]

5.    show mediatrace flow-specifier [name]

6.    show mediatrace path-specifier [name]

7.    show mediatrace initiator

8.    show mediatrace session-params [name]

9.    show mediatrace session [config| data| stats| hops] [brief| ID]

10.    show mediatrace responder app-health

11.    show mediatrace responder sessions [ global-session-id | brief | details]

12.    debug mediatrace {event | trace | error} [initiator | responder| session-id]

13.    end

Examples

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