Currently, no there is no way to specify two addresses.  However this
doesn't mean you can't bond the interfaces and tell DRBD to use the
bond0 address instead.

Brian

Andreas Reschke wrote:
> Hello,
> at the moment I'm building a new HA-Cluster (Active-Active) with 2 servers 
> in the DMZ. The server has 5 NIC, 2 for the LAN in the DMZ , 2 for 
> heartbeat and DRBD and 1 unconfigured.
> It is possible to configure 2 IP-adresses in the drbd.conf for 2 transport 
> channels? Now all data are going over only 1 NIC.
>
> My /etc/drbd.conf:
> resource drbd0 {
>   protocol C;
>   incon-degr-cmd "echo '!DRBD! pri on incon-degr'";
>   startup { wfc-timeout 0; degr-wfc-timeout     120; }
>   disk { on-io-error detach; } # or panic, ...
>   syncer {
>      group 0;
>      rate 12M;
>   }
>   on bgstsapdmz1 {
>     device /dev/drbd0;
>     disk /dev/mapper/sap_vg-sap_proxy;
>     address 11.0.0.2:7788;
>     address 11.0.0.3:7788;
>     meta-disk internal;
>   }
>   on bgstsapdmz2 {
>     device /dev/drbd0;
>     disk /dev/mapper/sap_vg-sap_proxy;
>     address 11.0.0.5:7788;
>     address 11.0.0.6:7788;
>     meta-disk internal;
>   }
> }
> resource drbd1 {
>   protocol C;
>   incon-degr-cmd "echo '!DRBD! pri on incon-degr'";
>   startup { wfc-timeout 0; degr-wfc-timeout     120; }
>   disk { on-io-error detach; } # or panic, ...
>   syncer {
>      group 0;
>      rate 12M;
>   }
>   on bgstsapdmz1 {
>     device /dev/drbd1;
>     disk /dev/mapper/sap_vg-bussiness_connector;
>     address 11.0.0.2:7789;
>     address 11.0.0.3:7789;
>     meta-disk internal;
>   }
>   on bgstsapdmz2 {
>     device /dev/drbd1;
>     disk /dev/mapper/sap_vg-bussiness_connector;
>     address 11.0.0.5:7789;
>     address 11.0.0.6:7789;
>     meta-disk internal;
>   }
> }
>  
> Im using static routes for this net:
> bgstsapdmz2:~ # netstat -rn
> Kernel IP Routentabelle
> Ziel            Router          Genmask         Flags   MSS Fenster irtt 
> Iface
> 11.0.0.1        0.0.0.0         255.255.255.255 UH        0 0          0 
> eth2
> 11.0.0.3        0.0.0.0         255.255.255.255 UH        0 0          0 
> eth4
> 11.0.0.2        0.0.0.0         255.255.255.255 UH        0 0          0 
> eth3
> XXX.XX.XXX.0    0.0.0.0         255.255.255.0   U         0 0          0 
> eth0
> XXX.XX.XXX.0    0.0.0.0         255.255.255.0   U         0 0          0 
> eth1
> 169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 
> eth0
> 127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0 
> lo
> 0.0.0.0         XXX.XX.XXX.1    0.0.0.0         UG        0 0          0 
> eth0
>
> eth0: XXX.XX.XXX.XX > public IP
> eth1: XXX.XX.XXX.XX > public IP
> eth2: 11.0.0.2 > Heartbeat + DRBD
> eth3: 11.0.0.3 > Heartbeat + DRBD
> eth4: 11.0.0.4 > Heartbeat + DRBD
>  
> Gruß 
> Andreas Reschke
> ________________________________________________________________
> BG-IM173
> Unix/Linux-Administration
>  
> Behr GmbH & Co. KG
> ST B29, 3.OG
>  
> Tel.: +49 711 896-4598
> Fax: ++49 711-8902-4598
> Mobil: 0173-3197397
> [email protected]
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>   
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to