Command Reference Guide

Device Location, System Utility, and Clear Commands
CLI Command Reference
September 2014 Page 191
HP Moonshot Switch Module CLI Command Reference
traceroute
Use the traceroute command to discover the routes that IPv4 or IPv6 packets actually take when traveling to
their destination through the network on a hop-by-hop basis. Traceroute continues to provide a synchronous
response when initiated from the CLI.
The user may specify the source IP address of the traceroute probes. Recall that traceroute works by sending
packets that are expected not to reach their final destination, but instead trigger ICMP error messages back to
the source address from each hop along the forward path to the destination. By specifying the source address,
the user can determine where along the forward path there is no route back to the source address. Note that
this is only useful if the route from source to destination and destination to source is symmetric.) It would be
common, for example, to send a traceroute from an edge router to a target higher in the network using a
source address from a host subnet on the edge router. This would test reachability from within the network
back to hosts attached to the edge router. Alternatively, one might send a traceroute with an address on a
loopback interface as a source to test reachability back to the loopback interface address.
In the CLI, the user may specify the source either as an IPv4 address, IPv6 address, or as a routing interface.
When the source is specified as a routing interface, the traceroute is sent using the primary IPv4 address on
the source interface. With SNMP, the source must be specified as an address. The source cannot be specified
in the web UI.
HP Moonshot Switch Module will not accept an incoming packet, such as a traceroute response, that arrives
on a routing interface if the packet’s destination address is on one of the out-of-band management interfaces
(service port or network port). Similarly, HP Moonshot Switch Module will not accept a packet that arrives on
a management interface if the packet’s destination is an address on a routing interface. Thus, it would be futile
to send a traceroute on a management interface using a routing interface address as source, or to send a
traceroute on a routing interface using a management interface as source. When sending a traceroute on a
routing interface, the source must be that routing interface or another routing interface. When sending a
traceroute on a management interface, the source must be on that management interface. For this reason, the
user cannot specify the source as a management interface or management interface address. When sending a
traceroute on a management interface, the user should not specify a source address, but instead let the system
select the source address from the outgoing interface.
Using the options described below, you can specify the initial and maximum time-to-live (TTL) in probe packets,
the maximum number of failures before termination, the number of probes sent for each TTL, and the size of
each probe.
Default • count: 3 probes
• interval: 3 seconds
•size: 0 bytes
• port: 33434
•maxTtl: 30 hops
•maxFail: 5 probes
• initTtl: 1 hop
Format
traceroute {ip-address | [ipv6] {ipv6-address | hostname}} [initTtl initTtl]
[maxTtl maxTtl] [maxFail maxFail] [interval interval] [count count] [port port]
[size size] [source {ip-address | | ipv6-address | unit/slot/port}]
Mode Privileged EXEC