Hi,

can heartbeat detect a network failure? If yes, which options should I use?

my test configuration:
- 2 Servers (ubuntu) with heartbeat and drbd.

node1: primary node
node2: secondary node

gateway for both nodes: 10.10.10.1 (pseudo member for this cluster)

drbd: configuration as active/passive system

# cat /etc/ha.d/haresources
node1 IPaddr2::192.168.100.100 drbddisk::r1
Filesystem::/dev/drbd0::/drbd::ext3::defaults

# cat /etc/ha.d/ha.cf
logfile /var/log/ha.log
logfacility local0
keepalive 2
deadtime 20
bcast eth0
node node1 node2
auto_failback on
ping 10.10.10.1

# /usr/lib/heartbeat/heartbeat -V
2.1.4


If I shutdown the switch interface from node1, heartbeat on node1 does
not unmount the drbd device and does not shutdown the virtual ip.
Node1 does not get any answers from node2 and the pseudo member
(gateway, 10.10.10.1) and should realize: "I'm cut from the network, so
I must stop my heartbeat services."

Node2 does not get any heartbeat signal from node1 and mounts the drbd
device and starts the virtual IP 192.168.100.100. Node2 does, what it
should do.

At the moment I don't know, why node1 does not realize the network failure.

Has anybody a hint for me?

Best regards,
thomas polnik.


_______________________________________________
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