Skip check_bgp_router_id on T2 devices#9090
Conversation
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
|
@kellyyeh PR conflicts with 202205 branch |
|
@kellyyeh PR conflicts with 202012 branch |
|
@kellyyeh could you open cherrypick PR on 202205 branch? w/o this it is failing chassis single asic card sanity check |
This is a cherry-pick PR for #8576 and #9090 * Check if BGP has Loopback0 IP as its router ID (#8576) * Skip check_bgp_router_id on T2 devices (#9090) What is the motivation for this PR? An issue was found that T0 did not announce Loopback to T1, this check is to bridge the test gap to ensure bgp router identifier matches Loopback0 IP. How did you do it? Added in sanity_check to match bgp router id and loopback0 ip How did you verify/test it? Ran a advanced_reboot manually and checked expected log: BGP router identifier: https://elastictest.org/scheduler/testplan/649c780c75768730ce0de9f3
Description of PR
Summary: Skip check_bgp_router_id on T2 devices
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
In chassis the a different Loopback ip is used as bgp router_id
How did you do it?
Skip check_bgp_router_id on t2 topo
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation