On 04-Aug-14 12:26 PM, praveen malviya wrote: > > > > -------- Original Message -------- > Subject: Re: [users] SU restart configuration > Date: Sun, 3 Aug 2014 23:14:35 -0700 > From: santosh satapathy <[email protected]> > To: praveen malviya <[email protected]> > > > > Thanks a lot Praveen. > > I would like to configure for an SU with sa-aware components in > no-redundancy model and no spare SUs/SIs configured such that: > > When a component restarts, the component should restart say 3 times and > then after escalation the SU should restart 3 times(configurable) and > stop escalating further as mentioned in section 3.11. When the > escalation is stopped it should come back to admin state 3 so that after > the issue related to the component is fixed can be unlocked again. I > would like to not further escalate to (level 3) a SU switchover/failover > or node failover or reboot as its the only node the SU is running on a > node and no spare SU/SI/Node is configured. > > Can I achieve this configuration using AMF? Any help is much appreciated. >
Escalation cannot be stopped this way. If in the configuration saAmfNodeSuFailoverMax=0 is set to 0, nodefailover will be escalated without any sufailover. Here if saAmfNodeAutoRepair is 0 then node will not be repaired by AMF. Since AMF does not support admin repair on node by admin, so manual reboot of node is the only option. But still one thing can be done OpenSAF 4.4 onwards.Enable saAmfSUFailover flag and disable saAmfSGAutoRepair. In this way escalation will stop at the sufailover level with SU in disabled state. All the components of this SU will be cleaned up (this clean up itself should fix the problem with component). Now if there are no more SUs on the node, nodefailover will never get escalated because no more faulty components. After fixing the component (if not perfectly cleaned up), perform admin repair of this disabled SU. This will instantiate the SU and assign it, if allowed by configuration parameters. Thanks, Praveen > > > > On Tue, Jul 22, 2014 at 11:43 PM, praveen malviya > <[email protected] <mailto:[email protected]>> wrote: > > > On 23-Jul-14 12:04 PM, santosh satapathy wrote: > > Hello All, > > Can somebody let me know if we can prevent the SU restart to > limit to n > times, when a component faults in that SU instead of getting > escalated to > SU failover/Node failover. It is desired in my case to stop > restarting the > SU after a finite number of times. > > Is such a configuration possible? > > You can configure saAmfSGSuRestartMax for this. > Please see section "3.11.2.2 Escalations of Levels 1 and 2 " of > B.04.01 spec for how it works. > > Thanks, > Praveen > > Thanks a lot, > Santosh > > ------------------------------__------------------------------__------------------ > Want fast and easy access to all the code in your enterprise? > Index and > search up to 200,000 lines of code with a free copy of Black Duck > Code Sight - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds > _________________________________________________ > Opensaf-users mailing list > Opensaf-users@lists.__sourceforge.net > <mailto:[email protected]> > https://lists.sourceforge.net/__lists/listinfo/opensaf-users > <https://lists.sourceforge.net/lists/listinfo/opensaf-users> > > > > > ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
