Initiator-based data-plane validation for segment routed, multiprotocol label switched (MPLS) networks
Techniques for initiator-based data-plane validation of segment routed, multiprotocol label switched (MPLS) networks are described herein. In examples, an initiating node may determine to validate data-plane connectivity associated with a network path of the MPLS network. The initiating node may store validation data in a local memory of the initiating node. In examples, the initiating node may send a probe message that includes a request for identification data associated with a terminating node. The terminating node may send a probe reply message that includes the identification data, as well as, in some examples, a code that instructs the initiating node to perform validation. In examples, the initiating node may use the validation data stored in memory to compare to the identification data received from the terminating node to validate data-plane connectivity. In some examples, the initiating node may indicate a positive or negative response after performing the validation.
1. A method comprising:
determining, at a sender node, to validate connectivity in a network path of a multi-protocol label switched (MPLS) network, wherein the network path is associated with a first terminating node and a second terminating node;
generating an MPLS Echo Request message to validate the connectivity in the network path;
populating the MPLS Echo Request message with a Type-Length-Value (TLV) that indicates a prefix of the first terminating node;
sending, from the sender node, the MPLS Echo Request message via the network path;
receiving a response message including identification data associated with the first terminating node, the identification data comprising first data indicating that the MPLS Echo Request message terminated at the first terminating node; and
determining, using the identification data, that the connectivity in the network path is valid.
2. The method of claim 1 , wherein the TLV further indicates that the first terminating node is an egress node.
3. The method of claim 1 , further comprising:
storing, in a local database, validation data including one or more associations between network paths and respective terminating nodes of the MPLS network; and
determining, at the sending node and using the validation data stored in the local database, that the connectivity in the network path is valid.
4. The method of claim 3 , further comprising:
sending, to a path computation element (PCE) of the MPLS network, a path query indicating a request to receive the validation data;
receiving, from the PCE, the validation data; and
wherein storing the validation data in the local database of the sending node is based at least in part on the determining to validate the connectivity in the network path.
5. The method of claim 4 , wherein storing the validation data in the local database of the sending node further comprises storing the validation data for a period of time, the period of time corresponding to an amount of time associated with a lifecycle of the MPLS Echo Request message.
6. The method of claim 1 ,
wherein the identification data further comprises
second data indicating an incoming-interface link associated with the first terminating node.
7. A sending node comprising:
one or more processors; and
one or more non-transitory computer-readable media storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
determining to validate connectivity in a network path of a multi-protocol label switched (MPLS) network, wherein the network path is associated with a first terminating node and a second terminating node;
generating an MPLS Echo Request message to validate the connectivity in the network path;
populating the MPLS Echo Request message with a Type-Length-Value (TLV) that indicates a prefix of the first terminating node;
sending the MPLS Echo Request message via the network path;
receiving a response message including identification data associated with the first terminating node, the identification data comprising first data indicating that the MPLS Echo Request message terminated at the first terminating node; and
determining, using the identification data, that the connectivity in the network path is valid.
8. The sending node of claim 7 , wherein the TLV further indicates that the first terminating node is an egress node.
9. The sending node of claim 7 , the operations further comprising:
storing, in a local database, validation data including one or more associations between network paths and respective terminating nodes of the MPLS network; and
determining, using the validation data stored in the local database, that the connectivity in the network path is valid.
10. The sending node of claim 9 , the operations further comprising further comprising:
sending, to a path computation element (PCE) of the MPLS network, a path query indicating a request to receive the validation data; and
receiving, from the PCE, the validation data;
wherein storing the validation data in the local database of the sending node is based at least in part on the determining to validate the connectivity in the network path.
11. The sending node of claim 10 , wherein storing the validation data in the local database of the sending node further comprises storing the validation data for a period of time, the period of time corresponding to an amount of time associated with a lifecycle of the MPLS Echo Request message.
12. The sending node of claim 7 ,
wherein the identification data further comprises
second data indicating an incoming-interface link associated with the first terminating node.
13. One or more non-transitory computer-readable media storing processor-executable instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:
determining, at a sending node, to validate connectivity in a network path of a multi-protocol label switched (MPLS) network, wherein the network path is associated with a first terminating node and a second terminating node;
generating, at the sending node, an MPLS Echo Request message to validate the connectivity in the network path;
populating, at the sending node, the MPLS Echo Request message with a Type-Length-Value (TLV) that indicates a prefix of the first terminating node;
sending, from the sending node, the MPLS Echo Request message via the network path;
receiving a response message including identification data associated with the first terminating node, the identification data comprising first data indicating that the MPLS Echo Request message terminated at the first terminating node; and
determining, using the identification data, that the connectivity in the network path is valid.
14. The one or more non-transitory computer-readable media of claim 13 , wherein the TLV further indicates that the first terminating node is an egress node.
15. The one or more non-transitory computer-readable media of claim 13 , the operations further comprising:
storing, in a local database, validation data including one or more associations between network paths and respective terminating nodes of the MPLS network; and
determining, using the validation data stored in the local database, that the connectivity in the network path is valid.
16. The one or more non-transitory computer-readable media of claim 15 , the operations further comprising:
sending, to a path computation element (PCE) of the MPLS network, a path query indicating a request to receive the validation data; and
receiving, from the PCE, the validation data;
wherein storing the validation data in the local database of the sending node is based at least in part on the determining to validate the connectivity in the network path.
17. The one or more non-transitory computer-readable media of claim 16 , wherein storing the validation data in the local database of the sending node further comprises storing the validation data for a period of time, the period of time corresponding to an amount of time associated with a lifecycle of the MPLS Echo Request message.