- **status**: accepted --> review
- **Comment**:
Published updated AMF PR doc.
---
** [tickets:#1251] In 2n model, saAmfSGNumPrefInserviceSUs doesn't instantiate
SUs as per default value when unset.**
**Status:** review
**Milestone:** 4.6.1
**Created:** Mon Feb 09, 2015 10:28 AM UTC by Syed Shareef Ali
**Last Updated:** Tue May 05, 2015 05:38 AM UTC
**Owner:** Praveen
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
2. Perform unlock-instantiation and unlock of each SUs.
3. 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.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
