badmotors.blogg.se

Wireshark tcp retransmission causes
Wireshark tcp retransmission causes










wireshark tcp retransmission causes

I finally got an opportunity to go out there and do some proper diagnostics. That worked, and they've been running like that for about a month. It got worse and worse until I eventually had them disconnect the uplink between the Stratix 5700 and the unmanaged switch in the ML1400 cabinet, and string a patch cable directly between the two unmanaged switches, just to get them out of immediate trouble. There seemed to be the occasional dropout to the other ML1400 (not shown) as well, but none to the PLC's on produced/consumed, and the ML1400 in the picture was definitely the main culprit. The ML1400 doesn't talk to anything else.Ībout 4 months ago, they started getting sporadic comms dropouts between the L71 and the ML1400.

wireshark tcp retransmission causes

The L71 also talks to one other ML1400 with more or less identical architecture, and about 5-6 CompactLogix/ControlLogix PLC's using produced/consumed tags, again with similar physical infrastructure. It's been in place and working fine for about 4 years.

wireshark tcp retransmission causes

The L71 uses explicit messaging to read and write to and from the ML1400. Got a customer with a control system architecture like this:












Wireshark tcp retransmission causes