#1251 In 2n model, saAmfSGNumPrefInserviceSUs doesn't instantiate SUs as per default value when unset.

[Syed Shareef Ali]

In 2n model, saAmfSGNumPrefInserviceSUs doesn't instantiate SUs as per default value when unset.

Steps:-
1. Runtime bring up 2N redundancy model with following configuration.
a) 3SUs in lock-instantiation state & each SU having 3 PI components.Each SUs spawned on PL-4.
b) 3SIs in unlocked state & each SI having 3 CSIs.
c) SG in unlock state, saAmfSGNumPrefInserviceSUs=3

1. Perform unlock-instantiation and unlock of each SUs.
2. Runtime unset the saAmfSGNumPrefInserviceSUs from 3 to <Empty>

It was observed that after step2, all 3SUs got instantiated.
However after step3 also, it was observed that 3 SUS was in instantiated state which was wrong because when saAmfSGNumPrefInserviceSUs gets unset, it should take default value of saAmfSGNumPrefInserviceSUs which is 2 for 2N model as per AMF B4.1 spec page 123.

[Praveen]

Published updated AMF PR doc.

[Praveen]

Documented in the changeset:

changeset: 161:d45c07d6375c
branch: opensaf-4.5.x
parent: 148:3ce1d815cb2b
user: praveen.malviya@oracle.com
date: Thu Oct 22 10:10:42 2015 +0530
summary: amf: updates for 4.5 branch for [#315,#1251 and #1328]

changeset: 162:953ce37c31cf
branch: opensaf-4.6.x
parent: 156:985aa15a50d0
user: praveen.malviya@oracle.com
date: Thu Oct 22 10:12:44 2015 +0530
summary: amf: updates for 4.6 branch for [#315,#1251 and #1328]

changeset: 163:e17b9c98f6ea
tag: tip
parent: 160:64fd88acc540
user: praveen.malviya@oracle.com
date: Thu Oct 22 10:19:34 2015 +0530
summary: amf: updates for 4.7