Skip to content

[202012] Check if BGP has Loopback0 IP as its router ID (#8576)#9195

Merged
wangxin merged 2 commits intosonic-net:202012from
kellyyeh:router-id-cherrypick-202012
Aug 1, 2023
Merged

[202012] Check if BGP has Loopback0 IP as its router ID (#8576)#9195
wangxin merged 2 commits intosonic-net:202012from
kellyyeh:router-id-cherrypick-202012

Conversation

@kellyyeh
Copy link
Contributor

@kellyyeh kellyyeh commented Jul 31, 2023

Description of PR

This is a cherry-pick PR for #8576 and #9090
Summary: Skip check_bgp_router_id on T2 devices
Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • Test case(new/improvement)

Back port request

  • 201911
  • 202012
  • 202205

Approach

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

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

@kellyyeh kellyyeh requested a review from vaibhavhd July 31, 2023 18:07
@kellyyeh kellyyeh changed the title Check if BGP has Loopback0 IP as its router ID (#8576) [202012]Check if BGP has Loopback0 IP as its router ID (#8576) Aug 1, 2023
@kellyyeh kellyyeh changed the title [202012]Check if BGP has Loopback0 IP as its router ID (#8576) [202012] Check if BGP has Loopback0 IP as its router ID (#8576) Aug 1, 2023
@wangxin wangxin merged commit a1e4e94 into sonic-net:202012 Aug 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants