LAN Port enumaration Problem

[caustic]

Hello,
I got a problem with my LAN Interfaces.
I've two on board and 2 Network Interface Cards installed.
All were shown by manboardbios correctly installed and connected.
But two lanports are shown under proxmox as rename10 and rename11 and unkown...

ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
link/ether ac:1f:6b:d5:d6:44 brd ff:ff:ff:ff:ff:ff
3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1 state UP mode DEFAULT group default qlen 1000
link/ether ac:1f:6b:d5:d6:45 brd ff:ff:ff:ff:ff:ff
4: ens9f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr2 state UP mode DEFAULT group default qlen 1000
link/ether a0:36:9f:5e:23:6c brd ff:ff:ff:ff:ff:ff
5: ens5f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 00:1b:21:53:a9:f9 brd ff:ff:ff:ff:ff:ff
6: ens9f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr3 state UP mode DEFAULT group default qlen 1000
link/ether a0:36:9f:5e:23:6d brd ff:ff:ff:ff:ff:ff
7: ens9f2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr4 state UP mode DEFAULT group default qlen 1000
link/ether a0:36:9f:5e:23:6e brd ff:ff:ff:ff:ff:ff
8: ens9f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr5 state UP mode DEFAULT group default qlen 1000
link/ether a0:36:9f:5e:23:6f brd ff:ff:ff:ff:ff:ff
9: ens5f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 00:1b:21:53:a9:f8 brd ff:ff:ff:ff:ff:ff
10: rename10: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 00:1b:21:53:a9:fb brd ff:ff:ff:ff:ff:ff
11: rename11: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 00:1b:21:53:a9:fa brd ff:ff:ff:ff:ff:ff
12: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether ac:1f:6b:d5:d6:44 brd ff:ff:ff:ff:ff:ff
13: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether ac:1f:6b:d5:d6:45 brd ff:ff:ff:ff:ff:ff
14: vmbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether a0:36:9f:5e:23:6c brd ff:ff:ff:ff:ff:ff
15: vmbr3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether a0:36:9f:5e:23:6d brd ff:ff:ff:ff:ff:ff
16: vmbr4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether a0:36:9f:5e:23:6e brd ff:ff:ff:ff:ff:ff
17: vmbr5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether a0:36:9f:5e:23:6f brd ff:ff:ff:ff:ff:ff
root@pve1:~#

Everything seems to be recognized...

root@pve1:~# lspci | egrep -i --color 'network|ethernet'
04:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
05:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
19:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06)
19:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06)
1a:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06)
1a:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06)
b3:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
b3:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
b3:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
b3:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)

Aber :


Startuplog :

Jul 12 05:55:12 pve1 kernel: e1000e 0000:1a:00.0 eth1: (PCI Express:2.5GT/s:Width x4) 00:1b:21:53:a9:fb
Jul 12 05:55:12 pve1 kernel: e1000e 0000:1a:00.0 eth1: Intel(R) PRO/1000 Network Connection
Jul 12 05:55:12 pve1 kernel: e1000e 0000:1a:00.0 eth1: MAC: 0, PHY: 4, PBA No: D57995-007
Jul 12 05:55:12 pve1 kernel: e1000e 0000:1a:00.1: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Jul 12 05:55:12 pve1 kernel: e1000e 0000:1a:00.1 eth2: (PCI Express:2.5GT/s:Width x4) 00:1b:21:53:a9:fa
Jul 12 05:55:12 pve1 kernel: e1000e 0000:1a:00.1 eth2: Intel(R) PRO/1000 Network Connection
Jul 12 05:55:12 pve1 kernel: e1000e 0000:1a:00.1 eth2: MAC: 0, PHY: 4, PBA No: D57995-007
Jul 12 05:55:12 pve1 kernel: e1000e 0000:19:00.0 ens5f0: renamed from eth3
Jul 12 05:55:12 pve1 kernel: e1000e 0000:1a:00.1 ens5f1: renamed from eth2
Jul 12 05:55:12 pve1 kernel: e1000e 0000:1a:00.0 rename10: renamed from eth1
Jul 12 05:55:12 pve1 kernel: e1000e 0000:19:00.1 rename9: renamed from eth0

I never had such a problem in previous releases ... Is there a solution?
Thanks in advance.
caustic

 

[Stoiko Ivanov]

Try upgrading the BIOS/UEFI and all other firmwares of your system - this helps quite often in this situation

 

[caustic]

Thank you very much, for your answer.
This is the first thing I did.

But this did not solve the problem.
In my opinion the kernel driver has an issue.

It was a brand new Proxmox setup.

The log files are showing the following issue.
There is set eth0 for two diffrent lan ports and the same with eth1.
So it is impossible to rename these ports correctly.

Jul 12 05:55:12 pve1 kernel: e1000e 0000:19:00.1 rename9: renamed from eth0
the same eth0 is given by the kernel to
04:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
this is eth0 too

I changed the network interface card with another controller chip now and the enumeration is ok.
eth0 to eth9.

Solved for me so far, but the e1000e driver should be watched.
Today I read a lot about this driver and it seems to me this driver has more then one issue.
But ok I'm not an expert in driver developpment or implementation.

Best Regards
Sven