PH57722: The high availability heartbeat status reported in the Load Balancer's hamon.log file is not correct.

APAR status

• Closed as program error.

Error description

• Load Balancer logs the following data in hamon.log when
  logging is set to verbose:
  
  Heartbeat Status:
  -----------------
  Count ................ 1
  
  Source[1] ............ <local_ip_address>
  Destination[1] ....... <remote_ip_address>
  Status[1] ............ <status>
  The Status may indicate OK, trying, unavailable, or down.
  
  The status is the neighbor state of the destination address and
  not the heartbeat status.  The neighbor state is determined
  when the Load Balancer is started and does not change. The
  heartbeat status may be bad when the status indicates OK and
  the beartbeat status may be good when the status indicates
  unavailable or down.
  

Local fix

• Local fix is to ignore the "Status[1] ............ 70
  (Unavailable - server down)" line
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Load Balancer users with      *
  *                  high availability configured                *
  ****************************************************************
  * PROBLEM DESCRIPTION: The high availability log file          *
  *                      (hamon.log) does not report an          *
  *                      accurate heartbeat status.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The heartbeat status reports the neighbor state status rather
  than the heartbeat status. The neighbor state indicates if
  the Load obtained the MAC address of the destination IP
  address. The MAC address is not necessary for heartbeat
  packets and the status is irrelevent with regards to the
  heartbeat health.
  

Problem conclusion

• Logging has been corrected to indicate the number of seconds
  that have elapsed since the last heartbeat was received. In
  most cases, the value will be 0 seconds that indicates a good
  health. The time since the last heartbeat was received applies
  to all heartbeats and is not tracked for individual heartbeats
  when multiple heartbeats are defined.
  
  Fix levels:
     8.5.5.25
     9.0.5.18
  

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