Don't think that's possible in DRBD. What you could do though is to add some redundancy at the NIC level (nic bonding).
Gianni On Mon, 28 Oct 2019 at 06:19, Achim Pucher <[email protected]> wrote: > Hello, > > I beg your pardon for my stupid question: > > I have a 2-NIC-Setup: > > linstor node create testhost01 128.102.0.242 > linstor node create testhost04 128.102.0.245 > linstor node interface create testhost01 data 10.10.10.242 > linstor node interface create testhost04 data 10.10.10.245 > linstor storage-pool set-property testhost01 drbdpool PrefNic data > linstor storage-pool set-property bkhost04 drbdpool PrefNic data > > This results by example in the local resource to > connection > { > host testhost01 address ipv4 10.10.10.242:7018; > host testhost04 address ipv4 10.10.10.245:7018; > } > > Is there a way to define that if interface 10.10.10.245 is not useable > the drbd updates will be send through 128.102.0.245? > > Thanks a lot for your help! > > -- > > Mit freundlichen Grüßen > Achim Pucher > ---- > b+k CAD/CAM Unternehmensberatung GmbH > Daimlerstr. 1 > 38112 Braunschweig > Tel: +49-531-58004-29 > Fax: +49-531-58004-56 > ---- > http://www.bk-cad.de > Registergericht Braunschweig HRB 4181 > Geschäftsführer: Stefan Berndt, Swen Uhlemann > Ust.ID: DE180096944 > Steuernummer 13/206/00333 > > > _______________________________________________ > Star us on GITHUB: https://github.com/LINBIT > drbd-user mailing list > [email protected] > https://lists.linbit.com/mailman/listinfo/drbd-user >
_______________________________________________ Star us on GITHUB: https://github.com/LINBIT drbd-user mailing list [email protected] https://lists.linbit.com/mailman/listinfo/drbd-user
