[bgp] Update timer test to use correct neighbor type#3109
Merged
prsunny merged 1 commit intosonic-net:masterfrom Mar 9, 2021
Merged
[bgp] Update timer test to use correct neighbor type#3109prsunny merged 1 commit intosonic-net:masterfrom
prsunny merged 1 commit intosonic-net:masterfrom
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
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:
Fixes # sonic-net/sonic-buildimage#6921
Type of change
Approach
What is the motivation for this PR?
Bgp update timer test establishes two bgp peering session with pseudoswitch. This neighbor type is
ToRRouterfor all dut types.Fix is to configure the neighbor based on the dut type
How did you do it?
How did you verify/test it?
Run the test on both T0 and T1 topology
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation