[Linux-HA] /etc/hosts VS node directive in ha.cf

Pavlos Parissis pavlos.parissis at gmail.com
Thu Oct 7 01:18:24 MDT 2010


On 6 October 2010 14:12, Lars Ellenberg <lars.ellenberg at linbit.com> wrote:

> On Fri, Oct 01, 2010 at 08:45:58AM +0200, Pavlos Parissis wrote:
> > Hi,
> >
> > It was mentioned in this thread [1] that Heartbeat does care about the
> > content of /etc/hosts file.
> > That statement triggered me because in my setup the /etc/hosts doesn't
> > resolve the nodename configured in ha.cf to an IP address which is part
> of
> > the 2 cluster LANs.
> > My system have 3 different NICs, 1 is used for the traffic network and
> the
> > other 2 are used by Heartbeat. The systems have assigned IPs to all NICs.
> >
> > The /etc/hosts file looks like this and it is common on all nodes, expect
> > the first 2 lines.
> > 127.0.0.1               node-01.local.localdomain node-01
> > localhost.localdomain localhost
> > ::1             localhost6.localdomain6 localhost6
> >
> > 10.10.10.1              node-01-cluster1.local.localdomain
> node-01-cluster1
> > 10.10.10.129            node-01-cluster2.local.localdomain
> node-01-cluster2
> > 192.168.78.11           node-01.local.localdomain node-01
> >
> > 10.10.10.2              node-02-cluster1.local.localdomain
> node-02-cluster1
> > 10.10.10.130            node-02-cluster2.local.localdomain
> node-02-cluster2
> > 192.168.78.22           node-02.local.localdomain node-02
> >
> > 10.10.10.3              node-03-cluster1.local.localdomain
> node-03-cluster1
> > 10.10.10.131            node-03-cluster2.local.localdomain
> node-03-cluster2
> > 192.168.78.33           node-03.local.localdomain node-03
> >
> > 10.10.10.4             admin-cluster1.local.localdomain admin-cluster1
> > 10.10.10.132           admin-cluster2.local.localdomain admin-cluster2
> > 192.168.78.4           admin.local.localdomain admin
> >
> > and the ha.cf has
> >
> > autojoin none
> > use_logd on
> > debug 0
> > mcast eth0 239.0.0.43 694 1 0
> > bcast eth1
>
> Neither mcast nor bcast need to resolve peer information.
> So it's not important if your node names resolve,
> or how long that resolving would take.
>
> > BTW, is it a requirement from Heartbeat to assign IP on the interface
> that
> > are being in the communication link?
>
> If you use IP for cluster communication,
> you better use an interface with IP enabled.
> Maybe I don't understand your question?
>

You understood the question very well even my question was not written
correctly - I should have written
Is it a requirement from Heartbeat to assign IP on the interface that is
being used as communication link?


Thanks,
Pavlos



More information about the Linux-HA mailing list