Sometimes, Proxmox is not visible on the network, before I restart it a couple of times.

[yonoss]

At least two of your screenshots show "NO CARRIER" and "NO LINK" detected on your eno1 interface. That's a physical layer issue, unlikely to have anything to do with DHCP distribution.

Try a different cable, different port and finally different NIC. Even thousand dollar Mellanox NIC sometimes are DoA. It happens. Or the chipset on the NIC is no (longer) compatible with the Kernel, or support got broken.

The fastest way to resolution is by swapping the parts.

You can also try to throw LINKDELAY in your config file, although I am not sure what the equivalent of it is netplan format.
https://support.hpe.com/hpesc/public/docDisplay?docId=sf000059866en_us&docLocale=en_US

Good luck

---

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

The fix for my problem is a system reboot. IMO if there would have been a physical problem with any of the network related components, the reboot wouldn't have helped. Plus I've already tried with multiple systems, network cables and even switches. When I was running proxmox, with each deployment I was seeing this behavior.

 

[bbgeek17]

The fix for my problem is a system reboot.

Did you try to quantify cold vs warm reboot? Perhaps on warm reboot the chipset is properly initialized. Or perhaps, its just a race between BIOS and firmware, and sometimes you get lucky.

Reliably troubleshooting such DIY home setups is next to impossible, compared to a proper enterprise hardware. The "no carrier" should not happen if there is light/cable between two ports. Get yourself a $10 unmanaged 5 port switch and plug the cables there. Does the "no link"/"no carrier" persist?

---

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