-
Notifications
You must be signed in to change notification settings - Fork 136
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
MAC address fix #223
MAC address fix #223
Conversation
CI MessageYour results will arrive shortly |
CI MessageError: ERROR: Failed to post results to GitHub |
@onvm try again? |
CI MessageYour results will arrive shortly |
CI MessageError: ERROR: Failed to post results to GitHub |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This worked for me. Made sure to checkout on the PR branch, ran the manager with the default syntax and ran the load generator NF with ./go.sh 1 -d 2 -m <Nimbus node MAC address>
and had no issues. Did not see the "Failed to obtain MAC address" error.
@onvm is this working now? |
CI MessageYour results will arrive shortly |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@onvm is this working now?
CI Message
Run successful see results:
Test took: 5 minutes, 23 seconds
✔️ Pktgen performance check passed
✔️ Speed Test performance check passed
[Results from nimbnode23]
-
Median TX pps for Pktgen: 7721721
Performance rating - 100.28% (compared to 7700000 average) -
Median TX pps for Speed Tester: 42227047
Performance rating - 100.54% (compared to 42000000 average)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good fix, remove it from lb and I'll approve
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good - lets add a RTE_LOG(INFO, APP, "")
(dpdk's print statement) somewhere to let the user know we're using a fake mac addr (as discussed on slack)
speed_tester has the same setup. Should we add the same print to it as well? @dennisafa |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Tested again using same configuration as above. No problems.
@catherinemeadows I think it would be useful to have a print statement like this one in speed_tester |
Agreed - sorry I missed this comment. A comment wherever we fake it is a good idea. |
Fixes the load_generator bug mentioned in #222
Summary:
In order to resolve the issue where the "Failed to obtain MAC address" error is raised in the load_generator NF, the function onvm_get_fake_macaddr() is used to obtain a fake MAC address for testing or in the case that the provided MAC address of the port is not bound to DPDK.
Usage:
Merging notes:
TODO before merging :
Test Plan:
Ran the load_generator NF with the MAC address of the node I am testing with. I had @sreya519 run this fix for the load_generator as well since she experienced this error.
Review:
@sreya519 --> tested the load_generator fixes already