APAR status
Closed as program error.
Error description
syslog-tcp and nfs type log targets may be susceptible to unexpected reloads after processing 4 billion messages, while trying to access a log target that no longer exists.
Local fix
Restart DataPower before any syslog-tcp or NFS log targets reach 4 billion events. Can check current number in the WebGUI: Main > Log Target Status, Processed Events column
Problem summary
An incorrect count occuring on each event subscribed log messages on syslog-tcp or nfs targets would increment a counter. If this counter rolled over a deletion of the target may occur and and unexpected reload of the device would occur.
Problem conclusion
Resolve the incorrect count. Fixed in: 2018.4.1.18 10.0.1.5
Temporary fix
run show logging status, if a syslog-tcp or nfs type log target is approaching 4 billion processed events either restart the device or disable and reinable the impacted log targets.
Comments
APAR Information
APAR number
IT37506
Reported component name
DATAPOWER
Reported component ID
DP1234567
Reported release
18X
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-07-27
Closed date
2021-09-27
Last modified date
2021-09-27
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
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateways"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"18X"}]
Document Information
Modified date:
28 September 2021