-
Notifications
You must be signed in to change notification settings - Fork 690
Add explicit bypass tunnel assignment to RSVP-TE interface protection #1413
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
KyoyaTeramae
wants to merge
6
commits into
openconfig:master
Choose a base branch
from
KyoyaTeramae:Add-explicit-bypass-tunnel-assignment-to-RSVP-TE-interface-protection
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
earies
reviewed
Dec 10, 2025
Member
|
/gcbrun |
|
No major YANG version changes in commit 3998c51 |
…SVP-TE-interface-protection
…SVP-TE-interface-protection
…SVP-TE-interface-protection
dplore
reviewed
Dec 23, 2025
Member
|
/gcbrun |
Member
|
/gcbrun |
dplore
approved these changes
Jan 5, 2026
Member
dplore
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. To be reviewed at next OC Operators meeting.
Contributor
|
Discussed in the OC Operators Meeting Jan 6th 2026: Seems reasonable; no objections raised. Setting this last-call to 2 weeks from now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Scope
* This PR enhances to support an RSVP-TE Fast Reroute (FRR) capability by introducing a mechanism to explicitly assign pre-configured LSPs as bypass tunnels. This is a common requirement for service providers who want deterministic failover paths for protected interfaces. When an interface running RSVP-TE with FRR enabled fails, traffic can be redirected onto specified bypass LSPs, which have their own explicit paths.
To support this, the following changes are made:
1. A new
leaf-listnamedbypass-tunnelis added to the RSVP interface protection configuration (openconfig-mpls-rsvp.yang). This allows one or more pre-configured TE tunnels to be designated as bypass LSPs.2. To differentiate these bypass LSPs from regular LSPs, a new
BYPASS_P2Pidentity is introduced under theTUNNEL_TYPEbase (openconfig-mpls-types.yang).3. The
descriptionfor the tunneltypeleaf has been updated accordingly (openconfig-mpls-te.yang).* This change is backwards compatible as it only introduces new optional data nodes and a new identity.
Platform Implementations
* Cisco IOS-XR: The
backup-pathcommand under the protected interface allows specifying one or more tunnel interfaces to act as bypass LSPs. This directly corresponds to the proposedbypass-tunnelleaf-list.https://www.cisco.com/c/en/us/td/docs/iosxr/cisco8000/mpls/command/reference/b-mpls-cr-8k/b-mpls-te-commands.html#:~:text=backup%2Dbw-,backup%2Dpath%20tunnel%2Dte,-bandwidth%2Daccounting
* Drivenets DNOS: The
bypass-tunnelcommand underprotocols rsvp interface <interface-name> protectionis used to assign bypass LSPs. The bypass tunnel itself is also explicitly configured withbypassdifferentiated from a regular tunnel. This implicitly requires the proposedBYASS_P2Ptunnel type.* Nokia SR OS: The
bypass-onlycommand option for the configure router mpls lsp context explicitly defines the LSP as a dedicated manual configured bypass tunnel. This creates an exclusive LSP type that is differentiated from carrying regular service traffic, directly supporting the proposed BYPASS_P2P identity. When a manual path (ERO) is applied to this LSP type, it functions as a deterministic bypass tunnel.https://documentation.nokia.com/sr/24-7/7x50-shared/mpls/mpls-rsvp.html#ai9emdyo7f
Tree View
* The following diff shows the addition of the
bypass-tunnelleaf-list to the RSVP-TE interface protection configuration.module: openconfig-mpls +--rw network-instances +--rw network-instance* [name] +--rw mpls +--rw signaling-protocols +--rw rsvp-te +--rw interface-attributes +--rw interface* [interface-id] +--rw protection +--rw config +--rw link-protection-style-requested? identityref +--rw bypass-optimize-interval? uint16 + +--rw bypass-tunnel* -> ../../../../../../../lsps/constrained-path/tunnels/tunnel/name