Title: | DEC TCP/IP Services for OpenVMS |
Notice: | Note 2-SSB Kits, 3-FT Kits, 4-Patch Info, 7-QAR System |
Moderator: | ucxaxp.ucx.lkg.dec.com::TIBBERT |
Created: | Thu Nov 17 1994 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 5568 |
Total number of notes: | 21492 |
UCX V3.3 ECO 7 Customer is reporting a problem where a connection is being closed after a number of bytes are transferred (37-40k). He is planning to upgrade to UCX V4.0 with latest ECO, but wants to know how to determine the cause of failure. We are trying to determine who closed the connection, the HP or DEC side. Since the application is 3rd party and the other box is HP Unix it is difficult to determine where the problem is. We looked at UCX resources and there does not appear to be a problem where we are running out of resources (UCX SHOW COMM & UCX SHOW COMM/MEMORY). To try and eliminate a application problem we used a TELNET session type dump out the file and it also failed with a connection closed or: %TELNET-F-REMCLOSED, remote connection closed Other related notes in this conference include: 1580.*, 2081.*. The following files contain TCPIPTRACE output, if someone can tell me who dropped the connection or refer me to some document to help me to read the trace it would be greatly appreciated. This is for a premium customer. Regards, Drew Sanford Customer Support Center C970206-5468 HIPOWR::ASDSEE:[SANFORD.PUBLIC] UCXTRACE1.LOG -> TCPIPTRACE for 3rd party transfer UCXTRACE2.LOG -> TCPIPTRACE for TELNET session
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
5218.1 | The REMOTE (HP) sent a FIN | LASSIE::GEMIGNANI | Tue Feb 18 1997 16:56 | 39 | |
I looked into UCXTRACE2.LOG, and found that UCX received: UCX INTERnet trace RCV packet seq # = 414 at 7-FEB-1997 18:58:13.19 IP Version = 4, IHL = 5, TOS = 00, Total Length = 552 = ^x0228 IP Identifier = ^x64B7, Flags (0=0,DF=1,MF=0), Fragment Offset = 0 = ^x0000, Calculated Offset = 0 = ^x0000 IP TTL = 57 = ^x39, Protocol = 6 = ^x06, Header Checksum = ^x0DC3 IP Source Address = 3.82.8.236 IP Destination Address = 156.30.29.2 TCP Source Port = 10240, TCP Destination Port = 3455 TCP Sequence Number = 399657465 = ^x17D249F9 TCP Acknowledge Number = 355968112 = ^x1537A470 TCP Data Offset = 05, Calculated Offset = 20 = ^x14 Flags (URG=0,ACK=1,PSH=1,RST=0,SYN=0,FIN=1), Window = 32768 = ^x8000 TCP Checksum = ^x4879, Urgent Pointer = 0 = ^x0001 To which UCX replied: UCX INTERnet trace XMT packet seq # = 440 at 7-FEB-1997 18:58:18.16 IP Version = 4, IHL = 5, TOS = 00, Total Length = 40 = ^x0028 IP Identifier = ^xBBF5, Flags (0=0,DF=0,MF=0), Fragment Offset = 0 = ^x0000, Calculated Offset = 0 = ^x0000 IP TTL = 128 = ^x80, Protocol = 6 = ^x06, Header Checksum = ^xB67F IP Source Address = 156.30.29.2 IP Destination Address = 3.82.8.236 TCP Source Port = 3455, TCP Destination Port = 10240 TCP Sequence Number = 355968112 = ^x1537A470 TCP Acknowledge Number = 399657978 = ^x17D24BFA TCP Data Offset = 05, Calculated Offset = 20 = ^x14 Flags (URG=0,ACK=1,PSH=0,RST=0,SYN=0,FIN=1), Window = 4096 = ^x1000 TCP Checksum = ^x8287, Urgent Pointer = 0 = ^x0000 The FIN=1 indicates the socket was closed (a normal socket shutdown). | |||||
5218.2 | CSC32::D_SANFORD | Wed Feb 19 1997 16:04 | 2 | ||
Thank you for looking at the log, I passed this information onto the customer. -drew |