Hi,
any Ideas on the above tcpdump, Ive noticed I get the following out out int my /var/log/messages Oct 16 17:03:35 dnstest3 avahi-daemon[2481]: Registering new address record for 172.69.128.112 on eth0. Oct 16 17:03:35 dnstest3 avahi-daemon[2481]: Registering new address record for 172.69.128.104 on eth0. Oct 16 17:03:35 dnstest3 avahi-daemon[2481]: Registering HINFO record with values 'I686'/'LINUX'. Oct 16 17:03:55 dnstest3 avahi-daemon[2481]: Withdrawing address record for fe80::216:e6ff:fef0:1a63 on eth0. Oct 16 17:03:55 dnstest3 avahi-daemon[2481]: Withdrawing address record for 172.69.128.104 on eth0. Oct 16 17:03:55 dnstest3 avahi-daemon[2481]: Host name conflict, retrying with <dnstest3-5167> Oct 16 17:03:55 dnstest3 avahi-daemon[2481]: Registering new address record for fe80::216:e6ff:fef0:1a63 on eth0. Oct 16 17:03:55 dnstest3 avahi-daemon[2481]: Registering new address record for 172.69.128.112 on eth0. Oct 16 17:03:55 dnstest3 avahi-daemon[2481]: Registering new address record for 172.69.128.104 on eth0. Oct 16 17:03:55 dnstest3 avahi-daemon[2481]: Registering HINFO record with values 'I686'/'LINUX'. Oct 16 17:04:15 dnstest3 avahi-daemon[2481]: Withdrawing address record for fe80::216:e6ff:fef0:1a63 on eth0. Oct 16 17:04:15 dnstest3 avahi-daemon[2481]: Withdrawing address record for 172.69.128.104 on eth0. On 10/15/07, Ilo Lorusso <[EMAIL PROTECTED]> wrote: > > > restarted HA on both nodes , > > got a new clusterMAC of > > clustermac=B1:07:84:AB:56:34 > > when I do a tcpdump on both the nodes this is the output, > > > node2 : > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes > 14:20:44.540640 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20:44.642330 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > 14:20:44.743305 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20:44.844299 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > 14:20:44.945264 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20:45.046248 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > 14:20:45.147222 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20:45.248205 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > 14:20:45.297583 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20:45.349210 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20: 45.399797 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > 14:20:45.450165 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > 14:20:45.501759 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20:45.603734 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > 14:20:45.705724 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20:45.807709 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > 14:20:45.909688 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20:46.011676 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > 14:20:46.113651 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20:46.219577 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > > > > Node1: > > 14:20:44.559691 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20:44.661413 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > 14:20:44.762386 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20:44.863383 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > 14:20:44.964352 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20:45.065340 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > 14:20:45.166314 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20:45.267310 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > 14:20:45.316547 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20:45.368314 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20:45.418762 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > 14:20:45.469259 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > 14:20:45.520727 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20:45.622706 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > 14:20:45.724698 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20:45.826675 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > 14:20:45.928657 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20:46.030643 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > 14:20:46.132631 arp who-has 172.69.128.112 tell 172.69.128.112 > 14:20:46.238552 arp reply 172.69.128.112 is-at b1:07:00:04:ab:00 > > > > On 10/15/07, Michael Schwartzkopff <[EMAIL PROTECTED]> wrote: > > > > Am Montag, 15. Oktober 2007 13:02 schrieb Ilo Lorusso: > > > Hi, > > > > > > Okay I removed the arp and mac settings I and configured, > > > > > > I can see that HA gave my iptables a clustermac of > > > clustermac=B1:07:84:AB:56:34 > > > > > > but when I check my arp table on my windows host I get > > > > > > 172.69.128.112 b1-07-a4-ab-56-bd dynamic, > > > > > > and therefore cant ping or connect to the cluster?? > > > > Something VERY strange is happening in your network. Can you please > > tcpdump > > all ARP traffic on the heartbeat nodes? Something like: > > > > tcpdump -n -i eth0 arp > > > > When a IPaddr2 resource starts it should anncounce its MAC address in > > the > > network. So please could you see if it announces the correct MAC > > address. So > > we can see if your cluster announces the wrong MAC address of your net > > learns > > the wrong address. Thanks. > > > > -- > > Dr. Michael Schwartzkopff > > MultiNET Services GmbH > > Addresse: Bretonischer Ring 7; 85630 Grasbrunn; Germany > > Tel: +49 - 89 - 45 69 11 0 > > Fax: +49 - 89 - 45 69 11 21 > > mob: +49 - 174 - 343 28 75 > > > > mail: [EMAIL PROTECTED] > > web: www.multinet.de > > > > Sitz der Gesellschaft: 85630 Grasbrunn > > Registergericht: Amtsgericht München HRB 114375 > > Geschäftsführer: Günter Jurgeneit, Hubert Martens > > > > --- > > > > PGP Fingerprint: F919 3919 FF12 ED5A 2801 DEA6 AA77 57A4 EDD8 979B > > Skype: misch42 > > _______________________________________________ > > 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
