On 12/07/2021 23:27, Kiril Pashin wrote:
Hi ,
is it valid to use the same network adapter interface on the same host to be
part of multiple
heart beat rings ?
There should be no problem from technical side, but I wouldn't call this
use case "valid". Idea of multiple rings is to have multiple independent
connections between nodes - something what one nic simply doesn't provide.
The scenario is hostA has eth0 ( ip 192.10.10.1 ) interface and hostB has eth0 (
192.20.20.1 ) and eth1 ( 192.20.20.2 ) .
This is unsupported configuration
Are there any restrictions to form two heartbeat rings { eth0, eth0 } and {
eth0, eth1 }
Technically only restriction is based on IP. But to make it reliable one
should use multiple NICs with multiple links and multiple switches.
as well as create a nozzle device to be able to ping hostA in case eth0 or eth1
go down on hostB
It is definitively possible to create noozle device which will allow to
ping hostA in case some of nic fails, but not in the way described in
config snip. Noozle device should have different IP subnet (noozle is
basically yet another network card).
nodelist {
node {
ring0_addr: 192.10.10.1
ring1_addr: 192.10.10.1
name: node1
nodeid: 1
}
node {
ring0_addr: 192.20.20.1
ring1_addr: 192.20.20.2
name: node2
nodeid: 2
}
}
nozzle {
name: noz01
ipaddr: 192.168.10.0
ipprefix: 24
}
This config will definitively not work.
Regards,
Honza
Thanks,
Kiril Pashin
DB2 Purescale Development & Support
[email protected]
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
