IT24941: A LOG TARGET STATUS MEMORY VALUE IS NOT CORRECT, ALWAYS BEING TOO LOW

Fix packs for DataPower Gateway version 7.7
Fix packs for DataPower Gateway version 7.5
Fix packs for DataPower Gateway version 7.5.1
Fix packs for DataPower Gateway version 7.5.2
Fix packs for DataPower Gateway version 7.6

APAR status

• Closed as program error.

Error description

• The user observed slowly increasing memory usage but struggled
  to pinpoint which part of configuration or traffic caused this.
  It turned out that having log target Identical Event Detection
  enabled, especially in combination with log target type
  syslog-tcp, did hold memory for a long time, as in this
  specific scenario many unique log records got created and where
  hold even beyond the Identical Event Detection timeout.
  It turned out this part of hold memory is not captured in the
  log target status provider, so customer could not pinpoint this
  specific log target to be the driver.
  

Local fix

• Either shortly disable/enable the log target object to reclaim
  hold memory,
  or do not use Identical Event Detection (a preferred practice
  anyway to safe resources on DataPower),
  or more specifically don't use Identical Event Detection if the
  log target type is syslog-tcp.
  

Problem summary

• The logging target status might not reflect actual memory used.
  

Problem conclusion

• Fix is available in 7.5.0.16, 7.5.1.15, 7.5.2.15, 7.6.0.8 and
  7.7.1.1
  For a list of the latest fix packs available, please see:
  http://www-01.ibm.com/support/docview.wss?uid=swg21237631
  

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

  DATAPOWER

• Fixed component ID

  DP1234567

Applicable component levels

• R750 PSY

     UP

• R751 PSY

     UP

• R752 PSY

     UP

• R760 PSY

     UP

• R770 PSY

     UP