Path-ping and ECMP-traceroute for IPV6 overlay virtualized networks
In one embodiment, an ingress network virtualization edge (NVE) in a computer network generates an echo packet, and sets an indication in the echo packet that the echo packet is for overlay path validation. In addition, the ingress NVE sets a message type of the echo packet to a generic echo request, and includes virtualization network (VN) context information within the echo packet. Once setting a destination address of the echo packet as an egress NVE address and including an indication to the egress NVE that the echo packet is an operations, administration, and management (OAM) message, the ingress NVE may then send the echo packet toward the egress NVE (e.g., to validate the VN context information and/or to reveal multipath traces).
1. A method, comprising:
generating an echo packet by an ingress node in a computer network;
setting an indication in a header of the echo packet that the echo packet is for overlay path validation;
setting, in the header, a message type of the echo packet to a generic echo request;
including, in a payload of the echo packet, context information within the echo packet;
including multipath information within the echo packet to cause each intermediate multipath receiver to reply with a respective flow label and mask for each egress interface of that multipath receiver;
setting, in the header, a destination address of the echo packet as an address of an egress node;
including, in the payload, an indication to the egress node that the echo packet is an operations, administration, and management (OAM) message;
sending the echo packet toward the egress node; and
sending a plurality of echo packets with incrementally increasing hop limits.
2. The method as in claim 1 , wherein sending the echo packet toward the egress node is to cause the egress node to send an echo reply to the ingress node according to validation of the context information.
3. The method as in claim 1 , further comprising:
in response to reaching the egress node with the echo packet, sending one or more additional echo packets toward the egress node on all available multipath paths using a corresponding flow label to cause the egress node to send an echo reply to the ingress node according to validation of the context information for each multipath path.
4. The method as in claim 1 , wherein the multipath information is an IPv6 flow label; a generic route encapsulation (GRE) key; a source user datagram protocol (UDP) port; or a combination thereof.
5. The method as in claim 4 , wherein the multipath information comprises a bit-mask.
6. The method as in claim 1 , wherein the indication to the egress node that the echo packet is an OAM message comprises a specific user datagram protocol (UDP) port and destination port.
7. The method as in claim 1 , wherein the indication to the egress node that the echo packet is an OAM message comprises an explicit indication.
8. The method as in claim 7 , wherein the explicit indication comprises an OAM-option destination header option with a particular flag set.
9. The method as in claim 1 , wherein the context information is in relation to IP-based overlay networks and comprises a context identifier (ID) and associated context details.
10. The method as in claim 1 , wherein the context information is included within a type-length-value (TLV) field of the echo packet.
11. The method as in claim 1 , wherein the indication in the echo packet that the echo packet is for overlay path validation comprises a particular flag set within a global flags field of the echo packet.
12. An apparatus, comprising:
one or more network interfaces to communicate as an ingress node in a computer network;
a processor coupled to the network interfaces and configured to execute one or more processes; and
a memory configured to store a process executable by the processor, the process when executed operable to:
generate an echo packet;
set an indication in a header of the echo packet that the echo packet is for overlay path validation;
set, in the header, a message type of the echo packet to a generic echo request;
include, in a payload of the echo packet, context information within the echo packet;
include multipath information within the echo packet to cause each intermediate multipath receiver to reply with a respective flow label and mask for each egress interface of that multipath receiver;
set, in the header, a destination address of the echo packet as an address of an egress node;
including, in the payload, an indication to the egress node that the echo packet is an operations, administration, and management (OAM) message;
send the echo packet toward the egress node; and
send a plurality of echo packets toward the egress node with incrementally increasing hop limits.
13. The apparatus as in claim 12 , wherein sending the echo packet toward the egress node is to cause the egress node to send an echo reply to the ingress node according to validation of the context information.
14. The apparatus as in claim 12 , wherein the process when executed is further operable to:
in response to reaching the egress node with the echo packet, send one or more additional echo packets toward the egress node on all available multipath paths using a corresponding flow label to cause the egress node to send an echo reply to the ingress node according to validation of the context information for each multipath path.
15. The apparatus as in claim 12 , wherein the multipath information is an IPv6 flow label; a generic route encapsulation (GRE) key; a source user datagram protocol (UDP) port or a combination thereof.
16. The apparatus as in claim 12 , wherein the indication to the egress node that the echo packet is an OAM message comprises one of either a specific user datagram protocol (UDP) port and destination port or an explicit indication.
17. The apparatus as in claim 12 , wherein the context information is in relation to IP-based overlay networks and comprises a context identifier (ID) and associated context details.
18. A tangible, non-transitory, computer-readable media having software encoded thereon, the software, when executed by a processor on an ingress node in a computer network, operable to:
generate an echo packet;
set an indication in a header of the echo packet that the echo packet is for overlay path validation;
set, in the header, a message type of the echo packet to a generic echo request;
include, in a payload of the echo packet, context information within the echo packet;
include multipath information within the echo packet to cause each intermediate multipath receiver to reply with a respective flow label and mask for each egress interface of that multipath receiver;
set, in the header, a destination address of the echo packet as an address of an egress node;
including, in the payload, an indication to the egress node that the echo packet is an operations, administration, and management (OAM) message;
send the echo packet toward the egress node; and
send a plurality of echo packets toward the egress node with incrementally increasing hop limits.