[ovirt-users] Re: Can't ping gluster interfaces for HCI setup

Thanks. I have the DNS but must have my interface config wrong. On my first node I have two interfaces in use, em1 for the management interface and p1p1 for the Gluster interface. [root@ovirt-node-00 ~]# cat /etc/sysconfig/network-scripts/ifcfg-em1 TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=no IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME=em1 UUID=724cddb2-8ce9-43ea-8c0e-e1aff19e72cc DEVICE=em1 ONBOOT=yes IPADDR=10.0.0.31 PREFIX=24 GATEWAY=10.0.0.1 DNS1=10.0.0.1 [root@ovirt-node-00 ~]# cat /etc/sysconfig/network-scripts/ifcfg-p1p1 TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=no IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME=p1p1 UUID=1adb45d3-4dac-4bac-bb19-257fb9c7016b DEVICE=p1p1 ONBOOT=yes IPADDR=10.0.1.31 PREFIX=24 GATEWAY=10.0.0.1 DNS1=10.0.0.1 On Tue, Apr 28, 2020 at 10:47 PM Jayme <jaymef(a)gmail.com&gt; wrote: > You should use host names for gluster like gluster1.hostname.com that > resolve to the ip chosen for gluster. > > For my env I have something like this: > > Server0: > Host0.example.com 10.10.0.100 > Gluster0.example.com 10.0.1.100 > > Same thing for other two severs except hostnames and ips of course. > > Use the gluster hostnames for the first step then the sever hostnames for > the others. > > I made sure I could ssh to and from both hostX and glusterX on each > server. > > On Tue, Apr 28, 2020 at 6:34 PM Shareef Jalloq <shareef(a)jalloq.co.uk&gt; > wrote: > >> Perhaps it's me, but these two documents seem to disagree on what >> hostnames to use when setting up. Can someone clarify. >> >> The main documentation here: >> https://www.ovirt.org/documentation/gluster-hyperconverged/chap-Deploying... talks >> about copying the SSH keys to the gluster host address but the old blog >> post with an outdated interface here: >> https://blogs.ovirt.org/2018/02/up-and-running-with-ovirt-4-2-and-gluster... uses >> the node address. >> >> In the first step of the hyperconverged Gluster wizard, when it asks for >> "Gluster network address", is this wanting the host IP or the IP of the >> Gluster interface? >> >> On Tue, Apr 28, 2020 at 10:24 PM Shareef Jalloq <shareef(a)jalloq.co.uk&gt; >> wrote: >> >>> OK, thanks both, that seems to have fixed that issue. >>> >>> Is there any other config I need to do because the next step in the >>> deployment guide of copying SSH keys seems to take over a minute just to >>> prompt for a password. Something smells here. >>> >>> On Tue, Apr 28, 2020 at 7:32 PM Jayme <jaymef(a)gmail.com&gt; wrote: >>> >>>> You should be using a different subnet for each. I.e. 10.0.0.30 and >>>> 10.0.1.30 for example >>>> >>>> On Tue, Apr 28, 2020 at 2:49 PM Shareef Jalloq <shareef(a)jalloq.co.uk&gt; >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> I'm in the process of trying to set up an HCI 3 node cluster in my >>>>> homelab to better understand the Gluster setup and have failed at the first >>>>> hurdle. I've set up the node interfaces on the built in NIC and am using a >>>>> PCI NIC for the Gluster traffic - at the moment this is 1Gb until I can >>>>> upgrade - and I've assigned a static IP to both interfaces and also have >>>>> both entries in my DNS. >>>>> >>>>> From any of the three nodes, I can ping the gateway, the other nodes, >>>>> any external IP but I can't ping any of the Gluster NICs. What have I >>>>> forgotten to do? Here's the relevant output of 'ip addr show'. em1 is the >>>>> motherboard NIC and p1p1 is port 1 of an Intel NIC. The >>>>> /etc/sysconfig/network-scripts/ifcfg-<if> scripts are identical aside from >>>>> IPADDR, NAME, DEVICE and UUID fields. >>>>> >>>>> Thanks, Shareef. >>>>> >>>>> [root@ovirt-node-00 ~]# ip addr show >>>>> >>>>> >>>>> 2: p1p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP >>>>> group default qlen 1000 >>>>> >>>>> link/ether a0:36:9f:1f:f9:78 brd ff:ff:ff:ff:ff:ff >>>>> >>>>> inet 10.0.0.34/24 brd 10.0.0.255 scope global noprefixroute p1p1 >>>>> >>>>> valid_lft forever preferred_lft forever >>>>> >>>>> inet6 fd4d:e9e3:6f5:1:a236:9fff:fe1f:f978/64 scope global >>>>> mngtmpaddr dynamic >>>>> >>>>> valid_lft 7054sec preferred_lft 7054sec >>>>> >>>>> inet6 fe80::a236:9fff:fe1f:f978/64 scope link >>>>> >>>>> valid_lft forever preferred_lft forever >>>>> >>>>> >>>>> 4: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast >>>>> state UP group default qlen 1000 >>>>> >>>>> link/ether 98:90:96:a1:16:ad brd ff:ff:ff:ff:ff:ff >>>>> >>>>> inet 10.0.0.31/24 brd 10.0.0.255 scope global noprefixroute em1 >>>>> >>>>> valid_lft forever preferred_lft forever >>>>> >>>>> inet6 fd4d:e9e3:6f5:1:9a90:96ff:fea1:16ad/64 scope global >>>>> mngtmpaddr dynamic >>>>> >>>>> valid_lft 7054sec preferred_lft 7054sec >>>>> >>>>> inet6 fe80::9a90:96ff:fea1:16ad/64 scope link >>>>> >>>>> valid_lft forever preferred_lft forever >>>>> >>>>> >>>>> _______________________________________________ >>>>> Users mailing list -- users(a)ovirt.org >>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>>>> oVirt Code of Conduct: >>>>> https://www.ovirt.org/community/about/community-guidelines/ >>>>> List Archives: >>>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/S7UESGZ6MJX... >>>>> >>>>