Help Center User GuideGetting StartedFAQRelease NotesRelease NotesRelease NotesRelease Notes
 
X
User Guide
Getting Started
FAQ
Release Notes
Release Notes
Release Notes
Release Notes
Contents  

Identifying Connectivity Issues by Using Traceroute

You can use Contrail Service Orchestration (CSO) to perform a traceroute operation from a device (provider hub, tenant device, CPE device, EX switch, enterprise hubs, or next-generation firewall device) to the remote host. Traceroute helps you view the path that a packet travels to reach the remote host. The result is useful in identifying the point of network failure in the path between the source device and remote host.

Note In Contrail Service Orchestration (CSO) Release 5.0, the following devices support traceroute:

  • EX Series: EX2300, EX3400, EX4300

  • MX Series

  • NFX Series: NFX150, NFX250

  • SRX Series: SRX300, SRX320, SRX340, SRX345, SRX1500, SRX4100, SRX4200, SRX4600

  • vSRX

Procedure

To perform traceroute operation:

  1. Do one of the following:
    • To initiate traceroute from a provider hub device, select Resources > Provider Hub Devices.

      The Provider Hub Devices page appears.

    • To initiate traceroute from a tenant device, select Resources > Tenant Devices.

      The Tenant Devices page appears.

  2. Select a device from the list of devices displayed and click More > Traceroute.

    The Traceroute page appears.

  3. Complete the configuration according to the guidelines provided in Table 40.

    Note  Fields marked with an asterisk (*) are mandatory.

  4. Click Traceroute to initiate the traceroute operation.

    A job is created and a traceroute progress page appears. If the traceroute operation is successful, the Traceroute Result page displays the traceroute parameters specified in Table 41.

    If the traceroute operation fails, the Traceroute Result page displays an appropriate error message (such as No response or No route to host).

Table 40: Fields on the Traceroute page

Field

Description

Remote Host

Enter the IPv4 address or hostname of the remote host.

Maximum Hops

Specify the maximum number of network devices that a packet can pass through to reach the remote host.

Default: 30.

Range: 1 through 255.

If the number of hops to reach the remote host exceeds the set value, the traceroute packet is dropped.

Advanced

Source Interface

Select a source interface on the device from which you want to send the packets to the remote host.

Click Clear All to remove the selected interface and select another interface.

Hostname Resolution

Click the toggle button to enable or disable (default) the display of hostname of the hops in the path to the remote host.

Wait Time (seconds)

Enter the time until which the device waits for a response from the remote host to a packet sent before considering timeout.

Default: 10 seconds.

Range: 0 through 86,399 seconds.

Routing Instance

Select a routing instance that the traceroute request packets can use to reach the remote host.

The trace result displays the route information based on the configured routing instance type.

To clear the selected routing instance, click Clear All and select another routing instance.

Table 41 lists the parameters on the Traceroute Result page when the traceroute operation is successful.

Table 41: Fields on the Traceroute Result page

Field

Description

Hop

Hostname or IPv4 address of the network devices that the packet passed through to reach the remote host.

Time Taken by Packet 1

Time Taken by Packet 2

Time Taken by Packet 3

Duration (in microseconds) between the time from when the source device sends a packet, and the time it received a response from the hops and the remote host.

Help us to improve. Rate this article.
Feedback Received. Thank You!

Ask questions in TechWiki

Check documentation in TechLibrary

Rating by you:      
X

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:
Email:

Need product assistance? Contact Juniper Support

Submit