IBM Support

PI57886: SYN-ACK RESPONSE MAY CONTAIN TSOPT WHEN IT SHOULD NOT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • z/VM TCP/IP is always using the TSopt and including a timestamp
    in the SYN-ACK packet that it sends back to any incoming SYN
    packet. According to RFC 7323, a TCP should only send a TSopt
    in the SYN-ACK if it received a TSopt in the initial SYN packet
    that it received for the connection.  There are some instances
    where this "invalid" SYN-ACK that gets sent back will get
    discarded by the TCP system that is attempting to connect.
    This results in the connection attempt timing out.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the z/VM TCP/IP stack           *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION: APPLY PTF                                    *
    ****************************************************************
    z/VM TCP/IP is always using the TSopt and including a timestamp
    in the SYN-ACK packet that it sends back to any incoming SYN
    packet. According to RFC 7323, a TCP should only send a TSopt
    in the SYN-ACK if it received a TSopt in the initial SYN packet
    that it received for the connection.  There are some instances
    where this "invalid" SYN-ACK that gets sent back will get
    discarded by the TCP system that is attempting to connect.
    This results in the connection attempt timing out.
    

Problem conclusion

  • When sending the SYN_ACK packet out, the updated code will check
    whether it has received a TSopt in the initial SYN packet that
    it received for the connection. If not, the SYN_ACK packet will
    not contain TSopt.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI57886

  • Reported component name

    TCP/IP V2 FOR V

  • Reported component ID

    5735FAL00

  • Reported release

    620

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-02-23

  • Closed date

    2016-03-03

  • Last modified date

    2016-12-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UI35843 UI35844 UI35845

Modules/Macros

  • FPTCPDOW F6TCPDOW
    

Fix information

  • Fixed component name

    TCP/IP V2 FOR V

  • Fixed component ID

    5735FAL00

Applicable component levels

  • R540 PSY UI35843

       UP16/03/03 I 1000

  • R620 PSY UI35844

       UP16/03/03 I 1000

  • R630 PSY UI35845

       UP16/12/02 P 1602

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27N","label":"APARs - VM\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"620","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"620","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
02 December 2016