IV51512: TEPS CRASHES DURING A TOPOLOGY UPDATE

IBM Tivoli Monitoring 6.2.3 Fix Pack 5 (6.2.3-TIV-ITM-FP0005)

APAR status

• Closed as program error.

Error description

• When a new log file agent comes online, the TEPS crashes during
  the physical topology update to add the new node.
  

Local fix

• Removing one of the systems that are using the same IP address
  will likely resolve the crash.
  

Problem summary

• At random, the portal server crashes and generates a core dump.
  Analysis of the stack trace shows the portal server was
  performing a topology update operation due to a new managed
  system coming online for the first time.
  

Problem conclusion

• Modified code to look up managed objects by ID during a topology
   update operation instead of storing a pointer to the managed
  object.
  
  The fix for this APAR is contained in the following maintenance
  packages:
  | fix pack | 6.2.3-TIV-ITM-FP0005
  

Temporary fix

• The crash is due to the presence of two managed systems with the
   same IP address but on different platforms (ex. Linux and
  Windows). This could occur if an old system was decommissioned
  and it's IP address reused for a new system on a different
  platform, but the old system's node status record was left in
  the management server's node status table. Removing the old
  server's node status record will alleviate the problem.
  

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

  TEPS

• Fixed component ID

  5724C04PS

Applicable component levels

• R623 PSY

     UP