|
Hi Alex,
sorry for delay...
>I have two computers with keepalived daemon.
>If I manualy kill keepalived daemon (killall keepalived ) on one from
>them, as second begin him work. Greate: keepalive work.
yes...
>If I manualy kill virtual_address ( ip addr del 10.0.0.233 dev eth2 ) on
>the first computer ( MASTER ) , as keepalived daemon on the BACKUP
>didn't recognize that something happaned with MASTER , and didn't up
>virtual_ipaddress.
>
>How explain it, where the BUG ???
Hmm... oh yes.... currently keepalived doesn t handle netlink ip check
before sending advert. The netlink call to set VRRP VIP is done during
bootstrap, then during checkers stats.
So the answer is.... It is a "bug" well, a lake of time from my side to add
that strong integrity check....
The VRRP part need to be enhanced... I am currenlty working on this with
netlink. The VIP presence check is needed for checkers because currenlty if
you run both healthcheck & failover, keepalived perform healthcheck even if
VIP is not owned by the BACKUP director... So the extension here is :
"perform healthcheck if VRRP VIP or IP is owned and correctly set".
I have been very busy with my job so I had to delayed a little my work. But
will be back to strong work :)
Currenlty the keepalived framework is cleaner than it was. Healthchecker
can be developed much more quickly... This work done, I need to spend more
time on netlink & VRRP....
VRRP framework need to be enhanced on the sending advert proc : checking
IFF_UP flags, netlink stats, probably MII register if NIC offer it, ....
If someone has some kind of code here, it will help me... Like : "before
sending something to the world, check if we can send it using the NIC :
need to test IFF stats, netlink, ..."
How is the best way to handle this.... Any comments will be welcome.
Best regards,
Alexandre
>P.S:
>I'm not using keepalived with LVS, i need just vrrpd part of it.
>
>-----------
>Configurations:
>
>on the first computer:
>
>vrrp_instance VI_1 {
> state MASTER
> interface eth2
> virtual_router_id 51
> priority 100
> advert_int 1
> authentication {
> auth_type AH
> auth_pass 1111
> }
> virtual_ipaddress {
> 10.0.0.233
> }
>}
>
>on the second computer:
>
>vrrp_instance VI_1 {
> state BACKUP
> interface eth2
> virtual_router_id 51
> priority 99
> advert_int 1
> authentication {
> auth_type AH
> auth_pass 1111
> }
> virtual_ipaddress {
> 10.0.0.233
> }
>}
|
