Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
One thing I didnt mention is that the virtual IPs I'm using are F5 VIPs,
which weren't configured in the hosts at all. Would that be the issue?
On Thu, Jun 4, 2015 at 10:21 AM, Kimly Heler <kimlyheler at gmail.com> wrote:
> Hi Igor, I just tried that and still getting the same error:
>
> on the primary node:
> [root at node1-datacenterA]$ drbdadm up --stacked r0
> drbd.d/r0.res:57: in resource r0, on node1-datacenterA node2-datacenterA:
> IP 192.168.42.1 not found on this host.
>
> I just tried 1 stacked drbd on cluster A, for now. I reduced cluster B to
> just a standalone server (no stacked), then the command was run fine on the
> backup standalone node, while the command was failing as above (note that I
> have the same r0.res file on all the nodes)
>
> on a backup node:
> [root at node1-datacenterB]$ drbdadm up r0
>
> So looks like it doesn't like --stacked with a virtual IP. Any idea?
>
> Kimly
>
> On Thu, Jun 4, 2015 at 6:26 AM, Igor Cicimov <icicimov at gmail.com> wrote:
>
>>
>> On 04/06/2015 8:50 PM, "Kimly Heler" <kimlyheler at gmail.com> wrote:
>> >
>> > Hello,
>> >
>> > I have 2 of two-node clusters in different data centers. I have
>> configured drbd of lvm resource on each cluster. Now I need to configure a
>> stacked drbd on top of these 2 clusters.
>> >
>> > It should be similar to section 8.4.2 in
>> http://drbd.linbit.com/users-guide-emb/s-pacemaker-stacked-resources.html except
>> I need to find a way to assign floating IPs to the stacked drbd.
>> >
>> > Here is what I derived from the user guide:
>> >
>> > resource clusterA {
>> > net {
>> > protocol C;
>> > }
>> >
>> > on host1-datacenterA {
>> > device /dev/drbd0;
>> > disk /dev/sda6;
>> > address 10.0.0.1:7788;
>> > meta-disk internal;
>> > }
>> >
>> > on host2-datacenterA {
>> > device /dev/drbd0;
>> > disk /dev/sda6;
>> > address 10.0.0.2:7788;
>> > meta-disk internal;
>> > }
>> > }
>> >
>> > resource clusterB {
>> > net {
>> > protocol C;
>> > }
>> >
>> > on host1-datacenterB {
>> > device /dev/drbd0;
>> > disk /dev/sda6;
>> > address 10.0.0.3:7788;
>> > meta-disk internal;
>> > }
>> >
>> > on host2-datacenterB {
>> > device /dev/drbd0;
>> > disk /dev/sda6;
>> > address 10.0.0.3:7788;
>> > meta-disk internal;
>> > }
>> > }
>> >
>> > resource r0 {
>> > net {
>> > protocol A;
>> > }
>> >
>> > stacked-on-top-of clusterA {
>> > device /dev/drbd10;
>> > address 192.168.42.1:7788; # Virtual IP of cluster A
>> > }
>> >
>> > stacked-on-top-of clusterB {
>> > device /dev/drbd10;
>> > address 192.168.42.2:7788; # Virtual IP of cluster B
>> > }
>> > }
>> >
>> > With this, it would error out with the virtual IP address with "IP not
>> found on host".
>> >
>> > I also looked at Floating peers in the user guide, but floating
>> 192.168.42.1:7789 would replace the whole section stacked-on-top-of.
>> >
>> > How can I tell drbd that r0 is a stacked drbd resource, and the peers
>> IPs are floating?
>> >
>>
>> Did you try setting:
>>
>> net.ipv4.ip_nonlocal_bind=1
>>
>> so apps can bind to non local ip?
>> > Thanks in advance
>> >
>> > Kimly
>> >
>> >
>> > _______________________________________________
>> > drbd-user mailing list
>> > drbd-user at lists.linbit.com
>> > http://lists.linbit.com/mailman/listinfo/drbd-user
>> >
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20150604/e2540cb1/attachment.htm>