Hi, Hamaguchi-san send_arp exists in two versions depending on the environment. https://github.com/ClusterLabs/resource-agents/blob/master/tools/send_arp.libnet.c https://github.com/ClusterLabs/resource-agents/blob/master/tools/send_arp.linux.c
Those that contain in your environment, it seems that it is send_arp.linux.c. send_arp.linux.c has been made to also work with the same options as the send_arp.libnet.c. However, -i and -p In send_arp.linux.c is not used. send_arp.linux.c sends arp every second because it is driven by the alarm(1). https://github.com/ClusterLabs/resource-agents/blob/master/tools/send_arp.linux.c#L384 This interval cannot be changed because they are hard-coded. Regards, Yusuke > -----Original Message----- > From: Shinjiro Hamaguchi [mailto:hamagu...@agile.ne.jp] > Sent: Wednesday, October 05, 2016 1:57 PM > To: users@clusterlabs.org > Subject: Re: [ClusterLabs] IPaddr2, interval between unsolicited ARP packets > > Matsushima-san > > > Thank you very much for your reply. > And sorry for late reply. > > > >Do you get same result by executing the command manually with different > parameters like this? > I tried following command but same result (1sec interval) > > [command used to send unsolicited arp] > /usr/libexec/heartbeat/send_arp -i 1500 -r 8 eth0 192.168.12.215 auto not_used > not_used > > [result of tcudump] > 04:31:50.475928 ARP, Request who-has 192.168.12.215 (Broadcast) tell > 192.168.12.215, length 28 > 04:31:51.476053 ARP, Request who-has 192.168.12.215 (Broadcast) tell > 192.168.12.215, length 28 > 04:31:52.476146 ARP, Request who-has 192.168.12.215 (Broadcast) tell > 192.168.12.215, length 28 > 04:31:53.476246 ARP, Request who-has 192.168.12.215 (Broadcast) tell > 192.168.12.215, length 28 > 04:31:54.476287 ARP, Request who-has 192.168.12.215 (Broadcast) tell > 192.168.12.215, length 28 > 04:31:55.476406 ARP, Request who-has 192.168.12.215 (Broadcast) tell > 192.168.12.215, length 28 > 04:31:56.476448 ARP, Request who-has 192.168.12.215 (Broadcast) tell > 192.168.12.215, length 28 > 04:31:57.476572 ARP, Request who-has 192.168.12.215 (Broadcast) tell > 192.168.12.215, length 28 > > >Please also make sure the PID file has been created properly. > When I checked manually with send_arp command, I didn't use send_arp command > with "-p" option. > > Even when I did fail-over of IPaddr2resource (not manually execute send_arp > command), I couldn't see pid file generated at /var/run/resource-agents/. > I used following command to see if pid file generated. > > watch -n0.1 "ls -la /var/run/resource-agents/" > > > Thank you in advance. > > > On Wed, Oct 5, 2016 at 12:20 PM, Digimer <li...@alteeve.ca> wrote: > > > > > > -------- Forwarded Message -------- > Subject: Re: [ClusterLabs] IPaddr2, interval between unsolicited ARP > packets > Date: Tue, 4 Oct 2016 11:18:37 +0900 > From: Takehiro Matsushima <takehiro.dream...@gmail.com> > Reply-To: Cluster Labs - All topics related to open-source clustering > welcomed <users@clusterlabs.org> > To: Cluster Labs - All topics related to open-source clustering welcomed > <users@clusterlabs.org> > > Hello Hamaguchi-san, > > Do you get same result by executing the command manually with > different parameters like this? > #/usr/libexec/heartbeat/send_arp -i 1500 -r 8 -p > /var/run/resource-agents/send_arp-192.168.12.215 eth0 > 192.168.12.215 > auto not_used not_used > > Please also make sure the PID file has been created properly. > > Thank you, > > Takehiro MATSUSHIMA > > 2016-10-03 14:45 GMT+09:00 Shinjiro Hamaguchi > <hamagu...@agile.ne.jp>: > > Hello everyone!! > > > > > > I'm using IPaddr2 for VIP. > > > > In the IPaddr2 document, it say interval between unsolicited ARP > packets is > > default 200msec and can change it using option "-i", but when i check > with > > tcpdump, it looks like sending arp every 1000msec fixed. > > > > Does someone have any idea ? > > > > Thank you in advance. > > > > > > [environment] > > kvm, centOS 6.8 > > pacemaker-1.1.14-8.el6_8.1.x86_64 > > cman-3.0.12.1-78.el6.x86_64 > > resource-agents-3.9.5-34.el6_8.2.x86_64 > > > > > > [command used to send unsolicited arp] > > NOTE: i got this command from /var/log/cluster/corosync.log > > #/usr/libexec/heartbeat/send_arp -i 200 -r 5 -p > > /var/run/resource-agents/send_arp-192.168.12.215 eth0 > 192.168.12.215 auto > > not_used not_used > > > > [result of tcudump] > > > > #tcpdump arp > > > > tcpdump: verbose output suppressed, use -v or -vv for full protocol > decode > > > > listening on eth0, link-type EN10MB (Ethernet), capture size 65535 > bytes > > > > 05:28:17.267296 ARP, Request who-has 192.168.12.215 (Broadcast) tell > > 192.168.12.215, length 28 > > > > 05:28:18.267519 ARP, Request who-has 192.168.12.215 (Broadcast) tell > > 192.168.12.215, length 28 > > > > 05:28:19.267638 ARP, Request who-has 192.168.12.215 (Broadcast) tell > > 192.168.12.215, length 28 > > > > 05:28:20.267715 ARP, Request who-has 192.168.12.215 (Broadcast) tell > > 192.168.12.215, length 28 > > > > 05:28:21.267801 ARP, Request who-has 192.168.12.215 (Broadcast) tell > > 192.168.12.215, length 28 > > > > > > > > _______________________________________________ > > Users mailing list: Users@clusterlabs.org > > http://clusterlabs.org/mailman/listinfo/users > <http://clusterlabs.org/mailman/listinfo/users> > > > > Project Home: http://www.clusterlabs.org > > Getting started: > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > <http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf> > > Bugs: http://bugs.clusterlabs.org > > > > _______________________________________________ > Users mailing list: Users@clusterlabs.org > http://clusterlabs.org/mailman/listinfo/users > <http://clusterlabs.org/mailman/listinfo/users> > > Project Home: http://www.clusterlabs.org > Getting started: > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > <http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf> > Bugs: http://bugs.clusterlabs.org > > _______________________________________________ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
