Just to make that clear again: the networt link is not saturated. Monitoring shows an average of around 400 MBit/s on a GBit interface. Which means it is quite far away from a bandwith problem. So the real question here is: why are packets lost...
I wanted to try the problem situation with a bbr congestion variant. But I found that the kernel delivered with proxmox does not supply this congestion protocol. Why is this?
That is not the complete truth. Look at this:
--- 192.168.192.250 Ping-Statistiken ---
14000 Pakete übertragen, 13862 empfangen, 0.985714% packet loss, time 14133836ms
rtt min/avg/max/mdev = 0.103/1.065/3.615/1.127 ms
This is quite a long...
No, the fiber link is dedicated, the copper is also used for other purposes. I checked that in detail and had to find out that the latest kernel networking is not really as good as one might think - after all those years. If there is nfs traffic...
Hello all,
I recently experience a problem with corosync showing link flapping, but it seems to me that these are really fake. Neither the corresponding switch shows a link problem, nor the kernels of the boxes (3-box cluster). I use a 10G fiber...