Heartbeat and /etc/hosts

[Pippo_9]

Hi all.

I want to find out if putting an entry for Heartbeat lan into /etc/hosts can generate troubles.
Is it possible to do that?

Thanks

JPM

[Sanjay_6 · Accepted solution]

Hi,

As long as the host names are unique. Putting any entry into /etc/hosts is not a problem.

Hope this helps.

Regds

[Lorenzo Facello]

Hi,

in my opinion it'n not a problem...
it's simply a host!

[Bharat Katkar]

No problem at all but bit of system overhead may increase for maintianing and resolving the same.
Do it if it really helps you. !!

[Jeff Schussele]

Hi JPM,

Nope - no troubles at all. We do it on all our clusters. In fact it's a good back door method between cluster nodes if, for any reason, the main IP goes down. You can then telnet/ssh between systems over the heartbeat network.
Of course this assumes you are using separate, private subnets for the heartbeats - which is *strongly* recommended.

My 2 cents,
Jeff

[Geoff Wild]

No problems at all - that's what we do in our clusters as we

hosts: files [NOTFOUND=CONTINUE] dns

in nsswitch.conf

In hosts:

#
# Heart Beat LAN
#
192.168.2.181 svr003hb
192.168.2.182 svr004hb


Rgds...Geoff

[Rita C Workman]

You can do this...but be sure that those heartbeat addresses do not conflict in any way with the pkg resolution.

I usually put my heartbeat addresses at the very bottom of the file, just to be overly careful.

Rgrds,
Rita

[SS_6]

/etc/hosts file is just to resolve hostname/IP and its not harmfull unless entries are unique.

[Dani Seely]

Yes, you can do this, and it works! From an Administrator's view ... test first, keep /etc/hosts entries separate, and USE COMMENTS!

Suggest that prior to making these entries you ensure there are no address resolution conflicts FIRST. After that, make the entries in /etc/hosts in a separate area for the heartbeat addresses, adding a comment so you know what they were added for and to keep this area separate from regular host entries.