Quote:
Originally Posted by
bobochacha29
On this ethernet segment we have many servers, but only these two servers got error, so I don't think this's the point.
A slight delay in a packet on a busy Ethernet segment is not "an error". That is how Ethernet works.
What you are "showing us' (an occasional 44 ms delay) is typical of all busy Ethernet segments with many devices.
44 ms is 44 one thousandths of a second. 44/1000 seconds.
The way in which you answer my questions shows you do not understand LAN networking and Ethernet (or networking in general).
Delays on an Ethernet segment are not "errors" and nor is it a sign of "instability". This his how the Ethernet (and indeed most networking protocols work) protocols works (queues, delays, priorities).
If you want guaranteed fast delivery between two hosts, you need to move them to their own Ethernet segment with only two devices on that network.
This is the only approach any experienced network engineer would take or advise.
Think about how Ethernet works. Every device wants to talk at the same time on the same wire. They cannot talk at the same time. The more devices, the more this happens. Each device will wait a random number of milliseconds to transmit when the network is busy. This is now LANs work. The more devices, the more a chance of a delay. So..... a 44ms delay (44/1000 of a second) occasionally on a busy LAN segment is normal.
As I mentioned to you, but you do not seem to want to understand, you want guaranteed fast delivery between two hosts on a LAN segment, you need to
move them to their own Ethernet segment with only two devices on that physical networking segment.