[action] [PR:18766] [DualToR] enforce same loopback ip and drop bgp pkts on loopback1 for dualtor#18912
Merged
mssonicbld merged 1 commit intosonic-net:202505from Jun 13, 2025
Conversation
11 tasks
Collaborator
Author
|
Original PR: #18766 |
Collaborator
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
… dualtor (sonic-net#18766) What is the motivation for this PR? This PR updates the DualToR config to enforce the same loopback1 IP address for both ToRs. Based on a recent Incident 628608070 : [SONiC RCA][SLB_DNC] Gemini Tors dropping vip traffic, we need to block BGP from being established on loopback1. How did you do it? Assign the same loopback1 IP to both ToRs. Added an iptables rules to drop the packets sonic-net/sonic-host-services#262 How did you verify/test it? Confirmed both ToRs used the same loopback1 IP, and verify the drop rule.
mssonicbld
force-pushed
the
cherry/202505/18766
branch
from
7162732 to
69cc36d
Compare
Collaborator
Author
|
Original PR: #18766 |
Collaborator
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
/azp run |
|
Commenter does not have sufficient privileges for PR 18912 in repo sonic-net/sonic-mgmt |
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.
Description of PR
Summary:
Fixes # (issue)
https://msazure.visualstudio.com/One/_workitems/edit/32910131/
Type of change
Back port request
Approach
What is the motivation for this PR?
This PR updates the DualToR config to enforce the same loopback1 IP address for both ToRs.
Based on a recent Incident 628608070 : [SONiC RCA][SLB_DNC] Gemini Tors dropping vip traffic, we need to block BGP from being established on loopback1.
How did you do it?
Assign the same loopback1 IP to both ToRs.
Added an iptables rules to drop the packets sonic-net/sonic-host-services#262
How did you verify/test it?
Confirmed both ToRs used the same loopback1 IP, and verify the drop rule.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation