IV36811: MIRROR TEMS EXHIBITS HIGH CPU UTILIZATION

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

APAR status

• Closed as program error.

Error description

• PROBLEM DESCRIPTION:
  The MIRROR Tivoli Enterprise Monitoring Server will exhibit a
  spike in CPU utilization every three (3) minutes. The duration
  of the spike increases over time until the TEMS performance is
  impacted servicing its functionality
  
  RECREATE INSTRUCTIONS:
  
  1. Install two (2) TEMS  with FTO enabled.
  2. Install OS Agent on endpoint
  3. Add 623 FP2 UM Agent to HUB TEMS Depot
  4. Execute 100 tacmd updateAgent -t UM -v 062302000 -n
  <endpoint:LZ>
  5. Monitor CPU utilization of Backup HUB.
  6. Observe duration of CPU Utilization increases every three (3)
  minutes over 1 hour time.
  

Local fix

• 1. Apply workaround solution IZ52198 supplied by IBM Support to
  RTEMS, HUB and MIRROR TEMS.
  
  2. Enable automated cleardeploystatus capability for 1 hour
  intervals.
  

Problem summary

• The mirror monitoring server will exhibit a spike in CPU
  utilization every three (3) minutes. The duration of the spike
  increases over time until the monitoring server's ability to
  function normally is impacted.
  
  The algorithm that executes on the mirror monitoring server
  acquires the list of deploy transactions contained on each
  remote monitoring server from the hub monitoring server every
  three minutes. The algorithm incorrectly treats the hub
  monitoring server as a remote and includes the deploy
  transactions from the hub in its list. As a result, the number
  of deploy transactions that are evaluated every three minutes
  doubles in size and takes increasing CPU cycles to process.
  

Problem conclusion

• Revise the algorithm processing on the mirror monitoring server
  to exclude the hub monitoring server from its list.
  
  The fix for this APAR is contained in the following maintenance
  packages:
  | fix pack | 6.2.3-TIV-ITM-FP0005
  

Temporary fix

• Execute the tacmd cleardeploystatus command frequently to reduce
   the number of deploy transactions that are on the list.
  

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

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels

• R623 PSY

     UP