Indeed, you have to add routes and rules to routing table. Just bond 
them.


-----Original Message-----
From: John Hearns [mailto:[email protected]] 
Sent: vrijdag 1 juni 2018 10:00
To: ceph-users
Subject: Re: [ceph-users] iSCSI to a Ceph node with 2 network adapters - 
how to ?

Errr....   is this very wise ?

I have both its Ethernets connected to the same LAN,
        with different IPs in the same subnet
        (like, 192.168.200.230/24 and 192.168.200.231/24)
 

In my experience setting up to interfaces on the same subnet means that 
your ssystem doesnt know which one to route traffic through...







On 1 June 2018 at 09:01, Wladimir Mutel <[email protected]> wrote:


                Dear all,
        
                I am experimenting with Ceph setup. I set up a single node
                (Asus P10S-M WS, Xeon E3-1235 v5, 64 GB RAM, 8x3TB SATA 
HDDs,
                Ubuntu 18.04 Bionic, Ceph packages from
                http://download.ceph.com/debian-luminous/dists/xenial/ 
<http://download.ceph.com/debian-luminous/dists/xenial/> 
                and iscsi parts built manually per
        http://docs.ceph.com/docs/master/rbd/iscsi-target-cli-manual-instal
l/ 
<http://docs.ceph.com/docs/master/rbd/iscsi-target-cli-manual-install/> )
                Also i changed 'chooseleaf ... host' into 'chooseleaf ... osd'
                in the CRUSH map to run with single host.
        
                I have both its Ethernets connected to the same LAN,
                with different IPs in the same subnet
                (like, 192.168.200.230/24 and 192.168.200.231/24)
                mon_host in ceph.conf is set to 192.168.200.230,
                and ceph daemons (mgr, mon, osd) are listening to this IP.
        
                What I would like to finally achieve, is to provide 
multipath
                iSCSI access through both these Ethernets to Ceph RBDs,
                and apparently, gwcli does not allow me to add a second
                gateway to the same target. It is going like this :
        
        /iscsi-target> create iqn.2018-06.host.test:test
        ok
        /iscsi-target> cd iqn.2018-06.host.test:test/gateways
        /iscsi-target...test/gateways> create p10s 192.168.200.230 
skipchecks=true
        OS version/package checks have been bypassed
        Adding gateway, sync'ing 0 disk(s) and 0 client(s)
        ok
        /iscsi-target...test/gateways> create p10s2 192.168.200.231 
skipchecks=true
        OS version/package checks have been bypassed
        Adding gateway, sync'ing 0 disk(s) and 0 client(s)
        Failed : Gateway creation failed, gateway(s) 
unavailable:192.168.200.231(UNKNOWN state)
        
                host names are defined in /etc/hosts as follows :
        
        192.168.200.230 p10s
        192.168.200.231 p10s2
        
                so I suppose that something does not listen on 
192.168.200.231, but I don't have an idea what is that thing and how to 
make it listen there. Or how to achieve this goal (utilization of both 
Ethernets for iSCSI) in different way. Shoud I aggregate Ethernets into 
a 'bond' interface with single IP ? Should I build and use 'lrbd' tool 
instead of 'gwcli' ? Is it acceptable that I run kernel 4.15, not 4.16+ 
?
        What other directions could you give me on this task ?
        Thanks in advance for your replies.
        _______________________________________________
        ceph-users mailing list
        [email protected]
        http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com 
<http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com> 
        



_______________________________________________
ceph-users mailing list
[email protected]
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Reply via email to