PH36996: FRAGMENTED TRAFFIC NOT BEING FORWARDED THROUGH THE LOAD BALANCER

APAR status

• Closed as program error.

Error description

• IPv4 fragmented traffic is not forwarded through the load
  balancer. Packet counts do not indicate that the packets are
  discarded or in error.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server Load       *
  *                  Balancer users                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Fragmented traffic is not forwarded.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When Load Balancer receives fragment packets, it does not
  forward the traffic to the backend servers.
  

Problem conclusion

• The Load Balancer selects the backend server based upon the
  first fragment which is indicated in the packet with a
  fragment offset of 0 and the 'more fragments' bit set.  The
  Load Balancer was not correctly detected the first fragment so
  it never selecting a server and never forwarding the
  fragmented traffic.
  
  Fix levels:
     8.5.5.20
     9.0.5.9
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  WS EDGE LB IPV4

• Fixed component ID

  5724H8812

Applicable component levels