Hi!
After option="-I <addr>" did not work I had a look into the RA: It's a big
mess!
---
ping_update() {
if have_binary fping; then
fping_check
active=$?
else
ping_check
active=$?
fi
[...]
---
So if the system has an fping (mine has!), the RA uses fping; otherwise it
uses ping.
Also, $OCF_RESKEY_options is only used for ping, but not for fping!
Needless to say that thje options of ping and fping cannot be compared.
Welcome to the mess!
At the very least the documentation should be updated!
Regards,
Ulrich
>>> Lars Ellenberg <[email protected]> schrieb am 04.09.2014 um 15:28
in
Nachricht <[email protected]>:
> On Thu, Sep 04, 2014 at 02:32:14PM +0200, Ulrich Windl wrote:
>> Hi!
>>
>> I'm using ocf:pacemaker:ping to ping some specific address. The requirement
> is that a specific source address (that is on a local interface) is being
> used to ping a destination. So if the resource moves between nodes, the same
> source address shall be used.
>>
>> The address to use is a secondary adress on interface bond0, like
bond0:xyz.
> I can spacify "-I bond0" and "-I bond0:xyz", but the latter seems to be
> ignores, as if I just said "-I bond0". Ping is from
iputils-ss021109-292.28.1
> (SLES11 SP3).
>>
>> I had this requirement for HP-UX years ago, and the solution was to install
a
> special local ping that allowed to select the source address.
>
>> So my preferences are:
>> 1) Get it done with the software I have
>
> ping -w 2 -c 3 -I 127.0.0.1 8.8.8.8
> ping: sendmsg: Invalid argument
> ping: sendmsg: Invalid argument
> PING 8.8.8.8 (8.8.8.8) from 127.0.0.1 : 56(84) bytes of data.
>
> --- 8.8.8.8 ping statistics ---
> 2 packets transmitted, 0 received, 100% packet loss, time 1008ms
>
> ping -w 2 -c 3 -I 10.11.12.13 8.8.8.8
> bind: Cannot assign requested address
>
> ping -w 2 -c 3 -I 10.43.9.55 8.8.8.8
> PING 8.8.8.8 (8.8.8.8) from 10.43.9.55 : 56(84) bytes of data.
> 64 bytes from 8.8.8.8: icmp_seq=1 ttl=41 time=27.4 ms
> 64 bytes from 8.8.8.8: icmp_seq=2 ttl=41 time=27.4 ms
>
> --- 8.8.8.8 ping statistics ---
> 2 packets transmitted, 2 received, 0% packet loss, time 1000ms
> rtt min/avg/max/mdev = 27.405/27.430/27.456/0.167 ms
>
> Does that help?
>
> --
> : Lars Ellenberg
> : LINBIT | Your Way to High Availability
> : DRBD/HA support and consulting http://www.linbit.com
>
> DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
> _______________________________________________
> 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
