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

[test] Add lacp fallback test cases #379

Closed
wants to merge 0 commits into from

Conversation

hzheng5
Copy link
Contributor

@hzheng5 hzheng5 commented Dec 7, 2017

  • Run lag_minlink test cases only if min_ports is configured
  • Run lag_fallback test cases if fallback is configure. The lag_fallback test cases flap the link from VM side while keeping the physical link up, this is to simulate the situation where the remote end stops sending LACP DU. If fallback is enabled, the port should still be selected, and LAG should be kept up. Otherwise, the member port should be unselected, and LAG should be brought down.

Please note min_port and fallback configure are mutual exclusive
for each lag.

Depends on sonic-net/sonic-buildimage#1118

Signed-off-by: Haiyang Zheng haiyang.z@alibaba-inc.com

Description of PR

Fixes # (issue)

Type of change

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

Approach

How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?

Documentation

@hzheng5
Copy link
Contributor Author

hzheng5 commented Dec 7, 2017

@rodnymolina Could you please help review the test plan?

Thanks,
Haiyang

@lguohan
Copy link
Contributor

lguohan commented Dec 8, 2017

can you add to REAME.test.md for how to run the test?

@hzheng5
Copy link
Contributor Author

hzheng5 commented Dec 8, 2017

@lguohan Thanks for the reminder. Just added the instruction to REAME.test.md.

This test case will run as part of the LAG-2 test cases on t0 topo.

Thanks,
Haiyang

@pavel-shirshov
Copy link
Contributor

Can you please resolve the conflict?

@@ -116,6 +116,9 @@
<PortChannel>
<Name>PortChannel{{ ((index+1)|string).zfill(4) }}</Name>
<AttachTo>{{ port_alias[28+index] }}</AttachTo>
{% if index%2 %}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fallback is enabled only when we have odd index?
Can you please comment what is this like do?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes. only enable fallback on odd ports here, so we can compare the status between odd ports and even ports to make sure both are in expected state.

Thanks for the suggestion. Will add some comment here.

@@ -83,6 +83,13 @@ ansible-playbook test_sonic.yml -i inventory --limit {DUT_NAME} --tags lag-2 --e
```
- Requires switch connected to a VM testbed with lag configured (t0, t1-lag)

### Lag-fallback test
```
ansible-playbook test_sonic.yml -i inventory --limit {DUT_NAME} --tags lag-2 --extra-vars "testbed_type={TESTBED_TYPE} ptf_host={PTF_HOST}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to convert your test into new format
ansible-playbook test_sonic.yml -i str --limit str-s6100-acs-1 --vault-password-file password.txt -e testcase_name=lag-2 -e testbed_name=vms3-t0-s6100

Please check how the recently added tests are executed. Please let me know if you have questions.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure. Thanks @pavel-shirshov
will rewrite the test case

@hzheng5
Copy link
Contributor Author

hzheng5 commented Oct 30, 2019

@pavel-shirshov I closed this pull request since the code is too old and has some conflicts. Please review the latest pull request #1187 instead, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants