Add testplan for BGP MED (Multi-Exit Discriminator) feature#8
Open
bpar9 wants to merge 1 commit into
Open
Conversation
- 22 comprehensive test cases covering MED functionality - Default MED value, route-map configuration (inbound/outbound) - Best path selection based on MED (same AS and cross-AS) - always-compare-med and deterministic-med options - MED interaction with local-preference and AS-path - IPv6 support, boundary values, persistence after restart - Route reflector scenarios - Route flapping stability
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
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
1 participant
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 adds a comprehensive test plan document for validating the BGP MED (Multi-Exit Discriminator) feature in SONiC. MED is an optional non-transitive BGP path attribute used to influence inbound traffic routing decisions from external ASes, where lower values are preferred.
Reviewer start point: Review the test plan document for technical accuracy and completeness of test coverage.
Files added:
docs/testplan/BGP-MED-Test-Plan.md- Test plan documenting 22 test casesLink to Devin run: https://cisco-demo.devinenterprise.com/sessions/71c0f42835ce4a9586a92d30b6615c2c
Requested by: @bpar9
Type of change
Back port request
Approach
What is the motivation for this PR?
To provide a detailed test plan for automated validation of the BGP MED feature, covering MED configuration via route-maps, best path selection based on MED values, and proper behavior with eBGP/iBGP peers.
How did you do it?
Created a test plan document with 22 detailed test cases covering:
always-compare-medanddeterministic-medoptionsHow did you verify/test it?
This is a test plan document only. Test implementation (
tests/bgp/test_bgp_med.py) is not included in this PR.Any platform specific information?
None - tests will use vtysh for route-map configuration which is platform-agnostic.
Supported testbed topology if it's a new test case?
Documentation
Test plan document added at
docs/testplan/BGP-MED-Test-Plan.mdItems for reviewer attention: