This issue is observed in one more case related to SU lock along with
su-failover recovery.
Attached quiesced.tgz contains conf and traces.
steps to reproduce:
1)Bting up the configuration.
2)Lock active SU.
3)The Su that is becoming active because of lock operation should fault with
su-failover reocvery.
4)Amfd will not remove quiesced assignments from locked SU:
after lock assignments are:
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=QUIESCED(3)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=QUIESCED(3)
Attachments:
-
[quiesced.tgz](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/0143c687/43d6/attachment/quiesced.tgz)
(45.3 kB; application/x-compressed)
---
** [tickets:#316] SI Assignments are not removed for a SU in Nway redundancy
model**
**Status:** accepted
**Milestone:** 4.7.2
**Created:** Fri May 24, 2013 08:39 AM UTC by Nagendra Kumar
**Last Updated:** Wed May 04, 2016 07:20 PM UTC
**Owner:** Praveen
**Attachments:**
- [logs.tar](https://sourceforge.net/p/opensaf/tickets/316/attachment/logs.tar)
(2.5 MB; application/x-gzip-compressed)
- [osafamfd](https://sourceforge.net/p/opensaf/tickets/316/attachment/osafamfd)
(228.2 kB; application/octet-stream)
-
[osafamfnd](https://sourceforge.net/p/opensaf/tickets/316/attachment/osafamfnd)
(122.8 kB; application/octet-stream)
-
[pl_logs.tar](https://sourceforge.net/p/opensaf/tickets/316/attachment/pl_logs.tar)
(1.3 MB; application/x-gzip-compressed)
Migrated from http://devel.opensaf.org/ticket/2987
changeset : 3855
Model : NWay
configuration : 1App,1SG,5SU with 3comps each, 5SIs with 3csi each.
si-si deps configured as SI1<-SI2<-SI3<-SI4
SIrankedSus not configured.
Node mapping : SU1 on SC-1, SU2 on SC-2, SU3 on PL-3, SU4,SU5 on PL-4.
While running the campaign, smf performs lock,lock-in of the activation units
i.e SUs. The SIs for SU3 are not removed though SU3 is in locked-state.
Subsequent unlock-in,unlock of SU3 fails.
/var/log/messages of active ctrl- SC-1 shows
============================================
Feb 3 22:45:14 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:16 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:18 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:20 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:23 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Fail to invoke admin operation,
too many SA_AIS_ERR_TRY_AGAIN, giving up.
dn=[safSu=SU3,safSg=SGONE,safApp=NWAYAPP], opId=[3]
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Failed to call admin operation 3
on safSu=SU3,safSg=SGONE,safApp=NWAYAPP
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Failed to Terminate activation
units in step=safSmfStep=0003
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Step undoing failed
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Step safSmfStep=0003 in procedure
safSmfProc=amfClusterProc-1 failed, step result 5
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: NO CAMP: Procedure
safSmfProc=amfClusterProc-1 returned FAILED
SU Assignments brief:
=======================
safSISU=safSu=SU1\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI3,safApp=NWAYAPP
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI2,safApp=NWAYAPP
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU3\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI5,safApp=NWAYAPP
saAmfSISUHAState=QUIESCED(3)
safSISU=safSu=SU4\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI5,safApp=NWAYAPP
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI1,safApp=NWAYAPP
saAmfSISUHAState=ACTIVE(1)
SU States:
==========
safSu=SU3,safSg=SGONE,safApp=NWAYAPP
saAmfSUAdminState=LOCKED(2)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
changed 4 months ago by bertil ¶
■owner changed from ingber to ravisekhar
■component changed from saf/smfsv to saf/avsv
I beleave this is an AMF problem. SMF only uses the AMF admin ops (lock, unlock
etc).
---
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.------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
