PH32085: LB DOES NOT COMPUTE STICKYMASK CORRECTLY

APAR status

• Closed as program error.

Error description

• When customer use stickymask, LB does not apply it to source
  network ip address.
  As result, LB considers some requests
  (client ip address belongs to same segment) as new affinity and
  forwards them to different backend server.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server Load       *
  *                  Balancer for IPv4 and IPv6 users            *
  ****************************************************************
  * PROBLEM DESCRIPTION: Affinity not working as expected with   *
  *                      LB stickymask setting.                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  With LB's stickymask feature, client affinity is grouped based
  on the client's IP address and the stickymask setting.
  Affinity is not grouped as expected when stickymask is used.
  

Problem conclusion

• The stickymask was not set in the executor code. The executor
  selects a server and without the stickymask information,
  server selection was based upon the entire client IP address
  instead of the IP group created when the stickymask is applied.
  
  Fix levels:
     8.5.5.19
     9.0.5.7
  

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