Re: TCP2617 Reason Code 2 and Reason Code 3

Perhaps the following may assist, albeit if the PTF is not applied, then that means running on an old, e.g. '08, cumulative?:
http://www-01.ibm.com/support/docview.wss?uid=nas294f4450c1c0ecaa2862573f70041f3c5

Presumably that is what is described [in Japanese] with subject "5700,5701,5706,5707 Ethernet adapter communication disconnection problem", here:
http://www-06.ibm.com/jp/domino01/mkt/cnpages1.nsf/page/default-00028B52
http://translate.google.com/translate?hl=en&sl=ja&u=http://www-06.ibm.com/jp/domino01/mkt/cnpages1.nsf/page/default-00028B52

Or perhaps more recent [if even only supersedes] "Ethernet Hardware PTFs" per a search on tokens: "IOPless" "ethernet"
https://www-912.ibm.com/s_dir/slkbase.NSF/643d2723f2907f0b8625661300765a2a/7f26d499f84de3f286256a3800632aee?OpenDocument

Regards, Chuck

Bryce Martin wrote:

We are seeing our remote journals ending due to the connection
dropping. Sometimes reason code 2 but this afternoon it was
almost all reason code 3. Our network guys have put a Fluke probe
on the switch and said they weren't seeing any dropped packets
between the two machines.

On Wed, Mar 24, 2010 at 21:25, Bryce Martin wrote:

I think that the Target machine has to be dropping a connection
or something because our Host machine is our main production
box and we aren't having any problems with its connections.
Could it be cabling? The switch ports?

Lukas Beeler wrote:

It could be, but what exactly is the issue you're experiencing? Is the link flapping? Lost packets? What do the Switch statistics
say? Did you test the cable using a real cable tester (e.G. Fluke)?

Are we talking about the HA links having issues or the normal network connection? How's the HA link made? Directly?