IZ75365: ABSTRACT: HIGH TEMS CPU AFTER RESTART WITH WPAS CONFIGURED.

IBM Tivoli Monitoring 6.2.2 Fix Pack 8 (6.2.2-TIV-ITM-FP0008)
IBM Tivoli Monitoring 6.2.2 Fix Pack 9 (6.2.2-TIV-ITM-FP0009)
IBM Tivoli Monitoring 6.2.2 Fix Pack 6 (6.2.2-TIV-ITM-FP0006)

APAR status

• Closed as program error.

Error description

• Environment: ITM 6.2.2 FP01 Red Hat Linux.
  
  
  
  Due to a defect in the TEMS KRANDREG module, the RTEMS can go
  into a
  loop making continuous calls to the ITM Global Location Broker
  facility.
  This loop can happen whenever the HUB TEMS Global Location
  Broker
  contains EXACTLY 50 entries relating to the ITM Warehouse Proxy
  Agent.
  
  The Global Location Broker is the HUB TEMS facility that shows
  which     Page 22 of 30
  RTEMS or Warehouse Proxy Agents have been registered in this
  environment.
  
  The total number of entries registered in the HUB TEMS Global
  Location
  Broker from the WPA agent are a combination of:
  1)  the number of ITM network protocols configured for the WPA
  agent
  (i.e. IP.PIPE, IP.SPIPE, etc)
  2) the number of network interface cards resident on any of the
  WPA
  agent machines
  3) the total number of WPA agents that have been configured and
  connected to the HUB TEMS
  
  The Global Location Broker entries for the WPA can look like
  this.
  This example is from an RTEMS RAS1 log when the RTEMS has the
  configuration parameters KDC_DEBUG=Y and KDE_DEBUG=Y set in its
  environment.
  

Local fix

• - stopped all WPA, RESULT: HUB CPU utilization was around 4% in
  avg.
  - started all WPAs again: HUB CPU utilization was around 80% in
  avg.
  - stopped WPAs again
  - reconfigured each WPA to bind only to one NIC interface
  - reconfigured each WPA to use only IP.PIPE protocol
  and restarted all WPAs.
  Now HUB is using less CPU (approximately 4% in avarage). Thats
  OK.
  

Problem summary

• High CPU utilization on a remote management server where the
  warehouse proxy agent is configured and the global location
  broker contains exactly 50 entries related to the warehouse
  proxy agent.
  
  The warehouse proxy on the remote management server goes into an
  infinite loop if the number of location broker entries is
  exactly 50.  This caused the high CPU usage on the management
  server.
  

Problem conclusion

• The code was changed so that the number of global broker entries
  defaults to 128 to keep it in sync with the maximum number of
  entries that can exist thus preventing the code from looping
  indefinitely.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
    | fix pack | 6.2.2-TIV-ITM-FP0003
  

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:

  OA34168

Fix information

• Fixed component name

  TEMA

• Fixed component ID

  5724C04TE

Applicable component levels

• R622 PSY

     UP