Last updated on APRIL 08, 2014
Applies to:Oracle Communications OpenSAFfire - Version 6.3.0 and later
Information in this document applies to any platform.
The restart behavior for failed components seems to differ between OpenSAFfire 6.2 and OpenSAFfire 6.3 when using the same redundancy configuration.
When component restarts are disabled, all of SUs are assigned to a single machine.
- In OpenSAFfire 6.2, the SU (Service Unit) will failover and restart up to the amount of times specified by saAmfSgtDefSuRestartMax before triggering the node reboot.
- In OpenSAFfire 6.3, the SU is simply terminated and does not restart. I am unable to get the SU to restart using amf-adm. What is the cause of the behavioural differences, and is there a way to force OpenSAFfire 6.3 to behave as it was in OpenSAFfire 6.2?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms