OpenSAFfire AMF Fails to Correctly Derive a Default Value for saAmfSGNumPrefInserviceSUs Resulting in Components not Restarting after a Node Reboot

(Doc ID 1494311.1)

Last updated on MAY 05, 2016

Applies to:

Oracle Communications OpenSAFfire - Version 1.0 to 6.2.0 [Release 1.0 to 6.2.0]
Generic Linux


In OpenSAFfire versions earlier than 6.2 (inclusive), AMF (Application Management Framework) fails to correctly derive a default value for SaAmfSG.saAmfSGNumPrefInserviceSUs.

This results in AMF not restarting the component in the SG/SU (Service Unit/Service Group) when the node hosting the component rejoins the cluster.

Here is an example log exert (note there is no ACTIVE SI assignment by AMF when the node rejoins the OpenSAFfire cluster):

As per Figure 32 in the SA Forum specification SAI-AIS-AMF-B.04.01.AL, if unset or unconfigured, the default value of saAmfSGNumPrefInserviceSUs should be the number of SUs configured in the SG.


The saAmfSGNumPrefInserviceSUs parameter in the IMM configuration is not configured and the node hosting the component rejoins the cluster (due to OpenSAFfire restart or node reboot recovery etc).


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms