Documentation associated with this issue:
In 2N model, if shutdown operation is issued on SI and fault occurs for the 
quiescing state such that it leads to fail-over of SU then:
1) AMF will keep the SI assigned with admin state UNLOCKED if no SI dependency 
is configured within SU.
2) AMF will  move SI to LOCKED state if SI dependency is configured within SU. 
SI will no longer be assigned.


---

** [tickets:#490] amf: Shutdown operation on SI with faults still shows 
assignments.**

**Status:** review
**Created:** Mon Jul 08, 2013 04:51 AM UTC by Praveen
**Last Updated:** Fri Sep 06, 2013 01:14 PM UTC
**Owner:** Praveen

changeset: 4334:f712a76ddda5 (opensaf-4.3.x).

configuration:
 2N model with 1 SG, 2 SIs with 2 csis in each, 3 SUs with 2 comps in each.
 Components have componentfailover as recovery policy.

Steps to reproduce:
 1) Perform shutdown operation on any SI1.
 2) Reject the assignments.
 3) AMF will make standby SU active and spare SU standby for both the SIs, even 
though it shows SI1 in Locked state.



SI is in Locked state:
safSi=SC-2N,safApp=OpenSAF
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=FULLY_ASSIGNED(2)
safSi=NoRed2,safApp=OpenSAF
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=FULLY_ASSIGNED(2)
safSi=NoRed1,safApp=OpenSAF
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=FULLY_ASSIGNED(2)
safSi=AmfDemo,safApp=AmfDemo1
        saAmfSIAdminState=LOCKED(2)
        saAmfSIAssignmentState=FULLY_ASSIGNED(2)
safSi=AmfDemo1,safApp=AmfDemo1
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=FULLY_ASSIGNED(2)

But still AMF assigns it:
safSISU=safSu=SC-1\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed1,safApp=OpenSAF
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SC-1\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SC-2\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed2,safApp=OpenSAF
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SC-2\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF
        saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
        saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
        saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
        saAmfSISUHAState=ACTIVE(1)



---

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.
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to