Providing a message associated with a performance issue of a transit node that is associated with a label switched path
In some implementations, a transit node associated with a label switched path (LSP), may identify a performance issue of the transit node. The transit node may generate, based on identifying the performance issue, a message associated with the performance issue. The transit node may send, to an ingress node associated with the LSP, the message to allow the ingress node to perform one or more actions associated with the LSP. The one or more actions associated with the LSP may include performance of an assessment operation associated with the LSP and/or initiation of a termination operation associated with the LSP.
1 . A method, comprising:
identifying, by a transit node associated with a label switched path (LSP) and based on monitoring telemetry data associated with the transit node, one or more trap codes or one or more exception codes associated with the transit node;
identifying, by the transit node and based on analyzing the one or more trap codes or the one or more exception codes, a performance issue of the transit node;
generating, by the transit node and based on identifying the performance issue, a first message that is a first copy of a message associated with the performance issue;
transmitting, by the transit node, and to an ingress node associated with the LSP, the first message to allow the ingress node to perform one or more actions associated with the LSP, wherein the one or more actions include:
causing, based on transmitting the first message, initiation of a termination operation associated with the LSP;
transmitting, by the transit node and to another ingress node associated with another LSP that includes the transit node, a second message, wherein the second message is a second copy of the message; and
causing, based on transmitting the second message, the other ingress node to perform one or more other actions associated with the other LSP.
2 . The method of claim 1 , wherein transmitting the first message allows the ingress node to perform an assessment operation associated with the LSP.
3 . The method of claim 1 , further comprising: receiving, based on transmitting the first message, one or more messages associated with an assessment operation that is associated with the LSP.
4 . The method of claim 1 , further comprising: receiving, based on transmitting the first message, one or more messages associated with the termination operation.
5 . The method of claim 1 , wherein transmitting the second message allows the other ingress node to perform an assessment operation associated with the other LSP.
6 . The method of claim 1 , further comprising: receiving, based on transmitting the second message, one or more messages associated with an assessment operation that is associated with the other LSP.
7 . The method of claim 1 , further comprising: receiving, based on transmitting the second message, one or more messages associated with another termination operation that is associated with the other LSP.
8 . The method of claim 1 , wherein the one or more actions or the one or more other actions include at least one of:
an LSP self-ping operation,
an LSP ping operation, or
another assessment operation configured to assess an LSP status.
9 . The method of claim 1 , wherein the message is in an extended format of a resource reservation protocol (RSVP) path error message to support an error specification object.
10 . An ingress node associated with a label switched path (LSP), comprising:
one or more memories; and
one or more processors to:
receive, from a transit node associated with the LSP, a first message that is a first copy of a message associated with a performance issue of the transit node, wherein the performance issue is identified by the transit node based on analyzing one or more trap codes or one or more exception codes associated with the transit node;
cause, based on the first message, initiation of a termination operation associated with the LSP,
wherein a second message that is a copy of the message is sent to another ingress node that is associated with another LSP that includes the transit node; and
perform, based on the message, one or more actions associated with the LSP.
11 . The ingress node of claim 10 , wherein the one or more processors, to perform the one or more actions associated with the LSP, are to:
perform, based on the message, an assessment operation associated with the LSP.
12 . The ingress node of claim 10 , wherein the one or more processors, to perform the one or more actions associated with the LSP, are to:
transmit, based on the message, one or more messages associated with an assessment operation that is associated with the LSP,
wherein the one or more messages are transmitted, via the LSP, to the transit node.
13 . The ingress node of claim 10 , wherein the one or more processors, to perform the one or more actions associated with the LSP, are to:
transmit one or more messages associated with the termination operation,
wherein the one or more messages are propagated to the transit node via the LSP.
14 . The ingress node of claim 10 , wherein the message is in an extended format of a resource reservation protocol (RSVP) path error message to support an error specification object.
15 . A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:
one or more instructions that, when executed by one or more processors of a transit node associated with a label switched path (LSP), cause the transit node to:
identify, based on monitoring telemetry data associated with the transit node, one or more trap codes or one or more exception codes associated with the transit node;
identify, based on analyzing the one or more trap codes or the one or more exception codes, a performance issue of the transit node;
generate, based on identifying the performance issue, a first message that is a copy of a message associated with the performance issue;
transmit, to an ingress node associated with the LSP, the first message to allow the ingress node to perform one or more actions associated with the LSP, wherein the one or more actions include:
causing, based on transmitting the first message, initiation of a termination operation associated with the LSP;
transmit, by the transit node and to another ingress node associated with another LSP that includes the transit node, a second message,
wherein the second message is a second copy of the message; and
cause, based on transmitting the second message, the other ingress node to perform one or more other actions associated with the other LSP.
16 . The non-transitory computer-readable medium of claim 15 , wherein the one or more actions include an assessment operation that is an LSP self-ping assessment operation or an LSP ping assessment operation.
17 . The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, when executed by the one or more processors, further cause the transit node to:
receive, based on transmitting the message, one or more messages associated with an assessment operation that is associated with the LSP.
18 . The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, when executed by the one or more processors, further cause the transit node to:
receive, based on transmitting the message, one or more messages associated with the termination operation that is associated with the LSP.
19 . The non-transitory computer-readable medium of claim 15 , wherein the message is in an extended format of a resource reservation protocol (RSVP) path error message to support an error specification object.
20 . The non-transitory computer-readable medium of claim 19 , wherein the message includes instructions to perform at least one of the one or more actions or the one or more other actions.