- **status**: accepted --> duplicate
- **Milestone**: future --> never
- **Comment**:
1)Time when modefailvoer request comes to active AMFD, it comes from the SU
active controller hosts:
Apr 16 14:48:13.721813 osafamfd [2783:avd_sgproc.c:0258] >>
avd_su_oper_state_evh: id:143, node:2010f,
'safSu=SU1,safSg=SGONE,safApp=TWONAPP' state:2
Apr 16 14:48:13.728389 osafamfd [2783:avd_su.c:0777] >> avd_su_oper_state_set:
'safSu=SU1,safSg=SGONE,safApp=TWONAPP' ENABLED => DISABLED
Apr 16 14:48:13.752753 osafamfd [2783:avd_su.c:0803] >>
avd_su_readiness_state_set: 'safSu=SU1,safSg=SGONE,safApp=TWONAPP'
OUT_OF_SERVICE
Apr 16 14:48:13.752867 osafamfd [2783:lga_api.c:0738] >> saLogWriteLogAsync
Apr 16 14:48:13.752994 osafamfd [2783:lga_mds.c:1168] >> lga_mds_msg_async_send
Apr 16 14:48:13.753190 osafamfd [2783:lga_mds.c:0577] >> lga_mds_enc
Apr 16 14:48:13.753398 osafamfd [2783:lga_mds.c:0608] T2 msgtype: 0
Apr 16 14:48:13.753505 osafamfd [2783:lga_mds.c:0621] T2 api_info.type: 4
Apr 16 14:48:13.753600 osafamfd [2783:lga_mds.c:0649] << lga_mds_enc
Apr 16 14:48:13.753718 osafamfd [2783:lga_mds.c:1190] << lga_mds_msg_async_send
Apr 16 14:48:13.753901 osafamfd [2783:lga_api.c:0903] << saLogWriteLogAsync
Apr 16 14:48:13.754019 osafamfd [2783:mbcsv_api.c:0773] >>
mbcsv_process_snd_ckpt_request: Sending checkpoint data to all STANDBY peers,
as per the send-type specified
Here AMFD marks the readiness state outservice and at the same time check
point it to standby SC-2.
On standby it decodes and update the state:
Apr 16 14:48:15.463171 osafamfd [3338:avd_ckpt_dec.c:1507] <<
dec_su_oper_state: status '1'
Apr 16 14:48:15.463293 osafamfd [3338:avd_ckpt_dec.c:1579] >>
dec_su_readiness_state
Apr 16 14:48:15.463674 osafamfd [3338:avd_ckpt_dec.c:1599] <<
dec_su_readiness_state: status '1'
Thus state got updated to SC-2, which will not update it to IMM.
2)As a part of nodefailover escalation active AMFD sends reboot message to its
amfnd:
Apr 16 14:48:13.788872 osafamfd [2783:lga_api.c:0903] << saLogWriteLogAsync
Apr 16 14:48:13.789178 osafamfd [2783:avd_util.c:1719] TR Sending REBOOT MSG to
2010f
Apr 16 14:48:13.789316 osafamfd [2783:avd_sgproc.c:0500] <<
avd_su_oper_state_evh
After sending this message only action that active AMFD performs is:
Apr 16 14:48:13.837926 osafamfd [2783:avd_imm.c:1607] >> avd_job_fifo_execute
Apr 16 14:48:13.838150 osafamfd [2783:avd_imm.c:1522] >>
job_exec_imm_objupdate:
safComp=COMP3SU1TWONAPP,safSu=SU1,safSg=SGONE,safApp=TWONAPP
saAmfCompPresenceState
Apr 16 14:48:13.838231 osafamfd [2783:imma_oi_api.c:2259] >>
saImmOiRtObjectUpdate_2
Apr 16 14:50:30.958544 osafamfd [2771:ncs_main_pub.c:0223] TR
NCS:PROCESS_ID=2771
Thus before reboot it does not update the state to IMM.
3) When SC-2 becomes active, it will mark the state as out of service in SC-1
exit handling,
but old state and new states are same, no update will be done to IMM.
on SC-2:
Apr 16 14:48:22.004717 osafamfd [3338:avd_sgproc.c:1456] >>
avd_node_down_appl_susi_failover: 'safAmfNode=SC-1,safAmfCluster=myAmfCluster'
Apr 16 14:48:22.004896 osafamfd [3338:avd_su.c:0749] >> avd_su_pres_state_set:
'safSu=SU1,safSg=SGONE,safApp=TWONAPP' TERMINATING => UNINSTANTIATED
The state will not be updated to IMM becasue of check:
void avd_su_readiness_state_set(AVD_SU *su, SaAmfReadinessStateT
readiness_state)
{
AVD_COMP *comp = NULL;
if (su->saAmfSuReadinessState == readiness_state)
return;
Thus the state was never got updated to IMM. This is the reason for SU1 in:
saAmfSUReadinessState=IN-SERVICE(2)
Again this is the same problem related to updates of runtime objects (#494 and
#853) when active controller is about to reboot and it has pending updates to
IMM.
Any fix will solve all similar problems. Hence marking this ticket duplicate of
#494. Also #494 will be updated by giving reference of #853 and #858.
---
** [tickets:#858] su is in wrong state of IN-SERVICE and UNINSTANTIATED**
**Status:** duplicate
**Milestone:** never
**Created:** Wed Apr 16, 2014 09:44 AM UTC by surender khetavath
**Last Updated:** Thu May 01, 2014 08:47 AM UTC
**Owner:** Praveen
changeset : 5143
model : 2n
configuration : 1App,1SG,5SUs with 3comps each, 5SIs with 3CSIs each
si-si deps configured as SI1 sponsor for SI2,3,4 resp
SU1 mapped to SC-1,SU2 to SC-2,SU3 to pl-3 and SU4,5 to PL-4.
PrefInserviceSus = 4
scenario:
1) fault in SU1 escalated the recovery to nodefailover and SC-1 went to reboot.
After the node is up, the SU1's state is in UNINSTANTIATED and INSERVICE rather
OOS.
SU1 state is not good
safSu=SU1,safSg=SGONE,safApp=TWONAPP
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=UNINSTANTIATED(1)
saAmfSUReadinessState=IN-SERVICE(2)
SUSI assignments are proper:
safSISU=safSu=SU3\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI2,safApp=TWONAPP
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU3\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI1,safApp=TWONAPP
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU3\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI5,safApp=TWONAPP
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI2,safApp=TWONAPP
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI5,safApp=TWONAPP
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI4,safApp=TWONAPP
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI1,safApp=TWONAPP
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.------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
