Re: TCPIP AIX FIN-Wait-2

On Thu, 4 Aug 1994 14:57:25 EST Yves Tremblay said:
>We have adsm client on  Aix 3.2.5 with schedule prompted at adsm server
>on VM. After schedule event occur and incremental backup finish , aix
>not close port to adsm server correctly. Netstat on VM say
>FIN-Wait-2. We must close many port manually or close the adsm server on
>VM to correct this problem. Have you some information to correct this
>problem ??????
>
>                     Thanks, Yves

There is a fix. The same error was also fixed on the other platforms
such as os/2, dos, sun etc.

--------------------------------------------------------------------
Item ic06714
Item ic06714




  APAR Identifier ...... IC06714      Last Changed ........ 94/05/23
  ADSM TCP/IP CONNECTIONS NOT CLOSED TCPNET235I MESSAGES SHOW A
  FIN-WAIT-2 STATE. TCP/IP BUFFER FILLS AND DRIVER TERMINATES.

  Symptom ...... IN INCORROUT         Status ........... CLOSED  PER
  Severity ................... 3      Date Closed ......... 94/04/15
  Component .......... 564802005      Duplicate of .........
  Reported Release ......... 110      Fixed Release ............ 999
  Component Name ADSM AIX/V3 CLI      Special Types ....
  Current Target Date ..              Type of Relief ..Not Available
  SCP ................... AIXRSC      Platform ............ AIX

  Status Detail: Not Available

  PE PTF List:

  PTF List:
  Release 1B0   : IP20153 available 94/05/23 (1000 )


  Parent APAR:    PN50355
  Child APAR list:


  ERROR DESCRIPTION:
  TCP/IP connections are not close properly. On an MVS system
  a Netstat command reveals messages tcpnet235i with a state
  FIN-WAIT-2 indication (message will be net235i if profile
  nomsgid). The problem originally occured at the 0.2/1.2
  level when the scheduler was unable to contact the client
  during prompted backups. It has also been reported when a Unix
  client password gets out of sync with server and due to password
  generate continued attempts to connect with bad password fail.
  Now at the 0.4/1.4 level the problem seems to exist when the
  server does connect with the client. The client connections
  have also been reported to remain in a CLOSE_WAIT.


  LOCAL FIX:
  Recycle the ADSM server to clear this messages/connections.


  PROBLEM SUMMARY:
  USERS AFFECTED:  AIX, DOS, HP, NOV, OS/2, SUN, SCO, ULT

  PROBLEM DESCRIPTION: When the schedule mode is prompted, client
  will wait for server to establish the connection.  After the
  connection has been established, client never closes that
  connection.

  RECOMMENDATION:  Apply the CSD when available.


  PROBLEM CONCLUSION: Added code to close the TCP/IP session.


  TEMPORARY FIX:


  COMMENTS:


  MODULES/MACROS:   EXE      DSMC     AFS      DSMC


  SRLS:      NONE


  RTN CODES:


  CIRCUMVENTION:


  MESSAGE TO SUBMITTER: