We tried to follow the Linstor documentation for setting up multiple network 
paths, but there seems to be a step missing.

First, we created 2 NICs on each node...


# linstor node interface create ha52a-cl nic_core 192.168.8.100
# linstor node interface create ha52a-cl nic_repl 198.51.100.100

# linstor node interface create ha52b-cl nic_core 192.168.8.102
# linstor node interface create ha52b-cl nic_repl 198.51.100.102

The we set the preferred NIC for the storage pools...


# linstor storage-pool set-property ha52a-cl spool2 PrefNic nic_core

# linstor storage-pool set-property ha52b-cl spool2 PrefNic nic_core

Then we created the resource...

# linstor resource-group spawn-resources rgroup2 site436 603G

The resource was created successfully, but the .res file only shows 
communication happening on one NIC.

    connection
    {

        disk
        {
            c-fill-target 1048576;
            c-max-rate 2048000;
        }
        host ha52a.mycharts.md address ipv4 198.51.100.100:7415;
        host ha52b.mycharts.md address ipv4 198.51.100.102:7415;
    }

Per the DRBD 9 docs, there should be "path" entries like this...


resource site436 {

  ...

  connection {

    path {

      host ha52a-cl address 192.168.8.100:7900;

      host ha52b-cl address 192.168.8.102:7900;

    }

    path {

      host ha52a-cl address 198.51.100.100:7900;

      host ha52b-cl address 198.51.100.102:7900;

    }

  }

  ...

}

What did we miss? There seems to be a step missing in the documentation where 
it tells you how to make DRBD use both NICs and not just the preferred one.

-Eric






Disclaimer : This email and any files transmitted with it are confidential and 
intended solely for intended recipients. If you are not the named addressee you 
should not disseminate, distribute, copy or alter this email. Any views or 
opinions presented in this email are solely those of the author and might not 
represent those of Physician Select Management. Warning: Although Physician 
Select Management has taken reasonable precautions to ensure no viruses are 
present in this email, the company cannot accept responsibility for any loss or 
damage arising from the use of this email or attachments.
_______________________________________________
Star us on GITHUB: https://github.com/LINBIT
drbd-user mailing list
[email protected]
https://lists.linbit.com/mailman/listinfo/drbd-user

Reply via email to