Как правило это не фулл дуплекс. И ошибки крк или буфера на интерфейсах. В одном регионе такое было порой.
interface ethernet print stats where name=ether17
name: ether17
driver-rx-byte: 0
driver-rx-packet: 0
driver-tx-byte: 42 215
driver-tx-packet: 644
rx-bytes: 0
rx-too-short: 0
rx-too-long: 0
rx-unicast: 0
rx-broadcast: 0
rx-pause: 0
rx-multicast: 0
rx-error-events: 0
rx-fcs-error: 0
rx-fragment: 0
rx-overflow: 0
rx-jabber: 0
tx-bytes: 0
tx-unicast: 0
tx-broadcast: 0
tx-pause: 0
tx-multicast: 0
tx-underrun: 0
tx-collision: 0
tx-late-collision: 0
tx-drop: 0
tx-rx-64: 0
tx-rx-65-127: 0
tx-rx-128-255: 0
tx-rx-256-511: 0
tx-rx-512-1023: 0
tx-rx-1024-max: 0
tx-queue0-packet: 0
tx-queue1-packet: 0
tx-queue2-packet: 0
tx-queue3-packet: 0
tx-queue4-packet: 0
tx-queue5-packet: 0
tx-queue6-packet: 0
tx-queue7-packet: 0
interface ethernet monitor ether17
;;; --PQ.HOSTING_NODE01--
name: ether17
status: link-ok
auto-negotiation: done
rate: 1Gbps
full-duplex: yes
tx-flow-control: no
rx-flow-control: no
advertising: 10M-half,10M-full,100M-half,100M-full,1000M-half,1000M-full
link-partner-advertising: 10M-half,10M-full,100M-half,100M-full,1000M-half,1000M-full