Proxmox installation interfaces get no IP

[ocmt58z1]

Hello everyone,

I am currently installing a proxmox system on some new hardware. For reference, I am using the following CPU and Motherboard:
- AMD EPYC 7443P
- Supermicro H12SSL-NT

After the installation, I noticed that I can not connect to my proxmox system. The network interfaces are down for some reason. Here is some information on my network config:

Router is 10.67.96.1
DHCP Server (Part of the Router) is also 10.67.96.1
Static IP assigned to Proxmox during install: 10.67.96.200/24

Here is the output of

ip a

:


For some reason

ip r

didn't setup any routes - so yea, something went wrong when setting up the network things on boot, I suppose.

I also noticed some errors in dmesg, not sure what to make of them, or if they are related.



Why did my proxmox system not setup the interfaces correctly on boot? Why are they all down?
I can probably add the network config manually by handing by setting the interface up and then see if it is reachable - however, I don't understand why this doesn't work out of the box. I never had this problem with any other proxmox system. Any advice?

EDIT: Seems like this might be related: https://forum.proxmox.com/threads/broadcom-nics-down-after-pve-8-2-kernel-6-8.146185/
I really hope this is not a problem with the specific hardware/drivers of my NICs....... :/

 

[bbgeek17]

Why did my proxmox system not setup the interfaces correctly on boot? Why are they all down?

You'd need to post output of cat /etc/pve/storage.cfg so one can correlate that with physical state of your devices ip a
A wild guess - the network cable is not plugged into the right port.

The routes are only setup if the interface is up.

As to the errors - seems like you have, perhaps, a dual Infiniband/Ethernet card and need to switch it's profile from IB to Eth.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Maconly34]

In my case, after removing a PCI card I could no longer connect, because the address of the network card had changed. So in console mode, directly on the server, I run this test and it works every time after reassigning the correct port.

check the configuration by trying to restart the service:

journalctl -u networking.service -f

Look at the list of ports :

ip link show

Check the details of a specific interface :

ethtool -i enp110s0

Once you have located the correct port, check the correspondence in the config file.If necessary, replace it.
Example :

nano /etc/network/interfaces

auto lo
iface lo inet loopback


iface enp110s0 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.0.224/24
gateway 192.168.0.250
bridge-ports enp110s0

bridge-stp off
bridge-fd 0

iface enp114s0 inet manual*

Restart the service
s

systemctl restart networking

Check whether the port is UP or DOWN:

ip link show

 

[UKek]

I have the same problem.
Lock also here:
https://forum.proxmox.com/threads/broadcom-nics-down-after-pve-8-2-kernel-6-8.146185/page-2

- make Firmware Update (BIOS -> 2.9, BMC: -> 01.04.05)
- do service networking restart

 

[stepanov1975]

I just wanted to share an update for anyone using the Supermicro H12SSL-NT motherboard and facing the same issue mentioned in the first post. After installing Proxmox, I couldn’t access the web interface and noticed the network link was down. The solution, in my case, was to disable RDMA in the BIOS. Once I turned it off, the network started working correctly. Hope this helps anyone running into a similar problem!