Abstract: Techniques are described for detecting and correcting mis-programming of label information in a router of a label switched path (LSP) without initially triggering a tear-down of the LSP. For example, techniques described in this disclosure enable an ingress router to determine whether label information is correctly programmed between a routing engine (e.g., control plane) and a forwarding engine (e.g., forwarding plane) of a router in the LSP, and to correct any mis-programming of label information by informing the router to reprogram the forwarding engine with original forwarding label information associated with the LSP.

Abstract: A device may receive information that identifies a bandwidth value of a label-switched path (LSP) that includes a protected link or a protected node. The device may determine a bypass LSP bandwidth threshold based on the bandwidth value. The device may determine a set of path bandwidth values associated with a set of paths. The device may compare the set of path bandwidth values and the bypass LSP bandwidth threshold. The device may select a path, of the set of paths, based on comparing the set of path bandwidth values and the bypass LSP bandwidth threshold. The device may generate a bypass LSP using the path.

Abstract: The techniques described herein may reduce global repairs in Multiprotocol Label Switching (MPLS) Label-Switched Paths (LSPs) by using an aggregated link bundle as a primary path when multiple paths are available. As an example, a router may determine a respective interface type for each path of a plurality of paths; determine, based on the respective interface types, whether one or more paths from the plurality of paths satisfies a set of constraints that are configured such that an aggregated link bundle interface type is preferred over a single link interface type; determine a preferred path based on whether the set of constraints were satisfied; configure a routing table of the router with the preferred path as a LSP to the destination; and send, based on the routing table, one or more packets using an interface of the router associated with the LSP.

Abstract: Techniques are described for reusing downstream-assigned labels when establishing a new label switched path (LSP) between an ingress router and an egress router prior to tearing down an existing LSP using make-before-break (MBB) procedures for the Resource Reservation Protocol (RSVP). In one example, a router receives, a first message requesting establishment of an LSP including a tunnel identifier pair. The router compares the tunnel identifier pair for the requested LSP to existing LSP information stored at the router. Based on a determination that the tunnel identifier pair for the requested LSP is the same as a tunnel identifier pair for an existing LSP, the router assigns a label used by the router to identify incoming traffic associated with the requested LSP that is the same as a previously allocated label for the existing LSP without updating labels in a forwarding table of a forwarding plane of the router.

Abstract: Techniques are described for detecting and correcting mis-programming of label information in a router of a label switched path (LSP) without initially triggering a tear-down of the LSP. For example, techniques described in this disclosure enable an ingress router to determine whether label information is correctly programmed between a routing engine (e.g., control plane) and a forwarding engine (e.g., forwarding plane) of a router in the LSP, and to correct any mis-programming of label information by informing the router to reprogram the forwarding engine with original forwarding label information associated with the LSP.