[Linux-ha-dev] Starting heartbeat when interfaces are down

[Graham, Simon]

> On 2007-10-19T21:57:17, Dejan Muhamedagic <dejanmm at fastmail.fm> wrote:
> 
> > http://old.linux-
> foundation.org/developer_bugzilla/show_bug.cgi?id=1732
> >
> > for some discussion on communication interfaces.
> 
> "discussion" means "the current deficits are by design" ;-)
> 

So right now I'm thinking I need to modify the config and restart 
the hb service when changes occur in the NICs...

> > > This seems somewhat counter to the idea of high availability but
> I'd
> > > like to understand the design center for this behavior before I
> start
> > > trying to 'fix' it...
> > What are your circumstances? In which situations should the
> > interface be down?
> 
> Hotplug interfaces. Transient issues. Weird bugs.
> 
> One NIC dead on start-up (which is a valid SPoF scenario which is
> currently not handled).

Exactly - when you are in a degraded state you still want the cluster to
come up.
The specific case that started me looking at this is when there is no
address
set on a link (e.g. if link is down at startup) which causes hb to
simply 
refuse to start.

Simon