RE: TCP goes down

We never had the TCP stack go down but we would sometimes see normal
TELNET socket drop. We have about 1/2 our Client Access users on SSL
TELNET and 1/2 nonSSL TELNET. And SSL TELNET would continue to work but
nonSSL TELNET stopped. All other TCP services continued to run OK when
this happened. It has not happened in about 6 months. We would stop and
restart TELNET and all was well again (except for the complaints from
the SSL TELNET users who got kicked off in order to fix the nonSSL
TELNET users. (We are V5R3 last PFTs applied late December.)

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rowe, Sheri
Sent: Tuesday, January 09, 2007 11: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?

Thanks for any words of wisdom.

Sheri Rowe
Timex Canada
Markham, Ontario

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.