Loss of internet, restarting network does not solve fully

[Terrum]

For some reason my host machine is losing internet connection every 30-60 minutes or such. When I run 'service networking restart' Proxmox is accessible again, but the VMs are not accessible on the internet until I shutdown and start the VM (a reboot does not solve).

'service networking status' and 'journalctl | grep networking' do not show any errors.

I am not too sure where else to look or what else to do. Any help is greatly appreciated as this is quite a serious issue for a production environment.

pveversion -v

proxmox-ve: 7.2-1 (running kernel: 5.15.39-1-pve)
pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85)
pve-kernel-5.15: 7.2-6
pve-kernel-helper: 7.2-6
pve-kernel-5.15.39-1-pve: 5.15.39-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-3
libpve-storage-perl: 7.2-7
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.5-1
proxmox-backup-file-restore: 2.2.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.5-1
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-11
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

 

[Terrum]

I also note that this only started happening after OVH had a network failure on a rack, affecting many servers. 3 of my servers were affected, 2 are fine now but 1 has this hourly network issue. They also replaced my motherboard and I think this may be the culprit but not sure how to diagnose it.

 

[Terrum]

Resolved by setting network configuration to DHCP instead of static. Not sure what is wrong with the static configuration seeing as it's very minimal, but alas.