Ask Your Question

Revision history [back]

TCP Previous Segment not Captured and TCP out of order

We are running Fortra Robot scheduler between an AS400 and Windows servers over a multipath SD-WAN network. For the last several months the agent on the windows server keeps losing connection to the AS400 temporarily. We use Solarwinds Orion and Solarwinds Netpath to see connectivity and run synthetic transactions and with the expection of an occasional packet drop it looks clean.

The agent uses port 7472 to connect to the AS400 and then SSH to transfer data. When I run a packet capture I see a number of TCP Previous Segment not captured and then TCP out of order. These seem to correlate with the drops the agent reports. I have uploaded the packet capture which has multiple agents captured but in this case the communication is between the AS400 150.100.10.41 and the agent at 10.33.1.210. If I filter on tcp.stream 248 that shows the stream using port 7472. I have uploaded the packet capture as well.

I'm at a loss at what the issue could be and seeing if anyone is seeing anything. At this point I'm leaning toward a TCP stack issue on the AS400 since it seems to be happening on multiple agents.

TCP Previous Segment not Captured and TCP out of order

We are running Fortra Robot scheduler between an AS400 and Windows servers over a multipath SD-WAN network. For the last several months the agent on the windows server keeps losing connection to the AS400 temporarily. We use Solarwinds Orion and Solarwinds Netpath to see connectivity and run synthetic transactions and with the expection of an occasional packet drop it looks clean.

The agent uses port 7472 to connect to the AS400 and then SSH to transfer data. When I run a packet capture I see a number of TCP Previous Segment not captured and then TCP out of order. These seem to correlate with the drops the agent reports. I have uploaded the packet capture which has multiple agents captured but in this case the communication is between the AS400 150.100.10.41 and the agent at 10.33.1.210. If I filter on tcp.stream 248 that shows the stream using port 7472. I have uploaded the packet capture here as well.well. https://www.cloudshark.org/captures/f4df9747c8e7

I'm at a loss at what the issue could be and seeing if anyone is seeing anything. At this point I'm leaning toward a TCP stack issue on the AS400 since it seems to be happening on multiple agents.