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

Need new test: BGP-Scalability #3609

Closed
kevinskwang opened this issue Jun 4, 2021 · 5 comments
Closed

Need new test: BGP-Scalability #3609

kevinskwang opened this issue Jun 4, 2021 · 5 comments

Comments

@kevinskwang
Copy link
Collaborator

kevinskwang commented Jun 4, 2021

This is a test gap:

Need to add BGP scalability test.

@kamalsahu0001
Copy link
Contributor

Hi Kevin,

Expectation here is to scale BGP sessions as well as the routes?

@yxieca
Copy link
Collaborator

yxieca commented Oct 14, 2021

Definition of scale:

  1. Generate as many EBGPv4 routes (16k) and report DUT limit
  2. Generate 8k ipv6 routes with /64 prefixes.
  3. Generate about 256 routes with prefix greater than /64.
  4. Generate about 8k ipv4 and 4k ipv6 routers in combination
  5. Generate over 100k BGP prefixes(Ipv4) followed by 25k IPv6 prefixes using route injector

Expected DUT behavior:
•DUT should report appropriate notification message when the maximum route limit has been reached.
•DUT should remain responsive to SNMP and to management CLI over console, telnet.
•DUT should continue to forward packets to any subnet that it has a route for A warning Syslog + Console message is expected from the device as it exceeds the limit.

@kamalsahu0001
Copy link
Contributor

Hi @yxieca,

Difference between step 1 and 5? In step 1 we will already hit the limit right. Step 5 is to see even after hitting the 16K limit, how it behaves when we advertise 100K ipv4 prefix and 25K ipv6 prefixes?

@yxieca
Copy link
Collaborator

yxieca commented Nov 8, 2021

@kamalsahu0001 I think step 5 is only step that actually exceeds DUT limit.

@kamalsahu0001
Copy link
Contributor

Keysight will be taking care of this test case. We have the script already defined in BGP convergence test plan. Will add new verification steps to look for the warning messages in console and in syslog. Will raise a separate PR in order to cover these BGP cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

4 participants