RE: TCP goes down

Check out your switch in which your iSeries is plugged in.  Are there
any logs or monitoring?  Try moving your connection to a different
switch and restarting the NIC.


Christopher Bipes
Information Services Director
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rowe, Sheri
Sent: Tuesday, January 09, 2007 8:36 AM
To: midrange-l@xxxxxxxxxxxx
Subject: TCP goes down

Has anyone had a problem with their TCP connection 'dropping'?  About 8
months ago, our overnight failed as the TCP on one of our iSeries went
'down'.  The system was up and I could sign on to the console fine but
not from a Client Access session.  Tried stopping and starting TCP (all
services) and varying off and on the line, but only an IPL could get the
communication between the iSeries and my network up.  

I contacted IBM who couldn't really help.  No entries in WRKPRB either.
I couldn't ping anything.

The history log had a bunch of entries to indicate the interactive
sessions and the connection to our other iSeries had terminated
TCP2617 TCP/IP connection to remote system 169.1.1.25 closed, reason
code 2. TCP2617 TCP/IP connection to remote system 169.1.1.25 closed,
reason code 3. CPF590A Session to device WT221S2 ended normally.   

It happened again this past Friday.  Does anyone know what is causing
this?  And/or how I can correct it once it does happen without an IPL?