Hi there,
Since a while, I have the follwing warning poping up in my network logs:
kernel
Warning: Deprecated Driver is detected: team will not be maintained in a future major release and may be disabled
PRIORITY 2
SYSLOG_FACILITY 0
SYSLOG_IDENTIFIER kernel
_BOOT_ID d4d3b70556034441872907cf80fb8ff4
_HOSTNAME my.server.local
_MACHINE_ID 79fd04559cc940cbb1180ab7b0816208
_SOURCE_MONOTONIC_TIMESTAMP 5719405
_TRANSPORT kernel
__CURSOR
s=9b3dd0987b264eecbfd42e6b922b4d35;i=5b4;b=d4d3b70556034441872907cf80fb8ff4;m=5748b5;t=616276aace14d;x=5a73675a42f6e8a
__MONOTONIC_TIMESTAMP 5720245
__REALTIME_TIMESTAMP 1713208409514317
As I plan to migrate soon my Almalinux servers to 9.X, I’m wondering what I should do prior ending in a catastrophe as this one is the only physical server I have. It uses an Intel X520 with dual 10G/s ports.
Also to note : every time I restart that server, instead of negotiating the speed to 20000 Mb/s, it only uses half of it until I remove one link from the bond and putting it back again.
Thanks in advance for you help! 
Do you really have bond or a team?
nmcli c s
The TeamD was a short-lived (RHEL 7 to 8) alternative for bonding.
What does lspci -nn show for the X520? (The device ID.)
Looks like a team:
It shows this:
03:00.0 Ethernet controller [0200]: Intel Corporation Ethernet 10G 2P X520 Adapter [8086:154d] (rev 01)
03:00.1 Ethernet controller [0200]: Intel Corporation Ethernet 10G 2P X520 Adapter [8086:154d] (rev 01)
So I guess I will have to recreate it as a bond no?
I did created it from cockpit if I remember right, but I don’t think there is an option to choose the type there.
Do you know if there is something we can do directly in configuration file?
Anyway, thanks for enlighting this already! 
The ixgbe of el9 does know that device:
[Alma9]$ modprobe -c | grep -i 8086.*154d
alias pci:v00008086d0000154Dsv*sd*bc*sc*i* ixgbe
(Note: RHEL includes some device IDs into the kernel modules that they build even when the code does not support that device. ELRepo builds “full” driver modules, so lack of driver is not always an issue.)
I don’t touch the files when I use NetworkManager.
If I configure “by hand”, then I do use nmcli. Red Hat has instructions:
RHEL 8: Chapter 3. Configuring network bonding Red Hat Enterprise Linux 8 | Red Hat Customer Portal
RHEL 9: Chapter 3. Configuring network bonding Red Hat Enterprise Linux 9 | Red Hat Customer Portal
However, I do now prefer Ansible configuration management, because I can keep logical config separate, in git repo (with clones for backup).
For bond, a later section in the aforementioned page: Chapter 3. Configuring network bonding Red Hat Enterprise Linux 9 | Red Hat Customer Portal
One does need packages ansible-core and rhel-system-roles in some machine to run the “play”.