Skip to content

Conversation

@marif-nexthop
Copy link
Contributor

Pre-submission checklist

  • I've ran the linters locally and fixed lint errors related to the files I modified in this PR. You can install the linters by running pip install -r requirements-dev.txt && pre-commit install
  • pre-commit run

Summary

We noticed that the management interface name after PXE booting FBOSS distro images changed to eno1. Some other linux images has it as eth0 which is the default in some FBOSS tests too.
Added biosdevname=0 net.ifnames=0 kernel commandline args to kernel. These two kernel arguments are used to disable Predictable Network Interface Naming feature which names interfaces like eno1 instead of eth0.

Test Plan

Tested on available hardware and verified that the management interface name is eth0.

…o FBOSS image (facebook#243)

<!-- Thanks for submitting a pull request! We appreciate you spending
the time to work on these changes. Please provide enough information so
that others can review your pull request. -->

**Pre-submission checklist**
- [x] I've ran the linters locally and fixed lint errors related to the
files I modified in this PR. You can install the linters by running `pip
install -r requirements-dev.txt && pre-commit install`
- [x] `pre-commit run`

We noticed that the management interface name on `wdg101` after PXE
booting one of our FBOSS distro images changed to `eno1`. The Accton SW
has it as `eth0` which is the default in some FBOSS tests too.
I looked at the difference and found that in our FBOSS distro image we
are not passing `biosdevname=0 net.ifnames=0` kernel commandline args
while Accton's linux image is passing it. These two kernel arguments are
used to disable `Predictable Network Interface Naming` which names
interfaces like `eno1`.

<!-- Explain the motivation for making this change and any other context
that you think would help reviewers of your code. What existing problem
does the pull request solve? -->

<!-- Demonstrate the code is solid. Example: The exact commands you ran
and their output, screenshots / videos if the pull request changes the
user interface. How exactly did you verify that your PR solves the issue
you wanted to solve? -->

<!-- If a relevant Github issue exists for this PR, please make sure you
link that issue to this PR -->
Tested by modifying kernel commandline args on Wedge800 (`wdg101`) and
verifying that the interface is listed at `eth0` and not `eno1`.
@meta-cla meta-cla bot added the CLA Signed label Dec 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant