|
Hi Alexandre,
first of all thanks for spendng time with my Problem and wow what a great
program you have realised here :)
> >> My new Problem is that we have an Router (Bintec XL2) which does not
> >react
> >> on "Gratious ARP". And the Network guys say they can not change the
> >> ARP-Timeout. So at the moment I am looking at 20-30 minutes timout :(
> >> ARP-Proxy would be to much for the Router as it has a lot to do.
> >>
> => Bintec (I don t know this hardware)
Bintec is a German Company - here quite well known ;) We use a lot of HDSL
connections and Bintec is (as far as I am informed) the only one who can
deal well with that.
> So I can see 2 solutions :) :
>
> 1. You go into the network room and burn the Bintec switch :).
yea, that would be fun ;)
> 2. I slightly enhance the Keepalived/VRRP code to extend it to the
> ARP-Reply. But this can be possible that your Bintec doesn t handle GARP
> that way too... But we can test. If this work I will apply into the new
> code.
As far as I have found out till now, ARP-Reply will not help :(
Bintec know of the Problem and are solving it, but it will take 4 months :(
This is what it does : so long the Router can reach the IP-Address it does
not update its ARP Cache :(
Solutions :
1. take down the VIP (and mybee the Card on the failed LB) for 90-100 Sec.
so that the cache in the Bintec timouts. Then start it again. Could that be
done with notify_failure/notify_master ?
2. Somehow use a VMAC. I have found an "ip arp" patch here
http://www.linuxvirtualserver.org/~julian/#iparp - could that possibly solve
my Problem ?
I would then use the notify_master to set a Private MAC and notify_failure
to remove it again. send_arp of the piranha package could be used to do the
Gratious ARP :)
3. May bee someone else has an Idea :)
Solution 2 ist probably better because the downtime will be the smallest :)
Greetings
Christian
|
