Analyses:

1) Issue of lock operation:

Dec 17 18:42:20.518547 osafamfd [6784:lga_api.c:0903] << saLogWriteLogAsync
Dec 17 18:42:20.518584 osafamfd [6784:su.cc:0875] >> su_admin_op_cb: 
399431958529, 'safSu=SU1,safSg=SG,safApp=test2nApp', 2
Dec 17 18:42:20.518607 osafamfd [6784:su.cc:0813] >> 
avd_su_readiness_state_set: 'safSu=SU1,safSg=SG,safApp=test2nApp' OUT_OF_SERVICE

2) Before the lock operation itself assignment counters were incorrect, this 
reflects when AMF given quiesced assignments

SI2-SI4 are going from  partially assigned state to fully assigned state:

Dec 17 18:42:20.523525 osafamfd [6784:si.cc:1303] TR safSi=SI2,safApp=test2nApp 
saAmfSINumCurrActiveAssignments=1
Dec 17 18:42:20.523835 osafamfd [6784:si.cc:1258] TR 
'safSi=SI2,safApp=test2nApp' PARTIALLY_ASSIGNED => FULLY_ASSIGNED
Dec 17 18:42:20.530048 osafamfd [6784:si.cc:1303] TR safSi=SI3,safApp=test2nApp 
saAmfSINumCurrActiveAssignments=1
Dec 17 18:42:20.530561 osafamfd [6784:si.cc:1258] TR 
'safSi=SI3,safApp=test2nApp' PARTIALLY_ASSIGNED => FULLY_ASSIGNED
Dec 17 18:42:20.540172 osafamfd [6784:si.cc:1303] TR safSi=SI4,safApp=test2nApp 
saAmfSINumCurrActiveAssignments=1
Dec 17 18:42:20.540388 osafamfd [6784:si.cc:1258] TR 
'safSi=SI4,safApp=test2nApp' PARTIALLY_ASSIGNED => FULLY_ASSIGNED

while SI1 is going from Fully assigned to partially assigned:
Dec 17 18:42:20.578628 osafamfd [6784:si.cc:1303] TR safSi=SI1,safApp=test2nApp 
saAmfSINumCurrActiveAssignments=0
Dec 17 18:42:20.579002 osafamfd [6784:si.cc:1258] TR 
'safSi=SI1,safApp=test2nApp' FULLY_ASSIGNED => PARTIALLY_ASSIGNED


AMF handled operation and its fault during the operation correctly. Since 
counters were not proper in the beginning, mismatch will surely happen after 
completion of operation.

AMF events during the operation:
1)After lock quiesced assignments to dependents.
2)Response of dependents and then Quiesced to sponsor SI1.
3)Quiesed response for SI1, Active for sponsor SI1 in SU2
4)Response for SI1 from SU2 for active state, AMF sent active for SI2-SI3 in 
SU2.
5)After getting active response for SI2-SI4, deletion in SU1.
6)During deletion fault in SU1 leads to su-Failover. 
AMFD deletes all the SUSIs, performed repair correctly.
In all these events AMF handling was correct.

Please test this by bringing system and application freshly and then performing 
operation/fault. 



---

** [tickets:#667] Assignment states of dependent sis show partially assigned**

**Status:** unassigned
**Created:** Tue Dec 17, 2013 01:22 PM UTC by surender khetavath
**Last Updated:** Thu Dec 19, 2013 12:56 PM UTC
**Owner:** nobody

changeset : 4733
model : 2n
configuration : 1App,1SG,2SUs with 4comps each, 4SIs with 1 CSI each
si-si deps configured as SI1 sponsor for SI2,3,4 resp
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. SI1 rejects the CSIRemoval cbk
3. unlock the SU1

/var/log/messages on pl-3:

Dec 17 18:42:19 PL-3 osafamfnd[4099]: NO saAmfSUFailover is true for 
'safSu=SU1,safSg=SG,safApp=test2nApp'
Dec 17 18:42:19 PL-3 osafamfnd[4099]: NO 
'safComp=COMP1,safSu=SU1,safSg=SG,safApp=test2nApp' faulted due to 
'csiRemovecallbackFailed' : Recovery is 'suFailover'
Dec 17 18:42:19 PL-3 osafamfnd[4099]: NO Terminating components of 
'safSu=SU1,safSg=SG,safApp=test2nApp'(abruptly & unordered)
Dec 17 18:42:19 PL-3 osafamfnd[4099]: NO 'safSu=SU1,safSg=SG,safApp=test2nApp' 
Presence State INSTANTIATED => TERMINATING
Dec 17 18:42:19 PL-3 logger: CLC-CLI spawnd cleanup for 
safComp=COMP1,safSu=SU1,safSg=SG,safApp=test2nApp 
Dec 17 18:42:19 PL-3 logger: CLC-CLI spawnd cleanup for 
safComp=COMP2,safSu=SU1,safSg=SG,safApp=test2nApp 
Dec 17 18:42:19 PL-3 logger: CLC-CLI spawnd cleanup for 
safComp=COMP4,safSu=SU1,safSg=SG,safApp=test2nApp 
Dec 17 18:42:19 PL-3 logger: CLC-CLI spawnd cleanup for 
safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp 
Dec 17 18:42:19 PL-3 osafamfnd[4099]: NO 'safSu=SU1,safSg=SG,safApp=test2nApp' 
Presence State TERMINATING => UNINSTANTIATED


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


safSi=SI1,safApp=test2nApp
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=FULLY_ASSIGNED(2)
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)

safSu=SU1,safSg=SG,safApp=test2nApp
        saAmfSUAdminState=UNLOCKED(1)
        saAmfSUOperState=ENABLED(1)
        saAmfSUPresenceState=INSTANTIATED(3)
        saAmfSUReadinessState=IN-SERVICE(2)
safSu=SU2,safSg=SG,safApp=test2nApp
        saAmfSUAdminState=UNLOCKED(1)
        saAmfSUOperState=ENABLED(1)
        saAmfSUPresenceState=INSTANTIATED(3)
        saAmfSUReadinessState=IN-SERVICE(2)


---

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