- **status**: accepted --> invalid
- **Milestone**: 4.4.2 --> never
- **Comment**:
As per AMF PR doc section 3.11.1.3, surestart recovery will be skipped in two
cases:
1) When saAmfSUPresenceState of failed SU is SA_AMF_PRESENCE_INSTANTIATING or
SA_AMF_PRESENCE_RESTARTING.
2)When assignments for some or all SIs are pending on the SU.
So component fault escalates to component-failover skipping su-restart and SG
becomes stable after standby becomes active.
Please find configuration and traces in 423.tgz after successful validation.
---
** [tickets:#423] amf: Active SU assignments are not removed while component
faults escalating to SuRestart.**
**Status:** invalid
**Milestone:** never
**Created:** Fri May 31, 2013 06:18 AM UTC by Praveen
**Last Updated:** Tue Mar 03, 2015 04:53 AM UTC
**Owner:** Praveen
Migrated from http://devel.opensaf.org/ticket/2947.
changeset : 3855 with 2911, 2918 patches
Model : 2n
configuration : 1App,1SG,5SU with 3comps each, 5SIs with 3csi each.
si-si deps configured as SI1<-SI2<-SI3<-SI4
csi-csi deps configured as CSI1/SI1<-CSI2/SI1<-CSI3<SI1 and
CSI1/SI5<-CSI2/SI5<-CSI3<SI5
SU1 is active and SU2 is standby
SU1,SU3 are mapped to PL-3 and SU2,4,5 are mapped to PL-4
scenario:
1. lock of active SU1
2. component in SU1 is made to fault in quiesced cbk
3. Recovery for faulted component escalates to SuRestart?
4. Su1 gets locked but assignments are not stuck in quiesced and Standby SU
remains in standby state itself.
SU states:
safSu=SU1,safSg=SGONE,safApp=TWONAPP
saAmfSUAdminState=LOCKED(2)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
safSu=SU2,safSg=SGONE,safApp=TWONAPP
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=SU3,safSg=SGONE,safApp=TWONAPP
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=SU4,safSg=SGONE,safApp=TWONAPP
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=SU5,safSg=SGONE,safApp=TWONAPP
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
SI assignments show:
safSISU=safSu=SU1\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI1,safApp=TWONAPP
saAmfSISUHAState=QUIESCED(3)
safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI1,safApp=TWONAPP
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI2,safApp=TWONAPP
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU1\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI2,safApp=TWONAPP
saAmfSISUHAState=QUIESCED(3)
safSISU=safSu=SU1\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI3,safApp=TWONAPP
saAmfSISUHAState=QUIESCED(3)
safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI3,safApp=TWONAPP
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU1\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI4,safApp=TWONAPP
saAmfSISUHAState=QUIESCED(3)
safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI4,safApp=TWONAPP
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU1\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI5,safApp=TWONAPP
saAmfSISUHAState=QUIESCED(3)
safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI5,safApp=TWONAPP
saAmfSISUHAState=STANDBY(2)
/var/log/messages of pl-3:
Dec 17 22:51:28 linux-xc76 osafamfnd[6692]: NO
'safComp=COMP1SU1TWONAPP,safSu=SU1,safSg=SGONE,safApp=TWONAPP' faulted due to
'avaDown(8)' : Recovery is 'suRestart(10)'
Dec 17 22:51:28 linux-xc76 osafamfnd[6692]: NO
'safSu=SU1,safSg=SGONE,safApp=TWONAPP' Presence State INSTANTIATED => RESTARTING
....
....
Dec 17 22:51:28 linux-xc76 osafamfnd[6692]: NO Assigning
'safSi=TWONSI1,safApp=TWONAPP' QUIESCED to
'safSu=SU1,safSg=SGONE,safApp=TWONAPP'
Dec 17 22:51:28 linux-xc76 osafamfnd[6692]: NO Assigning
'safSi=TWONSI2,safApp=TWONAPP' QUIESCED to
'safSu=SU1,safSg=SGONE,safApp=TWONAPP'
Dec 17 22:51:28 linux-xc76 osafamfnd[6692]: NO Assigning
'safSi=TWONSI3,safApp=TWONAPP' QUIESCED to
'safSu=SU1,safSg=SGONE,safApp=TWONAPP'
Dec 17 22:51:28 linux-xc76 osafamfnd[6692]: NO Assigning
'safSi=TWONSI4,safApp=TWONAPP' QUIESCED to
'safSu=SU1,safSg=SGONE,safApp=TWONAPP'
Dec 17 22:51:28 linux-xc76 osafamfnd[6692]: NO Assigning
'safSi=TWONSI5,safApp=TWONAPP' QUIESCED to
'safSu=SU1,safSg=SGONE,safApp=TWONAPP'
Dec 17 22:51:28 linux-xc76 osafimmnd[6673]: NO Implementer connected: 55
(COMP1SU1TWONAPP) <934, 2030f>
Dec 17 22:51:28 linux-xc76 osafimmnd[6673]: NO Implementer (applier)
connected: 56 (@COMP1SU1TWONAPP) <935, 2030f>
---
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.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
