Analysis:
1)AMFD sends quiesced assignment for all SIs to SU1.
2)AMFD received SU level quiesced response for SU1, SU level
active sent to SU2.
status of counters:
Dec 19 12:33:35.987742 osafamfd [6180:si.cc:1329] TR safSi=SI1,safApp=test2nApp 

saAmfSINumCurrActiveAssignments=1
Dec 19 12:33:35.987765 osafamfd [6180:si.cc:1333] TR safSi=SI1,safApp=test2nApp 

saAmfSINumCurrStandbyAssignments=0

Dec 19 12:33:35.989745 osafamfd [6180:si.cc:1329] TR safSi=SI2,safApp=test2nApp 

saAmfSINumCurrActiveAssignments=1
Dec 19 12:33:35.989757 osafamfd [6180:si.cc:1333] TR safSi=SI2,safApp=test2nApp 

saAmfSINumCurrStandbyAssignments=0

Dec 19 12:33:35.991553 osafamfd [6180:si.cc:1329] TR safSi=SI3,safApp=test2nApp 

saAmfSINumCurrActiveAssignments=1
Dec 19 12:33:35.991576 osafamfd [6180:si.cc:1333] TR safSi=SI3,safApp=test2nApp 

saAmfSINumCurrStandbyAssignments=0

Dec 19 12:33:35.993264 osafamfd [6180:si.cc:1329] TR safSi=SI4,safApp=test2nApp 

saAmfSINumCurrActiveAssignments=1
Dec 19 12:33:35.993297 osafamfd [6180:si.cc:1333] TR safSi=SI4,safApp=test2nApp 

saAmfSINumCurrStandbyAssignments=0



3)AMFD received disabled event for Su2 , AMF sent SU level delete in SU1. Also 
SUSIs are 
deleted in SU2.
For deletion counters are updated only for active and standby states after 
receving the 

response.

Since all the SUSIs are in modeify state in SU2, counters are not updated for 
any SIs 

while deleting SUSIs in SU2. Relevent AMF code
  if (susi->fsm == AVD_SU_SI_STATE_MODIFY) {
                        /* Dont delete here, if i am in modify state.
                           only happens when active -> qsd and standby rebooted 
*/
                } else if ((susi->fsm == AVD_SU_SI_STATE_ASGND) || (susi->fsm 
== 

AVD_SU_SI_STATE_ASGN)){
                        if (SA_AMF_HA_STANDBY == susi->state) {
                                avd_su_dec_curr_stdby_si(susi->su);
                                avd_si_dec_curr_stdby_ass(susi->si);
                        } else if ((SA_AMF_HA_ACTIVE == susi->state) || 

(SA_AMF_HA_QUIESCING == susi->state)) {
                                avd_su_dec_curr_act_si(susi->su);
                                avd_si_dec_curr_act_ass(susi->si);
                        }
                }
}

4)AMF received enabled event for SU2, AMF sends instantiation event to SU2.
5)AMFD received delete response for SU1, SUSIs are deleted and SG made stable.
6)AMFD received enabled event for instantiation for SU2, freshly assigned 
active for all
SIs in SU2.
In this case status of active counters for all SIs:
Dec 19 12:33:36.727995 osafamfd [6180:si.cc:1295] TR safSi=SI1,safApp=test2nApp 

saAmfSINumCurrActiveAssignments=2
Dec 19 12:33:36.730463 osafamfd [6180:si.cc:1295] TR safSi=SI2,safApp=test2nApp 

saAmfSINumCurrActiveAssignments=2
Dec 19 12:33:36.732337 osafamfd [6180:si.cc:1295] TR safSi=SI3,safApp=test2nApp 

saAmfSINumCurrActiveAssignments=2
Dec 19 12:33:36.734698 osafamfd [6180:si.cc:1295] TR safSi=SI4,safApp=test2nApp 

saAmfSINumCurrActiveAssignments=2

Here counters went beyond their 2N model limit for all the SIs
7)AMFD received active assignments for SIs.
8)Unlock of Su1 leads to successful standby assignment in SU1 for all SIs.


The issue is same as #666 with the difference that in #666 SI dep is configured 
and 

shutdown operation was performed instead of lock. In both the cases quiescing 
or quiesced  
assignments were successful, which means SUSIs are quiesced and thus SU is now 
in locked state.
After this both shutdown and lock operation behaves similarly i.e active 
assignment in SU2 and removal of assignment in Su1. Also in both the issues 
fault occurred during active assignment. 
This makes both of these issue similar and thus fix for #666 will also be 
applicable for #678.

Based on this analysis, marking #678 ticket as duplicate of #666. 
Also #666 will be updated to be reproducible without SI dependency and with 
lock operation.



---

** [tickets:#678] lock/unlock of su with faults results in SI's assgnState 
partially assigned**

**Status:** duplicate
**Created:** Thu Dec 19, 2013 07:12 AM UTC by surender khetavath
**Last Updated:** Thu Jan 02, 2014 07:18 AM UTC
**Owner:** Praveen

changeset : 4733
model : 2n
configuration : 1App,1SG,2SUs with 4comps each, 4SIs with 1 CSI each
si-si deps not configured. 
SU1 is active, SU2 is standby.
SU1 is mapped to pl-3 and SU2 to pl-4
saAmfSGAutoRepair=1(True)
SuFailover=1(True)

test:
1.lock of active su1
2.sponsor SI reject the active assignment as SU2
3. unlock the SU1

states:
safSISU=safSu=SU1\,safSg=SG\,safApp=test2nApp,safSi=SI3,safApp=test2nApp
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=SG\,safApp=test2nApp,safSi=SI3,safApp=test2nApp
        saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=SG\,safApp=test2nApp,safSi=SI1,safApp=test2nApp
        saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU1\,safSg=SG\,safApp=test2nApp,safSi=SI4,safApp=test2nApp
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=SG\,safApp=test2nApp,safSi=SI2,safApp=test2nApp
        saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU1\,safSg=SG\,safApp=test2nApp,safSi=SI2,safApp=test2nApp
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=SG\,safApp=test2nApp,safSi=SI1,safApp=test2nApp
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=SG\,safApp=test2nApp,safSi=SI4,safApp=test2nApp
        saAmfSISUHAState=STANDBY(2)


safSi=SI1,safApp=test2nApp
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3)
safSi=SI2,safApp=test2nApp
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3)
safSi=SI3,safApp=test2nApp
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3)
safSi=SI4,safApp=test2nApp
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3)



---

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.
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to