# Network setup: Cluster: Why can't name self in list of hosts?

**URL:** <https://discuss.elastic.co/t/network-setup-cluster-why-cant-name-self-in-list-of-hosts/110206>\
**Category:** Elasticsearch\
**Created:** [December 4, 2017, 7:51pm UTC](https://discuss.elastic.co/t/network-setup-cluster-why-cant-name-self-in-list-of-hosts/110206 "2017-12-04T19:51:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jose\_Ramierez](https://avatars.discourse-cdn.com/v4/letter/j/4bbf92/32.png) [@Jose\_Ramierez](https://discuss.elastic.co/u/Jose_Ramierez)\
**Post date:** [December 4, 2017, 7:51pm UTC](https://discuss.elastic.co/t/network-setup-cluster-why-cant-name-self-in-list-of-hosts/110206/1 "2017-12-04T19:51:24Z")

</div>

On 5.6.4

Why is it that I cannot list each nodes' OWN IP in:

discovery.zen.ping.unicast.hosts:

?

If I do this, (e.g. give every node in cluster same entry for "discovery.zen.ping.unicast.hosts: " ), then the cluster comes up red.

Why is ES so finnicky about this? (and forces me to script more for the setup)

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [December 4, 2017, 8:29pm UTC](https://discuss.elastic.co/t/network-setup-cluster-why-cant-name-self-in-list-of-hosts/110206/2 "2017-12-04T20:29:59Z")

</div>

It shouldn't be a problem.

Perhaps if you share some logs we can check what is happening?

---

<div class="post-metadata">

**Author:** ![Jose\_Ramierez](https://avatars.discourse-cdn.com/v4/letter/j/4bbf92/32.png) [@Jose\_Ramierez](https://discuss.elastic.co/u/Jose_Ramierez)\
**Post date:** [December 4, 2017, 9:38pm UTC](https://discuss.elastic.co/t/network-setup-cluster-why-cant-name-self-in-list-of-hosts/110206/3 "2017-12-04T21:38:46Z")

</div>

I am happy to share logs, but they don't say anything... (they show no errors)

The situation is:

Two ES servers, intent is to cluster them. Machines are: 192.168.10.33 and 192.168.10.34

On the .33 system, I can do:

discovery.zen.ping.unicast.hosts: ["192.168.10.34"]

If I do, on both nodes:

discovery.zen.ping.unicast.hosts: ["192.168.10.33", "192.168.10.34"]

The cluster health is red.

I can only get cluster health to green if .33 points to .34, and .34 points to .33

It would be nice to have a more vanilla way to go.

Open to suggestions!

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [December 4, 2017, 9:55pm UTC](https://discuss.elastic.co/t/network-setup-cluster-why-cant-name-self-in-list-of-hosts/110206/4 "2017-12-04T21:55:30Z")

</div>

> [@Jose\_Ramierez](#):
>
> I am happy to share logs, but they don't say anything... (they show no errors)

Right, but they will show something, so it'd be useful 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 1, 2018, 10:07pm UTC](https://discuss.elastic.co/t/network-setup-cluster-why-cant-name-self-in-list-of-hosts/110206/5 "2018-01-01T22:07:53Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.