[t0-64 template] avoid deploying conflict routing entries on leaf switch#826
Merged
lguohan merged 1 commit intosonic-net:masterfrom Mar 13, 2019
Merged
[t0-64 template] avoid deploying conflict routing entries on leaf switch#826lguohan merged 1 commit intosonic-net:masterfrom
lguohan merged 1 commit intosonic-net:masterfrom
Conversation
192.168.0.0/21 belongs ot the vlan. Leaf switch should not advertise routes in this segment to carve out IP address ranges from the VLAN. Doing so would cause T1 to VLAN IO validation failure. fast/warm reboot tests depend on the IO validation would also fail. Signed-off-by: Ying Xie <ying.xie@microsoft.com>
lguohan
approved these changes
Mar 13, 2019
yxieca
added a commit
that referenced
this pull request
Mar 18, 2019
…tch (#826) 192.168.0.0/21 belongs ot the vlan. Leaf switch should not advertise routes in this segment to carve out IP address ranges from the VLAN. Doing so would cause T1 to VLAN IO validation failure. fast/warm reboot tests depend on the IO validation would also fail. Signed-off-by: Ying Xie <ying.xie@microsoft.com>
deerao02
pushed a commit
to deerao02/sonic-mgmt
that referenced
this pull request
Dec 18, 2025
<!-- Please make sure you've read and understood our contributing guidelines; https://github.com/sonic-net/SONiC/blob/gh-pages/CONTRIBUTING.md Please provide following information to help code review process a bit easier: --> ### Description of PR <!-- - Please include a summary of the change and which issue is fixed. - Please also include relevant motivation and context. Where should reviewer start? background context? - List any dependencies that are required for this change. --> Summary: Added xfail to condition mark, for test_decap, which failed on IPv6 only topo. xfail for test_decap by sonic-net#20847 ### Type of change <!-- - Fill x for your type of change. - e.g. - [x] Bug fix --> - [ ] Bug fix - [ ] Testbed and Framework(new/improvement) - [ ] New Test case - [ ] Skipped for non-supported platforms - [ ] Test case improvement ### Back port request - [ ] 202205 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 ### Approach #### What is the motivation for this PR? Stable tests on IPv6 only topologies
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
[fwutil]: Use overlay driver when mounting next image filesystem (sonic-net#825) Fix for adding L3 interface to Vlan group (sonic-net#826)Fix for adding L3 interface to Vlan group (sonic-net#826) [db_migrator]Do DB migration for buffer pool size change on Mellanox platform (sonic-net#833) explicitly specify command with underscores (sonic-net#846) [intfutil] set speed to 0 when interface speed is not available (sonic-net#839)
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.
Summary:
Type of change
Approach
How did you do it?
192.168.0.0/21 belongs ot the vlan. Leaf switch should not advertise routes
in this segment to carve out IP address ranges from the VLAN. Doing so would
cause T1 to VLAN IO validation failure. fast/warm reboot tests depend on the
IO validation would also fail.
Signed-off-by: Ying Xie ying.xie@microsoft.com
How did you verify/test it?
warm-reboot on T0-64 topology.