Question on Keepalived and vrrp.

Noc Phibee noc at phibee.net
Tue Aug 22 05:56:47 BST 2006


Hi

I request a small information for install Keepalived 1.1.12
on redundant Linux Firewall. ;=)


My Firewall have 4 interface and for all one virtual Ip per interface.
The second firewall are same, 4 interface.

I want know if it's possible and what is the best configuration
for:

     - When one interface are dead, all virtual ip are switched on
    the backup and not only the virtual ip dead ?

    - When a changement are opered, he restart Shorewall for
    he detect all new virtual ip

    - Keepalived use a udp/tcp port for check ? if yes, has I specifier
    a ACCEPT into my shorewall config ?

the last question is because when i start the backup server, he say me:
Aug 22 06:40:18 fw-phibee-lyon-srv2 Keepalived: Starting Keepalived 
v1.1.12 (08/22,2006)
Aug 22 06:40:18 fw-phibee-lyon-srv2 Keepalived_vrrp: Using MII-BMSR NIC 
polling thread...
Aug 22 06:40:18 fw-phibee-lyon-srv2 Keepalived: Starting VRRP child 
process, pid=12723
Aug 22 06:40:18 fw-phibee-lyon-srv2 Keepalived_vrrp: Registering Kernel 
netlink reflector
Aug 22 06:40:18 fw-phibee-lyon-srv2 Keepalived_vrrp: Registering Kernel 
netlink command channel
Aug 22 06:40:18 fw-phibee-lyon-srv2 Keepalived_vrrp: Registering 
gratutious ARP shared channel
Aug 22 06:40:18 fw-phibee-lyon-srv2 Keepalived_vrrp: Configuration is 
using : 46326 Bytes
Aug 22 06:40:18 fw-phibee-lyon-srv2 Keepalived_vrrp: VRRP_Instance(VI_1) 
Entering BACKUP STATE
Aug 22 06:40:18 fw-phibee-lyon-srv2 Keepalived_vrrp: VRRP_Instance(VI_2) 
Entering BACKUP STATE
Aug 22 06:40:18 fw-phibee-lyon-srv2 Keepalived_vrrp: VRRP_Instance(VI_3) 
Entering BACKUP STATE
Aug 22 06:40:18 fw-phibee-lyon-srv2 Keepalived_vrrp: VRRP_Instance(VI_4) 
Entering BACKUP STATE
Aug 22 06:40:18 fw-phibee-lyon-srv2 Keepalived_vrrp: VRRP sockpool: 
[ifindex(2), proto(112), fd(7,8)]
Aug 22 06:40:18 fw-phibee-lyon-srv2 Keepalived_vrrp: VRRP sockpool: 
[ifindex(3), proto(112), fd(9,10)]
Aug 22 06:40:18 fw-phibee-lyon-srv2 Keepalived_vrrp: VRRP sockpool: 
[ifindex(4), proto(112), fd(11,12)]
Aug 22 06:40:18 fw-phibee-lyon-srv2 Keepalived_vrrp: VRRP sockpool: 
[ifindex(5), proto(112), fd(13,14)]
Aug 22 06:40:22 fw-phibee-lyon-srv2 Keepalived_vrrp: VRRP_Instance(VI_1) 
Transition to MASTER STATE
Aug 22 06:40:23 fw-phibee-lyon-srv2 Keepalived_vrrp: VRRP_Instance(VI_1) 
Entering MASTER STATE
Aug 22 06:40:23 fw-phibee-lyon-srv2 Keepalived_vrrp: VRRP_Instance(VI_1) 
setting protocol VIPs.
Aug 22 06:40:23 fw-phibee-lyon-srv2 Keepalived_vrrp: VRRP_Instance(VI_1) 
Sending gratuitous ARPs on eth0 for 192.168.1.254

why he start in master state on VI_1 ... the Master are good and he 
answer at ping



Thanks for your help
bye




Search lvs-users Archives
Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort

More information about the lvs-users mailing list