Reports for Troubleshooting › Traceroute Investigations › Manually Launch Traceroute Investigation

Manually Launch Traceroute Investigation

Take the following steps to launch a traceroute investigation.

Follow these steps:

1. Click Troubleshooting, Launch Investigation in the navigation bar.

   The Launch Traceroute page opens.

2. Complete the following fields:
   • Target Type. Use this field to select the type of target you want to investigate. Select Location, Media Device, or Device. Your selection determines the options that are available in the Target menu and in the Investigation Options section.
     Tips:
     • If the target is an IP address or DNS host name, select Device.
     • If the target is a voice gateway, select Media Device.
   • Target. Use this field to identify the target device you want to investigate. This device is the destination of the traceroute. The available targets depend on the Target Type you select.
     • If the Target Type is Location, the target Location must have a Cisco key phone defined.
     • If the Target Type is Device, enter the device IP address or DNS host name.
     • If the Target is an Avaya IP phone, select ICMP in the Protocol field.
   • Investigate From. This field identifies the collector that launches the traceroute. The management console selects the appropriate collector for the Target unless you selected Device as the Target Type.
   • Protocol. This field identifies the protocol to use for the traceroute.

     If you select Location or Media Device as the Target Type, the collector uses TCP over port 80.

     If you select Device as the Target Type, select the protocol for the call server or gateway device:

     • ICMP. ICMP is the only supported protocol for Avaya IP phone targets.
     • TCP over port 80
     • TCP for SIP (port 5060)
     • TCP for MGCP (port 2428)
     • TCP for H.323 (port 1720)

     For all traceroutes, including baseline traceroutes, the DiffServ ToS bits in the header are set for CS3 handling, the standard for call setup traffic.

   • Retries. Specify the number of probes, from 0 to 10, to send to each component in the route when a target endpoint does not respond. The default is 2 retries.
   • Route Searches. Specify the number of times, from 0 to 20, to attempt to find other routes for the selected target. Multiple traceroutes are attempted to see whether alternate routes are used between the collector and the target endpoint. The default is 0.

     All attempted unique routes are included in the Investigation Report.

   • Timeout. Specify the number of seconds, from 1 to 10, that must elapse before UC Monitor considers the traceroute timed out because the target is unreachable. The default is 2 seconds.
3. Click Launch.

   Results are displayed when they are available.

More information:

Incident Investigations