Skip to content

[bgp]: Fix BGP aggregate-address placeholder prefix rejected by FRR#24655

Open
Guoyuan001 wants to merge 2 commits into
sonic-net:masterfrom
Guoyuan001:fixholder
Open

[bgp]: Fix BGP aggregate-address placeholder prefix rejected by FRR#24655
Guoyuan001 wants to merge 2 commits into
sonic-net:masterfrom
Guoyuan001:fixholder

Conversation

@Guoyuan001
Copy link
Copy Markdown
Contributor

@Guoyuan001 Guoyuan001 commented May 15, 2026

Description of PR

Summary:
Fixes # (issue)
The PLACEHOLDER_PREFIX used by the BGP aggregate-address tests was
defined as a host route 192.0.2.0/32. FRR rejects aggregate-address entries
whose prefix length is too specific

image

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • New Test case
    • Skipped for non-supported platforms
  • Test case improvement

Back port request

  • 202205
  • 202305
  • 202311
  • 202405
  • 202411
  • 202505
  • 202511
  • 202603

Approach

What is the motivation for this PR?

Unblock tests/bgp/test_bgp_aggregate_address.py and
tests/bgp/test_bgp_aggregate_address_scale_stress.py, which were failing at
configuration time because FRR refused the /32 placeholder aggregate prefix.

How did you do it?

Changed PLACEHOLDER_PREFIX in tests/bgp/bgp_aggregate_helpers.py from
192.0.2.0/32 to 192.0.2.0/24 (still inside the RFC 5737 TEST-NET-1
documentation block, so it cannot collide with real routing) and added a
comment explaining the FRR constraint.

  • Removed the duplicated local PLACEHOLDER_PREFIX definitions in
    test_bgp_aggregate_address.py and test_bgp_aggregate_address_scale_stress.py
    and imported the single source of truth from bgp_aggregate_helpers.

How did you verify/test it?

Test it on DUT
image

Any platform specific information?

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

Documentation

Signed-off-by: Guoqiang Yuan <guoyuan@microsoft.com>
@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@github-actions github-actions Bot requested review from cyw233, lolyu and sanjair-git May 15, 2026 08:40
@Guoyuan001 Guoyuan001 closed this May 15, 2026
Signed-off-by: Guoqiang Yuan <guoyuan@microsoft.com>
@Guoyuan001 Guoyuan001 reopened this May 15, 2026
@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

1 similar comment
@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

1 similar comment
@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

Comment on lines +97 to +98
r".* ERR iptables: tac_connect_single: connection to .* failed: "
r"Network is unreachable.*",
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.

4 participants