> > >> Does the unlock operation trigger AMF attempts to instantiate the > >> component again? > > > > No, component is not instantiated again, because amf cannot > determine > > What state the component is in or what is the problem with his > > instantiation. > > My question was/is, what does the __operator__ have to do for > AMF to try instantiate the component again?
Setting the MIB object ncsSUTermState to TRUE (see NCS-AVSV-MIB) would help you with that. > > >> Another example is when an application has restarted to many times > >> within the probation period, what happens then and how is > that error > >> cleared? > > > > The next level of escalation is done & the escalated recovery is > > performed. > > This is configurable to any of SU RESTART, SU FAILOVER, NODE FAIL > > OVER/FAST... > > If all automatic AMF recovery actions has failed, how does > the __operator__ repair the system? If it goes through the regular escalation policy levels, it would reach NODE failover stage, after which One can pull out the card. If NODE failfast was chosen, the node anyway gets rebooted. Still, for such a faulty component, there's always a choice to lock, repair, unlock though. > > Thanks, > Hans > > _______________________________________________ Users mailing list [email protected] http://list.opensaf.org/maillist/listinfo/users
