zebra: Reset encapsulation source address when no srv6 is executed #19406
Merged
ton31337 merged 2 commits intoFRRouting:masterfrom Aug 14, 2025
Merged
zebra: Reset encapsulation source address when no srv6 is executed #19406ton31337 merged 2 commits intoFRRouting:masterfrom
no srv6 is executed #19406ton31337 merged 2 commits intoFRRouting:masterfrom
Conversation
When the 'no srv6' command is executed, all configurations under the 'srv6' VTY node should be cleared and defaults restored. However, the encapsulation source address is not being reset and remains configured after running 'no srv6'. This commit corrects this behavior by ensuring the encapsulation source address is properly cleared and restored to its default state when 'no srv6' is executed. The following example shows the issue. // Set source address to fcbb:bbbb:1::1 r1# configure r1(config)# segment-routing r1(config-sr)# srv6 r1(config-srv6)# encapsulation r1(config-srv6-encap)# source-address fcbb:bbbb:1::1 r1(config-srv6-encap)# exit r1(config-srv6)# exit r1(config-sr)# exit r1(config)# exit r1# show running-config ... segment-routing srv6 encapsulation source-address fcbb:bbbb:1::1 ... // Execute 'no srv6' r1# configure r1(config)# segment-routing r1(config-sr)# no srv6 r1# show running-config ... segment-routing srv6 encapsulation source-address fcbb:bbbb:1::1 <-- Source address is still configured ... Signed-off-by: Carmine Scarpitta <[email protected]>
Add a test cases to verify the SRv6 encapsulation source address is reset to its default value after running the 'no srv6' command. Signed-off-by: Carmine Scarpitta <[email protected]>
Member
|
@Mergifyio backport stable/10.4 stable/10.3 |
✅ Backports have been createdDetails
|
ton31337
added a commit
that referenced
this pull request
Aug 14, 2025
zebra: Reset encapsulation source address when `no srv6` is executed (backport #19406)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When the
no srv6command is executed, all configurations under thesrv6VTY node should be cleared and defaults restored. However, the encapsulation source address is not being reset and remains configured after runningno srv6.This commit corrects this behavior by ensuring the encapsulation source address is properly cleared and restored to its default state when
no srv6is executed.The following example shows the issue.
Set source address to fcbb:bbbb:1::1 :
Execute 'no srv6' :