Abstract: A disclosed method may include (1) receiving, at a node within a network, an MPLS echo request from an additional node adjacent to the node, (2) determining that a FEC query is included in a FEC stack of the MPLS echo request and then, in response to determining that the FEC query is included in the FEC stack of the MPLS echo request, (3) determining at least one FEC that corresponds to a label included in a label stack of the MPLS echo request, and then (4) notifying the additional node of the FEC that corresponds to the label included in the label stack by sending, to the additional node, an MPLS echo reply that identifies the FEC that corresponds to the label. Various other systems, methods, and computer-readable media are also disclosed.

Abstract: This disclosure describes techniques for using Operations, Administration, and Management (OAM) operations when routing packets using micro SIDs in segment routing. For example, a network device comprises one or more processors configured to: receive a packet; determine whether the packet is encapsulated with one or more micro segment identifiers (SIDs); in response to a determination that the packet is not encapsulated with one or more micro SIDs, determine whether the packet has reached a segment routing tunnel endpoint; and in response to a determination that the packet has reached the segment routing tunnel endpoint, initiate Operations, Administration, and Maintenance (OAM).

Abstract: A label switch router (LSR) in a label-switched path (LSP) may receive, from an ingress edge LSR, a Multi-Protocol Label Switching (MPLS) echo request, where the LSP includes a tunnel having details that are hidden by a Nil Forward Equivalency Class (FEC). The LSR may determine whether the LSR is an egress node for the tunnel in the LSP based at least in part on one or more labels in the MPLS echo request. The LSR may, in response to determining that the LSR is the egress node for the tunnel in the LSP, send an MPLS echo reply that indicates the LSR as being the egress node for the tunnel in the LSP.

Abstract: A disclosed method may include (1) receiving, at a node within a network, an MPLS echo request from an additional node adjacent to the node, (2) determining that a FEC query is included in a FEC stack of the MPLS echo request and then, in response to determining that the FEC query is included in the FEC stack of the MPLS echo request, (3) determining at least one FEC that corresponds to a label included in a label stack of the MPLS echo request, and then (4) notifying the additional node of the FEC that corresponds to the label included in the label stack by sending, to the additional node, an MPLS echo reply that identifies the FEC that corresponds to the label. Various other systems, methods, and computer-readable media are also disclosed.

Abstract: A static label-switched path (LSP) over which packets belonging to a forwarding equivalency class (FEC) are forwarded may be tested by (a) generating a multi-protocol label switching (MPLS) echo request message including a target FEC stack type-length-value (TLV), the target FEC stack TLV having a Nil FEC sub-TLV; and (b) sending the MPLS echo request message with a label stack corresponding to the FEC for forwarding over the static LSP. A static segment routed traffic engineered (SRTE) path, including at least two segments, over which packets belonging to a forwarding equivalency class (FEC) are forwarded, may be tested by (a) generating a multi-protocol label switching (MPLS) echo request message including, for each of the at least two segments, a target FEC stack type-length-value (TLV), each target FEC stack TLV having a Nil FEC sub-TLV; and (b) sending the MPLS echo request message with a label stack corresponding to the FEC for forwarding over the static SRTE path.

Abstract: A device may determine a boot up identifier for the device using information related to a deployment of the device. The boot up identifier may identify the deployment of the device. The device may perform a comparison of the boot up identifier and a provisioned identifier to determine whether the deployment of the device and an intended deployment of the device match. The provisioned identifier may identify the intended deployment of the device. The device may perform a boot up of the device in a particular mode of operation based on a result of the comparison. The comparison may indicate whether the deployment of the device and the intended deployment of the device match. The particular mode of operation may cause the device to boot up to recover or reconfigure the device.

Abstract: A static label-switched path (LSP) over which packets belonging to a forwarding equivalency class (FEC) are forwarded may be tested by (a) generating a multi-protocol label switching (MPLS) echo request message including a target FEC stack type-length-value (TLV), the target FEC stack TLV having a Nil FEC sub-TLV; and (b) sending the MPLS echo request message with a label stack corresponding to the FEC for forwarding over the static LSP. A static segment routed traffic engineered (SRTE) path, including at least two segments, over which packets belonging to a forwarding equivalency class (FEC) are forwarded, may be tested by (a) generating a multi-protocol label switching (MPLS) echo request message including, for each of the at least two segments, a target FEC stack type-length-value (TLV), each target FEC stack TLV having a Nil FEC sub-TLV; and (b) sending the MPLS echo request message with a label stack corresponding to the FEC for forwarding over the static SRTE path.