IC86817: FALSE SLM TRIGGER POSSIBLE IF MESSAGE COUNT MONITORS ARE IN USE WHEN UPTIME VALUE EXCEEDS MAXIMUM

Fix packs for DataPower XML Security Gateway appliances version 3.8.2
Fix packs for DataPower Integration appliances version 3.8.2
Fix packs for DataPower B2B Appliance XB60 version 3.8.2
Fix packs for DataPower Low Latency Appliance version 3.8.2
Fix packs for DataPower XML Security Gateway appliances version 4.0.1
Fix packs for DataPower Integration appliances version 4.0.1
Fix packs for DataPower B2B appliances version 4.0.1
Fix packs for DataPower Low Latency Appliance version 4.0.1
Fix packs for DataPower XML Security Gateway appliances version 4.0.2
Fix packs for DataPower Integration appliances version 4.0.2
Fix packs for DataPower B2B appliances version 4.0.2
Fix packs for DataPower Low Latency Appliance version 4.0.2
Fix packs for DataPower Service Gateway appliances version 4.0.2
Fix packs for DataPower Low Latency Appliance version 5.0
Fix packs for DataPower B2B appliances version 5.0
Fix packs for DataPower Integration appliances version 5.0
Fix packs for DataPower XML Security Gateway appliances version 5.0
Fix packs for DataPower Service Gateway appliances version 5.0
Fix packs for DataPower Service Gateway XG45 Virtual Edition version 5.0
Fix packs for DataPower Integration Appliance XI52 Virtual Edition version 5.0

APAR status

• Closed as program error.

Error description

• If the DataPower uptime wraps while message counts are being
  monitored for IP's with long delays between logins, SLM can
  trigger when its message count has not actually been reached.
  
  The symptom will be intermittent, obviously incorrect SLM
  triggering, shutting out an IP which has not exceeded its
  message count limit.
  

Local fix

• A possible workaround is to restart the DataPower appliance
  periodically to reset the Uptime: every 24 days for an XI50 or
  every 49 days for an XI52.
  

Problem summary

• Affected is the use of count monitors.
  
  Count monitors might get triggered even though
  the actual traffic is coming at a rate significantly below
  the specific rate limit.
  
  This happens when you are trying to sending a series of
  transactions that pass certain points of times (about every 25
  or 50 days, depending on firmware releases). Once
  triggered, all following transactions will be rejected. It will
  not recover without a shutdown reload.
  

Problem conclusion

• The fix is available in 3.8.2.16, 4.0.1.14, 4.0.2.10, 5.0.0.4
  
  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

• R382 PSN

     UP

• R401 PSN

     UP

• R402 PSN

     UP

• R500 PSN

     UP