Documentation

pingnoderouteindex

Name

net node record-route -  trace the route from one router to a specific destination

Synopsis

record-route [--capacity] [--check-loop] [--deflection] [--delay] [--ecmp] [--load=] [--tos=] [--tunnel] [--weight] <address|prefix> 

Arguments

--capacity
optionally report the path's capacity
--check-loop
optionally check for forwarding loops
--deflection
optionnaly check for path deflection
--delay
optionnaly report the path's delay
--ecmp
optionally discover ECMP paths
--load=
optionally load the path with a traffic load
--tos=
optionally use a different forwarding plane
--tunnel
optionally discover the path within tunnels
--weight
optionally report the path's IGP weight
address|prefix
destination address or prefix

Description

This command records the addresses of the nodes that packet sent from the source address traverse to reach the destination address. The destination may be an IP address or an IP prefix. In the case of an IP address, the trace stops only when a node with the specified address is reached. In the case of an IP prefix, the trace stops as soon as a node with an IP address that matches the specified prefix is reached.

Output format: <source> <destination> <result> <num-hops> <list of hops> [options]

The value of result is one of

SUCCESS
The destination was reachable. In this case, the list of hops is the list of the IP adresses of the traversed nodes.
UNREACH
The destination was not reachable. In this case, the list of hops is the list of IP addresses of the nodes traversed until no route was available.
TOO_LONG
The path towards the destination was too long (i.e. longer than 30 hops). This is often the symptom of a routing loop.
DOWN
there was a route to reach the destination, but a link down was found on the way. This indicates a misconfiguration or routing error. This can however occur in transient states, after a link has been brought down and the routing has not reconverged. The last node in the list of hops indicates the node adjacent to the failing link.
LOOP
If the option --check-loop has been specified and a forwarding loop is found, then this status is reported.
TUNNEL_UNREACH
The path went through a tunnel but the tunnel end-point does not support the IP-in-IP protocol. Consider using the net node ipip-enable. The last node in the list of hops is the address of the faulty node.
TUNNEL_BROKEN
The path went through a tunnel but at a point the tunnel end-point was not reachable. The last node in the list of hops is the address of the faulty node.

Example: cbgp> net node 1.0.0.1 record-route 1.0.0.2
1.0.0.1 1.0.0.2 SUCCESS 3 1.0.0.1 1.0.0.3 1.0.0.2
cbgp>

Here is another example that traces all the equal-cost paths (ECMP) between two nodes: cbgp> net node 1.0.0.0 record-route --ecmp 1.0.0.4
1.0.0.0 1.0.0.4 SUCCESS 4 1.0.0.0 1.0.0.1 1.0.0.3 1.0.0.4
1.0.0.0 1.0.0.4 SUCCESS 4 1.0.0.0 1.0.0.1 1.0.0.3 1.0.0.4
cbgp>

See also

See also commands ping and traceroute for alternative ways to check the reachability of nodes.

Known bugs

IMPORTANT NOTE: due to changes in the network topology data structure and in the way tunnels are handled, the tunnel tracing feature is currently broken. Tracing route through tunnels is therefore temporarily disabled.