[cherry-pick] Set VM as reflector for LT2/FT2 (#19238)#466
Merged
bingwang-ms merged 2 commits intoAzure:202503from Jun 30, 2025
Merged
[cherry-pick] Set VM as reflector for LT2/FT2 (#19238)#466bingwang-ms merged 2 commits intoAzure:202503from
bingwang-ms merged 2 commits intoAzure:202503from
Conversation
* Set VM as reflector for LT2/FT2
11 tasks
auspham
previously approved these changes
Jun 30, 2025
yxieca
approved these changes
Jun 30, 2025
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
3 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.
Description of PR
Summary:
This PR is to cherry-pick sonic-net/sonic-mgmt#19238 to 202503 branch.
This PR is to enhance VM template to support route reflector.
In DT2 topologies, the BGP sessions between FT2 and LT2 are IBGP. Hence, the routes learnt from exabgp, which is also IBGP session, are not advertised to DUT.
To workaround this, this PR set VM as route reflector if the VM type is
lowerspineorfabricspine.Type of change
Back port request
Approach
What is the motivation for this PR?
This PR is to support route reflector in VM template.
How did you do it?
Check VM type and enable route reflector if VM type is
lowerspineorfabricspine.How did you verify/test it?
The change is verified on a physical testbed.
Any platform specific information?
No.
Supported testbed topology if it's a new test case?
Not a new test.
Documentation