Re: TCP2617 Reason Code 2 and Reason Code 3 -- MIDRANGE-L

Subject: Re: TCP2617 Reason Code 2 and Reason Code 3
From: Lukas Beeler <lukas.beeler@xxxxxxxxxxxxxxxx>
Date: Wed, 24 Mar 2010 21:31:33 +0100
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On Wed, Mar 24, 2010 at 21:25, Bryce Martin <BMartin@xxxxxxxxxxxx> 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?

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?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: TCP2617 Reason Code 2 and Reason Code 3 , Bryce Martin

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.