saAmfSURestartCount and saAmfCompRestartCount Not Reset after Probation Period Expiration
(Doc ID 1663005.1)
Last updated on NOVEMBER 05, 2019
Applies to:
Oracle Communications OpenSAFfire - Version 6.3.0 and laterInformation in this document applies to any platform.
Symptoms
In OpenSAFfire 6.3.0, when viewing the saAmfSURestartCount and saAmfCompRestartCount runtime attributes via immlist, neither appear to reset after the appropriate restart probation period has expired or the recovery escalation algorithm has completed and the system has returned to a steady state.
These values are used to track the number of times the Service Unit (SU) or Component has been restarted since first stage of recovery was undertaken by the Application Management Framework (AMF).
The component/SU recovery should be escalated to the next level when:
saAmfSURestartCount exceeds SaAmfSG.saAmfSGSuRestartMax within SaAmfSG.saAmfSGSuRestartProb
For example (assume two component restarts is escalated to a SU restart and two SU restarts is escalated to SU failover:
1. Initial saAmfSURestartCount before any system failures
Changes
Component/SU failure resulting in restart actions being taken by AMF.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |