New 4.4 install, unable to reach network (other live CDs work just fine)

[Giovanni]

Hello,

I just installed PVE 4.4 via iDRAC on a host that has had the same network configuration and was remotely accessible (from the internet). I am stumped at the network issue I am seeing on the bridge interface.

I have checked /etc/networking/interfaces

vmbr0 has member interfaces eth0 and the ip settings are under it (eth0 is not listed in there elsewhere)

If I boot a linux live CD It gets network just fine, not sure what else or where to troubleshoot this, any ideas? It is definitely something at the OS Level. I attempted a re-install but ended up with the same result.

Network is static IP and not DHCP, have triple verified the gateway, network and IP addressed hardcoded in the config to be the same as the one in the tested LiveCDs.

 

[manu]

Maybe a physical link problem ?

Check with 'ip link' that Ethernet connectivity is there ( it should show LOWER_UP on both vmbr0 and eth0)

 

[Giovanni]

Maybe a physical link problem ?

Check with 'ip link' that Ethernet connectivity is there ( it should show LOWER_UP on both vmbr0 and eth0)

Thanks for the reply.

vmbr0 is NO-CARRIER, BROADCAST, MULTICAST, UP state DOWN

Attached is the screenshot of ip link and ip addr show vmbr0

 

[Giovanni]

This is interesting, I have another server. Exact same hardware Dell R320 with 4 network cards (bnx2 driver in kernel) and neither server can get networking working in proxmox.

The 'dmesg | grep eth' is the same on both servers.

bnx0 eth0 using MSIX
vmbr0 entered forwarding state
vmbr0 entered forwarding state
vmbr0 entered disabled state
device eth0 left promiscuous mode

Not sure what else to try, is it a kernel driver issue?

 

[Giovanni]

looks like firmware-bnx2 from debian/jessie is basically the same as currently loaded on pve-firmware so we're good on it.

After reading more on dmesg I found the problem. The eth name was changed on debian/pve (other live CDs like sysrescuecd would detect the built-in ethernet card as eth0 - for some reason proxmox sees that exact same network card as "eth2")

Swapping the eth0 member with eth2 and resetting the networking stack fixed the issue. I made a blog post detailing the commands to fix this for anyone else noticing the same issue after fresh install.

 

[manu]

Hi Giovanni

Proxmox 5.0 will be based on Debian Stretch, which has persistent nic naming, this should solve this class of problems ( devices will be named after their geographical position on the pci bus, and not assigned a name based on the timing of their detection by the kernel)

see https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ for details

 

[johnnywoz]

yes! Thank You!

...After reading more on dmesg I found the problem. The eth name was changed on debian/pve (other live CDs like sysrescuecd would detect the built-in ethernet card as eth0 - for some reason proxmox sees that exact same network card as "eth2").

This was my issue as well, no network after fresh install (on new hardware). My motherboard has 2 NICs, and following your directions I found eth1 was up and eth0 was down, so just moved the network cable from one port to the other and viola!!!!

 

[fabian]

the 5.0 Beta installer supports choosing the management NIC, and should autodetect the/an active one if DHCP is available on your network.

 

[spamsam]

Solution was 100% spot on

 

[JesusM]

looks like firmware-bnx2 from debian/jessie is basically the same as currently loaded on pve-firmware so we're good on it.

After reading more on dmesg I found the problem. The eth name was changed on debian/pve (other live CDs like sysrescuecd would detect the built-in ethernet card as eth0 - for some reason proxmox sees that exact same network card as "eth2")

Swapping the eth0 member with eth2 and resetting the networking stack fixed the issue. I made a blog post detailing the commands to fix this for anyone else noticing the same issue after fresh install.

I get this error:
root@server:~# ifup -a
interface dummy0 does not exist!

Waiting for vmbr1 to get ready (MAXWAIT is 2 seconds).
/bin/sh: 1: /etc/pve/kvm-networking.sh: not found
ifup: failed to bring up vmbr1

Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds).
RTNETLINK answers: File exists
ifup: failed to bring up vmbr0