Skip to content

Adding RT-7.12: BGP Drain using Route Policy #6023

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ASHNA-AGGARWAL-KEYSIGHT wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Adding RT-7.12: BGP Drain using Route Policy #6023

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
fdbc5a0
Adding RT-7.12: BGP Drain using Route Policy
ASHNA-AGGARWAL-KEYSIGHT Sep 11, 2026
6321391
updated test registry
ASHNA-AGGARWAL-KEYSIGHT Sep 11, 2026
f83c4fb
Merge branch 'main' into fpt_otg_RT_7_12
ASHNA-AGGARWAL-KEYSIGHT Sep 11, 2026
b1a1ff3
addressed gemini review comments
ASHNA-AGGARWAL-KEYSIGHT Sep 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions feature/bgp/policybase/otg_tests/bgp_drain_policy_test/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -151,8 +151,7 @@ explicitly covers both IPv4 and IPv6 counterparts.
* Check `/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/afi-safis/afi-safi/state/prefixes/sent`
equals 0 for both IPv4 and IPv6 to ATE port 2.
* Verify if the ATE captures BGP UPDATE (Withdraw) messages for the drained prefixes.
* Step 4 - Validate that both IPv4 and IPv6 continuous traffic streams experience
a drop in Rx rate to 0 (100% loss) at ATE port 2 following the policy application.
* Step 4 - Validate on OTG the prefixes withdraw received from the peer.

### RT-7.12.3 - Remove Policy and Restore Prefix Advertisement

Expand All @@ -179,7 +178,7 @@ explicitly covers both IPv4 and IPv6 counterparts.
* Step 3 - Validate that the DUT withdraws ONLY IPv4 prefixes from the peer:
* Check `/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/afi-safis/afi-safi/state/prefixes/sent`
equals 0 for IPv4 and 10,000 for IPv6 to ATE port 2.
* Step 4 - Validate that the IPv4 continuous traffic stream drops to 0 Rx rate (100% loss), while the IPv6 traffic stream continues with 0% packet loss (Tx == Rx).
* Step 4 - Validate on OTG that the IPv4 withdraw prefixes are received, while the IPv6 traffic remains 0.
* Step 5 - Remove the export policy using gNMI Delete to restore the environment for the next test.

### RT-7.12.5 - Application of Non-Existent Policy
Expand Down
Loading
Loading