It must be an external device. If, for example, the kernel crashes hard, or if you get a spinlock, the system may not respond to anything or a service may never stop, blocking a reboot. You can not trust that the system is accessible or functioning in any way.
Fencing *must* be an external device. Period. What kind of servers do you have? On 12/02/2012 03:15 PM, Hermes Flying wrote: > If I have a requirement not to include external HW, is there any other > way? I mean, I am not -by far- a linux expert, but how come it doesn't > do a restart or halt? > > > ------------------------------------------------------------------------ > *From:* Digimer <[email protected]> > *To:* Hermes Flying <[email protected]> > *Cc:* General Linux-HA mailing list <[email protected]> > *Sent:* Sunday, December 2, 2012 10:01 PM > *Subject:* Re: [Linux-HA] Corosync on cluster with 3+ nodes > > On 12/02/2012 02:56 PM, Hermes Flying wrote: >> Clear! In order to do fence and crash a node, is there a specific HW >> requirement to do this? > > Yes, there must be external hardware (out-of-band management counts as > "external", despite physically being on the server's mainboard). The > most common fence device is IPMI, iLO, RSA, iDRAC and the like. > Alternatives are switched PDUs, like APC's AP7900. > > -- > Digimer > Papers and Projects: https://alteeve.ca/w/ > What if the cure for cancer is trapped in the mind of a person without > access to education? > > -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
