Migrated from http://devel.opensaf.org/ticket/2700
saAmfSGNumPrefActiveSUs & saAmfSGNumPrefStandbySUs attributes are mandatory for N+M, but if it is not configured AMF is setting it to 1.
Changed 11 months ago by hafe ¶
Need to be careful about backwards compatibility here. From this point I don't think we can add failing configuratoin validation, we can just produce warning logs and apply default values.
The following log will come if saAmfSGNumPrefActiveSUs and saAmfSGNumPrefStandbySUs are not configured:
osafamfd[16914]: NO 'saAmfSGNumPrefActiveSUs' is set to 1, not useful for NpM
osafamfd[16914]: NO 'saAmfSGNumPrefStandbySUs' is set to 1, not useful for NpM
Last edit: Nagendra Kumar 2015-07-02
changeset: 6685:cbd2b74ec3e3
branch: opensaf-4.5.x
parent: 6682:3ae8ccf11dbb
user: Nagendra Kumarnagendra.k@oracle.com
date: Fri Jul 24 15:13:49 2015 +0530
summary: amfd: log about invalid configuration of saAmfSGNumPrefActiveSUs/StandbySUs [#296]
changeset: 6686:0ee16330fe07
branch: opensaf-4.6.x
parent: 6683:41d92623b0f2
user: Nagendra Kumarnagendra.k@oracle.com
date: Fri Jul 24 15:14:25 2015 +0530
summary: amfd: log about invalid configuration of saAmfSGNumPrefActiveSUs/StandbySUs [#296]
changeset: 6687:3005fa42ddcb
tag: tip
parent: 6684:87efd95dc3ee
user: Nagendra Kumarnagendra.k@oracle.com
date: Fri Jul 24 15:14:35 2015 +0530
summary: amfd: log about invalid configuration of saAmfSGNumPrefActiveSUs/StandbySUs [#296]
[staging:cbd2b7]
[staging:0ee163]
[staging:3005fa]
Related
Tickets:
#296