<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 4, 2017 at 9:42 PM, Roberto Resoli <span dir="ltr"><<a href="mailto:roberto@resolutions.it" target="_blank">roberto@resolutions.it</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">Il 04/04/2017 13:08, Frank Rust ha scritto:<br>
> Hi folks,<br>
><br>
> I am wondering if it would be possible to create a drbdmanage cluster where the hostname don’t match the ip address of the network interface to use.<br>
><br>
> In detail:<br>
> I have a three node configuration with the ip visible to the outside:<br>
> node1 IP: 192.168.1.1 hostname fs1<br>
> node2 IP: 192.168.1.2 hostname fs2<br>
> node3 IP: 192.168.1.3 hostname fs3<br>
><br>
> Each of the nodes has a second network adapter which shall be used for the storage distribution (and is not visible to the outside).<br>
> node1 10.10.10.1<br>
> node2 10.10.10.2<br>
> node3 10.10.10.3<br>
><br>
> if I do<br>
> drbdmanage init 10.10.10.1<br>
> drbdmanage add-node fs2 10.10.10.2<br>
> drbdmanage add-node fs3 10.10.10.3<br>
><br>
> It will not work because the IP-address of "fs1" is 192.168.1.1 and not 10.10.10.1 and so on.<br>
> I hope it’s possible to understand my description...<br>
><br>
> I can not change the hostnames according to the storage network because it would break other services for the outside.<br>
><br>
> So my question: how would I configure it to get the second network adapter used.<br>
<br>
</span>My cluster is very similar to your; here my /etc/hosts, actualized with<br>
your IPs (and hostname, replace "<a href="http://yourdomain.com" rel="noreferrer" target="_blank">yourdomain.com</a>" with your own); maybe<br>
pvelocalhost is redundant in your case:<br>
<br>
127.0.0.1 localhost.localdomain localhost<br>
192.168.1.1 <a href="http://fs1.yourdomain.com" rel="noreferrer" target="_blank">fs1.yourdomain.com</a> fs1 pvelocalhost<br>
10.10.10.1 <a href="http://fs1.yourdomain.com" rel="noreferrer" target="_blank">fs1.yourdomain.com</a> fs1<br>
192.168.1.2 <a href="http://fs2.yourdomain.com" rel="noreferrer" target="_blank">fs2.yourdomain.com</a> fs2<br>
10.10.10.2 fs2.yourdomain.con fs2<br>
192.168.1.3 <a href="http://fs3.yourdomain.com" rel="noreferrer" target="_blank">fs3.yourdomain.com</a> fs3<br>
10.10.10.3 <a href="http://fs3.yourdomain.com" rel="noreferrer" target="_blank">fs3.yourdomain.com</a> fs3<br>
<br>
I have initialized DRBD9 without problems ...<br>
<br>
rob<br>
<div class="gmail-HOEnZb"><div class="gmail-h5"><br></div></div></blockquote><div>Or simply use different host names for the other network like:<br><br>192.168.1.1 fs1<br>
192.168.1.2 fs2<br>
192.168.1.3 fs3<br></div><div><span class="gmail-">10.10.10.1 sfs1<br></span></div><div><span class="gmail-">
10.10.10.2 sfs2<br></span></div><div><span class="gmail-">
10.10.10.3</span> sfs3<br></div><div> <br></div><div>and set the cluster using those names:<br><br></div><div>drbdmanage init 10.10.10.1<br>drbdmanage add-node sfs2 10.10.10.2<br>drbdmanage add-node sfs3 10.10.10.3<br><br></div><div>That's what I usually do it also helps to differentiate which network are we talking about from the host name perspective. Except if keeping the original names is a must for some reason ...<br></div></div></div></div>