Intel i350 GBE network controller not working

zogthegreat

New Member
May 29, 2020
8
1
1
60
Hi everyone!

My Asus Z9PR-D12 died on me and I've replaced it with a Supermicro X9DR3-LN4F+. I went with this board because I already had the CPU's and memory and I'm not really doing anything with it that I need a newer CPU.

My problem is that after installing Proxmox, the network dies. I used the following to get my NIC information:

ip -br -c link show

lo UNKNOWN 00:00:00:00:00:00 <LOOPBACK,UP,LOWER_UP>
eno1 DOWN 00:25:90:86:06:AE <NO-CARRIER,BROADCAST,MULTICAST,UP>
eno2 DOWN 00:25:90:86:06:AF <BROADCAST,MULTICAST>
eno3 DOWN 00:25:90:86:06:B0 <BROADCAST,MULTICAST>
eno4 DOWN 00:25:90:86:06:B1 <BROADCAST,MULTICAST>
vmbro DOWN 66:47:6B:C3:7A:36 <NO-CARRIER,BROADCAST,MULTICAST,UP>

Based on the output, it looks like my network is up, however, when I try to ping the local network, I get "Destination Host Unreachable". Also, on boot, the green and yellow light on the NIC are lit up, but once Proxmox boots, the lights go out.

Any suggestion as to where I'm messing up?

Thanks!

zog
 
I've tried add the MAC address to vmbro as described here:

https://forum.proxmox.com/threads/no-network-connectivity-after-fresh-proxmox-7-install.92133/

But it didn't work.

I also tried "systemctl restart networking" and I got the following output:

device eno1 left promiscuous mode
vmbr0: port 1(eno1) entered disabled state
vmbr0: port 1(eno1) entered blocking state
vmbr0: port 1(eno1) entered disabled state
device eno1 left entered mode

{EDIT} I think I figured it out. I ran ip link set dev eno* up for each of the interfaces. This started the network and I was able to connect with SSH. Not sure if the problem is resolved, but I can get in, so that's a start!
 
Last edited: