Skip to content
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.

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

[dualtor] Adding test for multiple nexthop routes #7600

Closed
wants to merge 1 commit into from

Conversation

Ndancejic
Copy link
Contributor

What I did: added tests/dualtor/test_multi_mux_nexthop_route.py which tests use case of multiple nexthop neighbors across different MUX ports.

DEPENDS ON: sonic-net/sonic-swss#2656

Why I did it: test coverage of this scenario

How I did it: test creates route to 2 different interfaces and neighbors, then validates that traffic is recieved from the expected ports.

  • 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?

What I did: added tests/dualtor/test_multi_mux_nexthop_route.py which tests use case of multiple nexthop neighbors across different MUX ports.

DEPENDS ON: sonic-net/sonic-swss#2656

How did you do it?

Why I did it: test coverage of this scenario

How did you verify/test it?

How I did it: test creates route to 2 different interfaces and neighbors, then validates that traffic is recieved from the expected ports.

Any platform specific information?

none

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

dualtor

Documentation

sonic-net/SONiC#1256

What I did: added tests/dualtor/test_multi_mux_nexthop_route.py which
tests use case of multiple nexthop neighbors across different MUX ports.

DEPENDS ON: sonic-net/sonic-swss#2656

Why I did it: test coverage of this scenario

How I did it: test creates route to 2 different interfaces and
neighbors, then validates that traffic is recieved from the expected
ports.
@Ndancejic Ndancejic closed this May 2, 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.

1 participant