IZ35329: AGENTS NEVER COME BACK ONLINE AFTER MULTIPLE RTEMS FAILOVERS.

APAR status

• Closed as program error.

Error description

• Approver:  MS
  
  Description:
  
  When the RTEMS reconnects, it retransmits its entire Node Status
  to the Hub.
  If the agent hasn't told the agent that it is off-line, the
  RTEMS will retransmit that the agent is still on-line.
  If that agent has already connected to another TEMS in the
  meantime, though, the on-line status with the new TEMS will be
  overwritten with an on-line status at the old TEMS.
  Because the Hub thinks that the agent has switched back to the
  old TEMS, when the agent's status at the old TEMS finally
  changes to off-line and the status to transmitted to the Hub,
  the off-line status will be honoured.
  
  Because of the fact that a) the RTEMS must lose its connection
  to the Hub b) around the same time that an agent switches and c)
  the status of the agent must remain on-line at the original TEMS
  after the switch and d) its status must be retransmitted before
  it goes off-line at the original TEMS
  

Local fix

• No workaround available.
  

Problem summary

• An Agent can appear offline after it has switched to another
  RTEMS.
  

Problem conclusion

• If an RTEMS loses its connection with the HUB, it will
  rebroadcast its entire node status table to the HUB after the
  connection is reestablished.  If an agent has switch away from
  the RTEMS before the rebroadcast, there is a chance the
  rebroadcast will cause the HUB to believe the agent has switched
  back to the original RTEMS.  When the agent does not send a
  heartbeat to the RTEMS, the RTEMS then marks the agent as
  offline.  The agent actually remains online, but connected to
  the TEMS it switched to.
  
  The code was modified to allow the HUB to know which TEMS an
  agent last sent a heartbeat to.  This allows the HUB to more
  accurately determine where an agent is actually connected.  The
  HUB will ignore online status requests for an agent when the
  online status is older than the latest one received.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | interim fix | 6.2.0.2-TIV-ITM-IF0001
  

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:

  OA27965 OA29321

Fix information

• Fixed component name

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels

• R620 PSY

     UP