diff options
| author | Andrew Geissler <geissonator@yahoo.com> | 2023-01-11 21:51:58 +0300 |
|---|---|---|
| committer | Andrew Geissler <andrew@geissonator.com> | 2023-01-14 00:05:22 +0300 |
| commit | 3da13b3a39f123f81094675f0802c4578f8b7a84 (patch) | |
| tree | 41c4d82329d5aefd0910943ffe59ed2aaed98122 /meta-openembedded/meta-python/recipes-devtools/python/python3-eth-utils | |
| parent | 517393d903089f921915530ffa689a7a1d113420 (diff) | |
| download | openbmc-3da13b3a39f123f81094675f0802c4578f8b7a84.tar.xz | |
meta-ibm:ncsi: ensure eth speeds set to 1 gigabit
IBM has run into some issues recently with certain network
configurations where eth1 is not getting set to 1 gigabit. This can
cause issues in scenarios where a network environment is running on 1
gigabit minimum-speed network switches.
Removing link-local support from eth1 seemed to aggravated this.
link-local is only on eth0 to avoid subnet issues. But without
link-local, the systemd call, systemd-networkd-wait-online, does not
always find an active eth1 so it never runs the command to force eth1 up
to 1 gigabit.
As far as we can tell, there's no appropriate mapping within
systemd-networkd-wait-online for it to know when the NCSI stack is
appropriately up on a network interface (allowing the 1 gigabit speed to
be set). Therefore the solution taken in this commit is to just keep
retrying for a period of time.
Tested:
- Verified new script ran and set eth ports as expected
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6737e208b59830262f51a8e30c78a97fc698e4fd
Diffstat (limited to 'meta-openembedded/meta-python/recipes-devtools/python/python3-eth-utils')
0 files changed, 0 insertions, 0 deletions