Greetings,

I have a two node cluster (squash and turnip).

+------------+           +------------+
| /dev/ttyS1 |  <====>   | /dev/ttyS1 |
|            |           |            |
|  squash    |           |  turnip    |
|            |           |            |
|     eth2   |  <====>   |   eth2     |
| (10.0.0.1) |           | (10.0.0.2) |
+------------+           +------------+

squash% cat /etc/ha.d/ha.cf
use_logd on

keepalive 1
deadtime 5
initdead 120

udpport 694
baud 115200
serial /dev/ttyS1
bcast eth2

node squash
node turnip

ping 131.212.4.166
ping 192.168.115.46

crm on


It appears that the heartbeat module does not recover when I issue
'ifdown eth2 && sleep 10 && ifup eth2'.

All relevant logging and diagnostics look correct before downing the
interface:

squash% sudo tcpdump -tqn -i eth2
tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode
listening on eth2, link-type EN10MB (Ethernet), capture size 96 bytes
IP 10.0.0.2.32768 > 10.0.0.7.694: UDP, length 209
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 208
IP 10.0.0.2.32768 > 10.0.0.7.694: UDP, length 206
IP 10.0.0.2.32768 > 10.0.0.7.694: UDP, length 209
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 208
IP 10.0.0.2.32768 > 10.0.0.7.694: UDP, length 209
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 208

turnip% sudo tcpdump -tqn -i eth2
tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode
listening on eth2, link-type EN10MB (Ethernet), capture size 96 bytes
IP 10.0.0.2.32768 > 10.0.0.7.694: UDP, length 209
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 205
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 208
IP 10.0.0.2.32768 > 10.0.0.7.694: UDP, length 209
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 208
IP 10.0.0.2.32768 > 10.0.0.7.694: UDP, length 209
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 208

squash% echo "squash eth2 - $(cl_status hblinkstatus squash eth2)" &&
echo "turnip eth2 - $(cl_status hblinkstatus turnip eth2)"
squash eth2 - up
turnip eth2 - up

turnip% echo "squash eth2 - $(cl_status hblinkstatus squash eth2)" &&
echo "turnip eth2 - $(cl_status hblinkstatus turnip eth2)"
squash eth2 - up
turnip eth2 - up

squash% sudo arp -n
Address          HWtype  HWaddress           Flags Mask   Iface
131.212.4.166    ether   00:D0:01:BA:D4:00   C            eth0
192.168.115.46   ether   00:D0:01:BA:D4:00   C            eth1

turnip% sudo arp -n
Address          HWtype  HWaddress           Flags Mask   Iface
192.168.115.46   ether   00:D0:01:BA:D4:00   C            eth1
131.212.4.166    ether   00:D0:01:BA:D4:00   C            eth0


After downing and upping the interface though, the broadcast
functionality of the heartbeat module does not seem to recover.

turnip# ifdown eth2 && sleep 10 && ifup eth2

squash% sudo tcpdump -tqn -i eth2
tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode
listening on eth2, link-type EN10MB (Ethernet), capture size 96 bytes
IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group
record(s), length 28
IP6 :: > ff02::1:ff0e:d8f: ICMP6, neighbor solicitation, who has
fe80::21b:21ff:fe0e:d8f, length 24
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 209
arp who-has 10.0.0.7 tell 10.0.0.2
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 206
IP6 fe80::21b:21ff:fe0e:d8f > ff02::2: ICMP6, router solicitation,
length 16
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 209
arp who-has 10.0.0.7 tell 10.0.0.2
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 209
IP6 fe80::21b:21ff:fe0e:d8f > ff02::16: HBH ICMP6, multicast listener
report v2, 1 group record(s), length 28
arp who-has 10.0.0.7 tell 10.0.0.2
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 209
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 209
arp who-has 10.0.0.7 tell 10.0.0.2

turnip% sudo tcpdump -tqn -i eth2
tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode
listening on eth2, link-type EN10MB (Ethernet), capture size 96 bytes
arp who-has 10.0.0.7 tell 10.0.0.2
IP6 fe80::21b:21ff:fe0e:d8f > ff02::2: ICMP6, router solicitation,
length 16
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 209
arp who-has 10.0.0.7 tell 10.0.0.2
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 209
arp who-has 10.0.0.7 tell 10.0.0.2
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 206
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 209
arp who-has 10.0.0.7 tell 10.0.0.2
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 209
arp who-has 10.0.0.7 tell 10.0.0.2
IP6 fe80::21b:21ff:fe0e:d8f > ff02::2: ICMP6, router solicitation,
length 16
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 209
arp who-has 10.0.0.7 tell 10.0.0.2
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 209
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 206
IP 10.0.0.1.32768 > 10.0.0.7.694: UDP, length 209

squash% echo "squash eth2 - $(cl_status hblinkstatus squash eth2)" &&
echo "turnip eth2 - $(cl_status hblinkstatus turnip eth2)"
squash eth2 - up
turnip eth2 - dead

turnip% echo "squash eth2 - $(cl_status hblinkstatus squash eth2)" &&
echo "turnip eth2 - $(cl_status hblinkstatus turnip eth2)"
squash eth2 - up
turnip eth2 - up

squash% sudo arp -n
Address          HWtype  HWaddress           Flags Mask   Iface
131.212.4.166    ether   00:D0:01:BA:D4:00   C            eth0
192.168.115.46   ether   00:D0:01:BA:D4:00   C            eth1

turnip% sudo arp -n
Address          HWtype  HWaddress           Flags Mask   Iface
192.168.115.46   ether   00:D0:01:BA:D4:00   C            eth1
131.212.4.166    ether   00:D0:01:BA:D4:00   C            eth0
10.0.0.7                 (incomplete)                     eth2


After downing and upping the interface, the broadcast address is
apparently looked at as a unicast address. Is this how the software is
supposed to work, or is this a bug?

Thanks,

-- 
Matt Zagrabelny - [EMAIL PROTECTED] - (218) 726 8844
University of Minnesota Duluth
Information Technology Systems & Services
PGP key 1024D/84E22DA2 2005-11-07
Fingerprint: 78F9 18B3 EF58 56F5 FC85  C5CA 53E7 887F 84E2 2DA2

He is not a fool who gives up what he cannot keep to gain what he cannot
lose.
-Jim Elliot

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to