[simple-fib] Fixes vm CPU hog issue in ECMP test.#1103
Closed
stephenxs wants to merge 2 commits intosonic-net:masterfrom
stephenxs:fix-ecmp-hog-vm-cpu
Closed
[simple-fib] Fixes vm CPU hog issue in ECMP test.#1103stephenxs wants to merge 2 commits intosonic-net:masterfrom stephenxs:fix-ecmp-hog-vm-cpu
stephenxs wants to merge 2 commits intosonic-net:masterfrom
stephenxs:fix-ecmp-hog-vm-cpu
Conversation
added 2 commits
September 6, 2019 11:49
The ecmp test test works by sending 10000 packets to DUT and then checking whether the load is balanced. However, the default mtu for this test case is 9112. With such mtu the VM CPU utilization can rise to 100%, which prevent routing protocols and LACP from running and then causes routing entries on DUT withdrawn and LAG interfaces flapped and fails the test. Fix the issue by using 1500 as the MTU to avoid hogging VM CPU.
prsunny
reviewed
Sep 7, 2019
| - debug : msg="Start FIB Test" | ||
|
|
||
| - set_fact: mtu=9114 | ||
| - set_fact: mtu=1500 |
Contributor
There was a problem hiding this comment.
This is a configurable parameter. Can we have this default to 9100 and in your test modify to 1500?. Prefer to keep the default as 9100.
Contributor
Author
There was a problem hiding this comment.
Sure. It's a better option. Then I will close this PR.
Contributor
Author
|
Set the mtu to 1500 by using ansible's arguments. Close the PR. |
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
…omatically (#24671) #### Why I did it src/sonic-swss-common ``` * ebebd2c - (HEAD -> 202505, origin/202505) Migrate agent pool from sonicbld-1es to sonicso1ES-amd64 for branch 202505 (sonic-net#1103) (21 hours ago) [yijingyan2] ``` #### How I did it #### How to verify it #### Description for the changelog
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
Revert "Revert " [201911]show interface counters for multi ASIC devices (sonic-net#1104)"" Revert "Revert "Pfcstat (sonic-net#1097)"" [show] Fix 'show int neighbor expected' (sonic-net#1106) Update argument for docker exec it->i (sonic-net#1118) Update to make config load/reload backward compatible. (sonic-net#1115) Handling deletion of Port Channel before deletion of its members (sonic-net#1062) Skip default route present in ASIC-DB but not in APP-DB. (sonic-net#1107) [CLI][PFCWD][Multi-ASIC] Added multi ASIC support to 'pfcwd' CLI (sonic-net#1102) [201911] Multi asic platform config interface portchannel, show transceiver (sonic-net#1087) [drop counters] Fix configuration for counters with lowercase names (sonic-net#1103) Signed-off-by: Abhishek Dosi <abdosi@microsoft.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of PR
Summary:
Fixes vm CPU hog issue in ECMP test
Type of change
Approach
How did you do it?
The ecmp test works by sending 10000 packets to DUT for l3 forwarding and then checking whether the forwarded packets are load-balanced. However, the default mtu for this test is 9112. With such mtu the VM CPU utilization can rise to 100%, which prevent routing protocols and LACP from running and then causes routing entries on DUT withdrawn and LAG interfaces flapped and fails the test.
Fix the issue by using 1500 as the MTU to avoid hogging VM CPU.
How did you verify/test it?
Run test on all topo.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation