Managing trace requests over tunneled links
In one embodiment, a head-end node of a tunnel, relative to a tail-end node, receives a trace request, and in response, generates an out-of-tunnel trace request based on the trace-request. The trace request is transmitted in-tunnel to the tail-end node, while also transmitting the out-of-tunnel trace request to at least one subsequent node. The head-end node may then receive a trace response from the tail-end node based on the in-tunnel trace request, as well as a trace response from each of the subsequent nodes based on the out-of-tunnel trace request.
1. A method, comprising:
receiving, at a head-end node of a tunnel relative to a tail-end node, a trace request;
generating, in response to the trace request, an out-of-tunnel trace request based on the trace-request;
transmitting the trace request in-tunnel to the tail-end node;
transmitting the out-of-tunnel trace request to at least one subsequent node;
receiving a trace response from the tail-end node based on the in-tunnel trace request; and
receiving a trace response from each of the subsequent nodes based on the out-of-tunnel trace request.
2. The method of claim 1 , wherein the out-of-tunnel and the in-tunnel trace requests are at least one of a media trace request, or a time to live (TTL)-based trace request.
3. The method of claim 1 , wherein the out-of-tunnel trace response and the in-tunnel trace response comprise one or more performance measurements.
4. The method of claim 1 , wherein the out-of-tunnel trace request causes each subsequent node along a path of the tunnel to i) generate and transmit a respective trace response to the head-end node, and ii) transmit the out-of-tunnel trace request to any additional subsequent node along the path of the tunnel until the out-of-tunnel trace request reaches the tail-end node.
5. The method of claim 1 , wherein the trace response from the tail-end node is an in-tunnel trace response and the trace response from each of the subsequent nodes are out-of-tunnel trace responses, the method further comprising:
aggregating each of the out-of-tunnel trace responses at the head-end node; and
transmitting the in-tunnel trace response and the aggregated out-of-tunnel responses to a trace request originator.
6. The method of claim 1 , wherein the trace response from the tail-end node based on the in-tunnel trace request is an in-tunnel trace response and the trace response from each of the subsequent nodes based on the out-of-tunnel trace request are out-of-tunnel trace responses, the method further comprising:
aggregating the in-tunnel trace response and each of the out-of-tunnel trace responses into a single response at the head-end node; and
transmitting the single response to a trace request originator.
7. The method of claim 1 , wherein the out-of-tunnel trace request is Internet Protocol (IP) routed to the at least one subsequent node.
8. The method of claim 1 , wherein the tunnel is one of a virtual private network (VPN) tunnel, a multiprotocol label switching label switched path (MPLS LSP), a generic route encapsulation (GRE) tunnel, an Internet Protocol Security (IPSec) tunnel, or a layer-2 tunneling protocol (L2TP) tunnel.
9. The method of claim 1 , wherein the head-end node is at least one of a provider edge (PE) device or a customer edge (CE) device.
10. An apparatus, comprising:
one or more network interfaces adapted to communicate in a computer network;
a processor coupled to the network interfaces and adapted to execute one or more processes; and
a memory configured to store a process executable by the processor, the process when executed operable to:
receive, at a head-end node of a tunnel to a tail-end node, a trace request;
generate, in response to the trace request, an out-of-tunnel trace request based on the trace-request;
transmit the trace request in-tunnel to the tail-end node;
transmit the out-of-tunnel trace request to at least one subsequent node;
receive a trace response from the tail-end node based on the in-tunnel trace request; and
receive a trace response from each of the subsequent nodes based on the out-of-tunnel trace request.
11. The apparatus of claim 10 , wherein the out-of-tunnel and the in-tunnel trace requests are at least one of a media trace request, or a time to live (TTL)-based trace request.
12. The apparatus of claim 10 , wherein the out-of-tunnel trace response and the in-tunnel trace response comprise one or more performance measurements.
13. The apparatus of claim 10 , wherein the out-of-tunnel trace request causes each subsequent node along a path of the tunnel to i) generate and transmit a respective trace response to the head-end node, and ii) transmit the out-of-tunnel trace request to any additional subsequent node along the path of the tunnel until the out-of-tunnel trace request reaches the tail-end node.
14. The apparatus of claim 10 , wherein the trace response from the tail-end node based on the in-tunnel trace request is an in-tunnel trace request and the trace response from each of the subsequent nodes based on the out-of-tunnel trace request are out-of-tunnel trace responses, the process when executed is further operable to:
aggregate each of the out-of-tunnel trace responses at the head-end node; and
transmit the in-tunnel trace response and the aggregated out-of-tunnel responses to a trace request originator.
15. The apparatus of claim 10 , wherein the trace response from the tail-end node based on the in-tunnel trace request is an in-tunnel trace response and the trace response from each of the subsequent nodes based on the out-of-tunnel trace request are out-of-tunnel trace responses, the process when executed is further operable to:
aggregate the in-tunnel trace response and each of the out-of-tunnel trace responses into a single response at the head-end node; and
transmit the single response to a trace request originator.
16. The apparatus of claim 10 , wherein the out-of-tunnel trace request is Internet Protocol (IP) routed to at least one subsequent node.
17. The apparatus of claim 10 , wherein the tunnel is one of a virtual private network (VPN) tunnel, a multiprotocol label switching label switched path (MPLS LSP), a generic route encapsulation (GRE) tunnel, an Internet Protocol Security (IPSec) tunnel, or a layer-2 tunneling protocol (L2TP) tunnel.
18. A tangible, non-transitory, computer-readable media having software encoded thereon, the software, when executed by a processor, operable to:
receive, at a head-end node of a tunnel to a tail-end node, a trace request;
generate, in response to the trace request, an out-of-tunnel trace request based on the trace-request;
transmit the trace request in-tunnel to the tail-end node;
transmit the out-of-tunnel trace request to at least one subsequent node;
receive a trace response from the tail-end node based on the in-tunnel trace request; and
receive a trace response from each of the subsequent nodes based on the out-of-tunnel trace request.
19. The computer-readable medium of claim 18 , wherein the out-of-tunnel and the in-tunnel trace requests are at least one of a media trace request, or a time to live (TTL)-based trace request.
20. The computer-readable medium of claim 18 , wherein the trace response from the tail-end node is an in-tunnel trace response and the trace response from each of the subsequent nodes are out-of-tunnel trace responses, the software, when executed, further operable to:
aggregate each of the out-of-tunnel trace responses at the head-end node; and
transmit the in-tunnel trace response and the aggregated out-of-tunnel responses to a trace request originator.