# Cluster network configuration with 2 network boards

**URL:** <https://discuss.elastic.co/t/cluster-network-configuration-with-2-network-boards/128385>\
**Category:** Elasticsearch\
**Created:** [April 17, 2018, 2:39pm UTC](https://discuss.elastic.co/t/cluster-network-configuration-with-2-network-boards/128385 "2018-04-17T14:39:08Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![dao](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@dao](https://discuss.elastic.co/u/dao)\
**Post date:** [April 17, 2018, 2:39pm UTC](https://discuss.elastic.co/t/cluster-network-configuration-with-2-network-boards/128385/1 "2018-04-17T14:39:08Z")

</div>

Hello, I have 3 hosts with 2 network interfaces. one public and the other private.

I want to bind port 9200 on public network interface (queries) and port 9300 on private interface (zen.discovery)

Here is my conf `ifconfig -a` for each of my servers (the IPs differ of course accross the hosts).

- IPs starting with 163.XXX.XXX.XXX are the public ones (interface enp1s0f0)
- IPs starting with 10.XXX.XXX.XXX are the private ones (interface enp1s0f1)

```auto
enp1s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 163.aaa.aaa.27 netmask 255.255.255.0 broadcast 163.aaa.aaa.255
        inet6 fe80::ec4:7aff:fe83:1228 prefixlen 64 scopeid 0x20<link>
        ether 0c:c4:7a:83:12:28 txqueuelen 1000 (Ethernet)
        RX packets 1078210 bytes 827903485 (789.5 MiB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 279800 bytes 182892689 (174.4 MiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
        device memory 0x7ac00000-7ac7ffff

enp1s0f1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000
        inet 10.bbb.bbb.27 netmask 255.255.255.128 broadcast 10.bbb.bbb.127
        inet6 fe80::ec4:7aff:fe83:1229 prefixlen 64 scopeid 0x20<link>
        ether 0c:c4:7a:83:12:29 txqueuelen 1000 (Ethernet)
        RX packets 3033 bytes 234078 (228.5 KiB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 2220 bytes 165435 (161.5 KiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
        device memory 0x7ac80000-7acfffff

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
        inet 127.0.0.1 netmask 255.0.0.0
        inet6 ::1 prefixlen 128 scopeid 0x10<host>
        loop txqueuelen 1 (Local Loopback)
        RX packets 1122961 bytes 200701185 (191.4 MiB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 1122961 bytes 200701185 (191.4 MiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

```

I have those settings in my `elasticsearch.yml` file. I took the inet private address of each of my hosts for the zen.discovery array.

```auto
discovery.zen.ping.unicast.hosts: ["10.bbb.bbb.27", "10.bbb.bbb.40", "10.bbb.bbb.75"]
network.bind_host: 0.0.0.0
network.publish_host: _enp1s0f1_

```

Unfortunately, it does not work, the nodes are responding on both of my adresses (public and private) on port 9200. But the nodes never joins the cluster, that means, I have 3 clusters of 1 node.

by the way, the ping is OK:

```auto
root@wilco-1:~# ping 10.bbb.bbb.40
PING 10.bbb.bbb.40 (10.bbb.bbb.40) 56(84) bytes of data.
64 bytes from 10.bbb.bbb.40: icmp_seq=1 ttl=63 time=0.468 ms
64 bytes from 10.bbb.bbb.40: icmp_seq=2 ttl=63 time=0.620 ms
64 bytes from 10.bbb.bbb.40: icmp_seq=3 ttl=63 time=0.623 ms
64 bytes from 10.bbb.bbb.40: icmp_seq=4 ttl=63 time=0.623 ms

```

What did I miss? HEEEELP !

---

<div class="post-metadata">

**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\
**Post date:** [April 17, 2018, 4:31pm UTC](https://discuss.elastic.co/t/cluster-network-configuration-with-2-network-boards/128385/2 "2018-04-17T16:31:29Z")

</div>

The `network.bind_host` setting is for the address that Elasticsearch binds to for HTTP and TCP (and `0.0.0.0` means all addresses). If you want to use separate addresses for these, you have to use different settings. In this case, you want `http.host` and `transport.host` (note that you can set `http.bind_host` and `http.publish_host` as well as `transport.bind_host` and `transport.publish_host` but based on your description I don't think that you need that).

So, you would want:

```auto
http.host: _enp1s0f0_
transport.host: _enp1s0f1_

```

---

<div class="post-metadata">

**Author:** ![dao](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@dao](https://discuss.elastic.co/u/dao)\
**Post date:** [April 18, 2018, 1:20pm UTC](https://discuss.elastic.co/t/cluster-network-configuration-with-2-network-boards/128385/3 "2018-04-18T13:20:37Z")

</div>

I have set this and it seems to work

```auto
network.host: 0.0.0.0
network.publish_host: _enp1s0f1_

```

The issue was a ip-filtering issue, where in fact, I had to add the cluster hosts in it (ip-filtering is a x-pack feature).

OK, so now, the hosts are talking together but in the monitoring, I still can see only 1 node. And the funny thing is that it is the same node whatever the host !

so situation:

host-1 ([https://wilco-1.domain.fr/](https://wilco-1.domain.fr/)) runs node-1 (node.name: wilco-1)  
host-2 ([https://wilco-2.domain.fr/](https://wilco-2.domain.fr/)) runs node-2 (node.name: wilco-2)  
host-3 ([https://wilco-3.domain.fr/](https://wilco-3.domain.fr/)) runs node-3 (node.name: wilco-3)

I have plenty of logs like  
`[2018-04-18T15:02:06,149][WARN][o.e.g.DanglingIndicesState] [wilco-3] [[.monitoring-es-6-2018.04.17/clVarL1iQ2OnOaT4fcFwPA]] can not be imported as a dangling index, as index with same name already exists in cluster metadata`

here is the monitoring rendering:

 ![11](https://us1.discourse-cdn.com/elastic/original/3X/6/9/69e0470c523d4cadc7233713b9ff03fc8504e749.png)

---

<div class="post-metadata">

**Author:** ![dao](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@dao](https://discuss.elastic.co/u/dao)\
**Post date:** [April 18, 2018, 2:07pm UTC](https://discuss.elastic.co/t/cluster-network-configuration-with-2-network-boards/128385/4 "2018-04-18T14:07:36Z")

</div>

and I found 2 clusters with the same name!!!

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/4/34ea4c314adea6afc1fc3d1075d5dd32826606a9.png)

---

<div class="post-metadata">

**Author:** ![dao](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@dao](https://discuss.elastic.co/u/dao)\
**Post date:** [April 19, 2018, 8:23am UTC](https://discuss.elastic.co/t/cluster-network-configuration-with-2-network-boards/128385/5 "2018-04-19T08:23:41Z")

</div>

How is it possible that there are 2 clusters with the same name?

---

<div class="post-metadata">

**Author:** ![dao](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@dao](https://discuss.elastic.co/u/dao)\
**Post date:** [April 24, 2018, 12:01pm UTC](https://discuss.elastic.co/t/cluster-network-configuration-with-2-network-boards/128385/6 "2018-04-24T12:01:51Z")

</div>

After a few hours, the 2nd cluster has disapeared and everything back OK

---

<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:** [May 22, 2018, 12:02pm UTC](https://discuss.elastic.co/t/cluster-network-configuration-with-2-network-boards/128385/7 "2018-05-22T12:02:00Z")

</div>

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