traceroute
Syntax
Syntax (QFX Series)
Release Information
Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
mpls option introduced in Junos OS Release 9.2.
Command introduced in Junos OS Release 11.1 for the QFX Series.
propagate-ttl option introduced in Junos OS Release 12.1.
Description
Display the route that packets take to a specified network host. Use traceroute as a debugging tool to locate points of failure in a network.
Options
host | — | IP address or name of remote host. |
as-number-lookup | — | (Optional) Display the autonomous system (AS) number of each intermediate hop on the path from the host to the destination. |
bypass-routing | — | (Optional) Bypass the normal routing tables and send requests directly to a system on an attached network. If the system is not on a directly attached network, an error is returned. Use this option to display a route to a local system through an interface that has no route through it. |
clns | — | (Optional) Trace the route belonging to the Connectionless Network Service (CLNS). |
gateway address | — | (Optional) Address of a router or switch through which the route transits. |
inet | inet6 | — | (Optional) Trace the route belonging to IPv4 or IPv6, respectively. |
interface interface-name | — | (Optional) Name of the interface over which to send packets. |
logical-system logical-system-name | — | (Optional) Perform this operation on all logical systems or on a particular logical system. |
monitor host | — | (Optional) Display real-time monitoring information for the specified host. |
mpls (ldp FEC address | rsvp label-switched-path name) | — | (Optional) See traceroute mpls ldp and traceroute mpls rsvp. |
no-resolve | — | (Optional) Do not attempt to determine the hostname that corresponds to the IP address. |
propagate-ttl | — | (Optional) On the PE router, use this option to view locally generated Routing Engine transit traffic. This is applicable for MPLS L3VPN traffic only. Use for troubleshooting, when you want to view hop-by-hop information from the local provider router to the remote provider router, when TTL decrementing is disabled on the core network using the no-proagate-ttl configuration statement.
|
routing-instance routing-instance-name | — | (Optional) Name of the routing instance for the traceroute attempt. |
source source-address | — | (Optional) Source address of the outgoing traceroute packets. |
tos value | — | (Optional) Value to include in the IP type-of-service (ToS) field. The range of values is 0 through 255. |
ttl value | — | (Optional) Maximum time-to-live value to include in the traceroute request. The range of values is 0 through 128. |
wait seconds | — | (Optional) Maximum time to wait for a response to the traceroute request. |
Required Privilege Level
network
List of Sample Output
traceroutetraceroute as-number-lookup host
traceroute no-resolve
traceroute propogate-ttl
traceroute (Between CE Routers, Layer 3 VPN)
traceroute (Through an MPLS LSP)
Output Fields
Table 1 describes the output fields for the traceroute command. Output fields are listed in the approximate order in which they appear.
Table 1: traceroute Output Fields
Field Name | Field Description |
|---|---|
traceroute to | IP address of the receiver. |
hops max | Maximum number of hops allowed. |
byte packets | Size of packets being sent. |
number-of-hops | Number of hops from the source to the named router or switch. |
router-name | Name of the router or switch for this hop. |
address | Address of the router or switch for this hop. |
Round trip time | Average round-trip time, in milliseconds (ms). |
Sample Output
traceroute
user@host> traceroute santacruz traceroute to green.company.net (10.156.169.254), 30 hops max, 40 byte packets 1 blue23 (10.168.1.254) 2.370 ms 2.853 ms 0.367 ms 2 red14 (10.168.255.250) 0.778 ms 2.937 ms 0.446 ms 3 yellow (10.156.169.254) 7.737 ms 89.905 ms 0.834 ms
traceroute as-number-lookup host
user@host> traceroute as-number-lookup 10.100.1.1traceroute to 10.100.1.1 (10.100.1.1), 30 hops max, 40 byte packets 1 10.39.1.1 (10.39.1.1) 0.779 ms 0.728 ms 0.562 ms 2 10.39.1.6 (10.39.1.6) [AS 32] 0.657 ms 0.611 ms 0.617 ms 3 10.100.1.1 (10.100.1.1) [AS 10, 40, 50] 0.880 ms 0.808 ms 0.774 ms
traceroute no-resolve
user@host> traceroute santacruz no-resolve traceroute to green.company.net (10.156.169.254), 30 hops max, 40 byte packets 1 10.168.1.254 0.458 ms 0.370 ms 0.365 ms 2 10.168.255.250 0.474 ms 0.450 ms 0.444 ms 3 10.156.169.254 0.931 ms 0.876 ms 0.862 ms
traceroute propogate-ttl
user@host> traceroute propagate-ttl 100.200.2.2
routing-instance VPN-A traceroute to 100.200.2.2 (100.200.2.2) from 1.1.0.2, 30 hops max, 40 byte packets
1 1.2.0.2 (1.2.0.2) 2.456 ms 1.753 ms 1.672 ms
MPLS Label=299776 CoS=0 TTL=1 S=0
MPLS Label=299792 CoS=0 TTL=1 S=1
2 1.3.0.2 (1.3.0.2) 1.213 ms 1.225 ms 1.166 ms
MPLS Label=299792 CoS=0 TTL=1 S=1
3 100.200.2.2 (100.200.2.2) 1.422 ms 1.521 ms 1.443 ms
traceroute (Between CE Routers, Layer 3 VPN)
user@host> traceroute vpn09
traceroute to vpn09.skybank.net (10.255.14.179), 30 hops max, 40
byte packets
1 10.39.10.21 (10.39.10.21) 0.598 ms 0.500 ms 0.461 ms
2 10.39.1.13 (10.39.1.13) 0.796 ms 0.775 ms 0.806 ms
MPLS Label=100006 CoS=0 TTL=1 S=1
3 vpn09.skybank.net (10.255.14.179) 0.783 ms 0.716 ms 0.686
traceroute (Through an MPLS LSP)
user@host> traceroute mpls1
traceroute to 10.168.1.224 (10.168.1.224), 30 hops max, 40 byte packets
1 mpls1-sr0.company.net (10.168.200.101) 0.555 ms 0.393 ms 0.367 ms
MPLS Label=1024 CoS=0 TTL=1
2 mpls5-lo0.company.net (10.168.1.224) 0.420 ms 0.394 ms 0.401 ms
