Proxmox VE 9.0 Installation on a Supermicro CSE-829U Server

Phoenix85

Member
Jan 14, 2025
65
1
8
Germany
Hi,

Installation in a ZFS 1 so mirrored wasn’t an issue and worked flawlessly.

My issue seems to be the Intel X540 Network Controller on the Server Mainboard.

Mainboard of Server X10DRU-I+ from Supermicro

The Network Bridge vmbr0 is down

I tried the allow unsupported SFP =1 but that didn‘t help

I have pictures but the forum always says they are too large.

Any idea how to fix it?
 
Last edited:
Please provide the output for:
Bash:
~# ip a 
~# cat /etc/network/interfaces
~# pveversion -v
Also try:
Bash:
lspci | grep -i ethernet
You should see the X540 entries.
 
Last edited:
Router is a Ubiquiti Dream Machine Pro SE with Gateway 192.168.1.1

I have Fiber Glass connection from Deutsche Telekom in Germany.

192.168.1.57 and 192.168.1.173 are my both Pi-Holes.

I also have a single Intel I210T1 PCI-Express card here for testing if needed.
 
Last edited:
Does the physical link appears to be Up? you can check if it detected with ethtool:
HTML:
ethtool enp1s0f0
...
        Link detected: yes
what happens when you try to manually bringing the vmbr0 up?
~# ifup vmbr0
 
From the earlier provided output of lspci | grep -i ethernet you have also Gigabit NIC:
For lspci |grep-i ethernet

View attachment 90837
Is the cable plugged in to the Gigabit NIC now? or are you plan is to use the 10-Gigabit connection? I think the Gigabit is correspond to ens2 (altname enp3s0)

If you want you can give it try and use it instead of Intel X540 10G card. Connect the cable to the Gigabit NIC and update your interfaces file to use ens2 instead of enp1s0f0. then try to bring the interface up with ~# ifup vmbr0


As you know, the message, Link detected: no, means that your network interface is not detecting a physical link (e.g., from a cable or switch). It could be:
1. Faulty or unsupported NIC
2. Bad or incompatible SFP module (if used).
3. Incorrect speed/duplex settings.
4. Cable is not properly plugged in at both ends (PVE and the switch/router/modem) or faulty one, (Pretty sure you did those check but just writing it just in case).

By the way, you can easily share the output of the command in a code block using the code icon in the forum toolbar, instead of attaching it as a screenshot.
 
At the moment an Ethernet cable is in IPMI Port and one in the Intel Gigabit NIC.
My plan is to use the 10 GBIT connection if possible. But at the moment it doesn't work.

I will test the Gigabit NIC later if that will work out of the box.

1. Don't think so as I have a second equal server with Proxmox Backup Server where I also can't get the 10GB ports to work .... yet
2. I don't think they have SFP Modules --> it's pure copper RJ-45 isn't it?
3. -> should I check this in my Ubiquiti Console?
4. Faulty one ... I had a few min ago a Hue Bridge Pro on it without any problems.

ens2 instead of enp1s0f0 --> how can I change that in the interfaces?

Is it via this command cat /etc/network/interfaces ?

And if, how?

Thanks
 
Last edited:
Yes I think this would be a good quick test.
ens2 instead of enp1s0f0 --> how can I change that in the interfaces?
You can do it via the web gui: Datacenter -> host -> network
edit vmbr0 and use ens2 for the bridge ports, and then click apply. After that verify if vmbr0 up, if not use ~# ifup vmbr0
 
Yeah I can’t access the GUI yet so I have to do it via cat /etc/network/interfaces ?

I‘m searching through Google to see how I can do via interfaces
Will this work?


In a Proxmox VE environment, you can't directly rename the virtual bridge vmbr0 to ens2, as they are two different types of network devices. The vmbr0 is a Linux bridge that acts as a virtual switch, while ens2 is a physical network interface (the name for a NIC, or Network Interface Card).

To change your network setup so that your virtual machines and the Proxmox host itself use the ens2 physical interface, you need to modify the network configuration file.


auto lo
iface lo inet loopback

iface enp3s0 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.1.10/24
gateway 192.168.1.1
bridge-ports enp3s0
bridge-stp off
bridge-fd 0
In this example, vmbr0 is the network bridge, and it's using the physical interface enp3s0. Your goal is to change enp3s0 to ens2.

1. Identify Your Current Network Configuration​



First, you need to access the Proxmox host's shell to check the current setup. You can do this via the web GUI's shell or an SSH client.Once you're in, run the following command to view the network configuration file:

cat /etc/network/interfaces

The output will show you the current configuration, likely similar to this:






2. Edit the Network Interfaces File ✍️



Use a text editor like nano or vim to edit the configuration file.

nano /etc/network/interfaces

Find the vmbr0 section and change the bridge-ports line to use ens2 instead of the old physical interface name.

Before:

auto vmbr0
vmbr0 inet static
address 192.168.1.10/24
gateway 192.168.1.1
bridge-ports enp3s0
bridge-stp off
bridge-fd 0

After:

auto vmbr0
vmbr0 inet static
address 192.168.1.10/24
gateway 192.168.1.1
bridge-ports ens2
bridge-stp off
bridge-fd 0

Don't forget to also find and change the line iface enp3s0 inet manual to iface ens2 inet manual. This ensures that the physical interface itself is not configured with an IP address, as its role is now to serve as a port for the bridge.

After making the changes, save and exit the file. In nano, press CTRL + X, then Y, and Enter.




3. Apply the Changes​



Once the file is saved, you have two options to apply the changes:

  • Via the Proxmox GUI: Go to Node -> Network and click the Apply Configuration button. This is the safest method and, with the ifupdown2 package installed, it can apply the changes without a reboot.
  • Via the command line: Run the command ifreload -a. This will attempt to apply the new configuration.
If those methods fail or if you're not using the ifupdown2 package, a simple reboot of the Proxmox host is a guaranteed way to apply the new network settings.

reboot
 
Last edited:
Yes this should work.
First connect the ethernet cable to the Gigabit NIC and ensure the link is detected:
Bash:
~# ethtool ens2
...
        Link detected: yes
Then, edit the interfaces file:
nano /etc/network/interfaces
In the vmbr0 section, change the bridge ports to be ens2.
In order to save the file in [0] nano press CTRL + X, then Y, and Enter.

After that ~# ifup vmbr0 should make the bridge port up.

[0] https://www.geeksforgeeks.org/linux-unix/nano-text-editor-in-linux/
 
First picture shows the installed x1 Intel Gigabit NIC Card.

Second picture shows no LED's for the plugged cable into the Intel Gigabit Interface.

Third picture shows the other ends of the Network Cable through that it goes into my Network rack.

Fourth picture shows IPMI which shows LED activity
 

Attachments

  • IMG_3108.JPG
    IMG_3108.JPG
    694.3 KB · Views: 5
  • IMG_3109.JPG
    IMG_3109.JPG
    512.5 KB · Views: 5
  • IMG_3110.JPG
    IMG_3110.JPG
    303.1 KB · Views: 6
  • IMG_3111.JPG
    IMG_3111.JPG
    454.1 KB · Views: 5
Output of this command?
Code:
for nic in $(ip -o link show | awk -F': ' '{print $2}'); do     echo "--- Interface: $nic ---";     ethtool "$nic" | grep "Link detected";     echo ""; done

R.