|
Hello Ajit,
You might have more luck posting to the keepalived list,
http://keepalived.sourceforge.net/listes.html. Is there any strange setup
/ security patches / etc. going on with your setup?
An open source alternative might be ultramonkey, www.ultramonkey.org.
Alternatively you can go with steeleye (commercial). There's a few others,
but I don't remember them offhand.
Cheers,
Peter
> -----Original Message-----
> From: Ajit Kashyap [mailto:ajitkashyap@xxxxxxxxx]
> Sent: Tuesday, September 30, 2003 8:17 AM
> To: LinuxVirtualServer.org users mailing list.
> Subject: Re: Both directors take all vip's with keepalived
>
>
> Since this is not going to work can anyone suggest for
> a commerially available good product which does this
> job? I have to have this up and running in production
> by end of this week.
>
> Appreciate your help.
>
> Ajit
>
>
> --- Ajit Kashyap <ajitkashyap@xxxxxxxxx> wrote:
> > I have installed keepalived 1.1.2 on redhat 9.0 with
> > 2.4.20 kernel. When I run it I'm having problems
> > with
> > vrrp assigning proper ip's. If I have
> > vrrp_sync_group
> > in my config vip's don't get created and I see the
> > following error in syslog
> >
> > Keepalived: Watchdog: Error connecting /tmp/.vrrp
> > wdog
> > socket
> >
> > If I take out vrrp_sync_group from my config then
> > the
> > vip's do get created but all the 5 vip's get created
> > on both the directors instead of 3 on first and 2 on
> > the 2nd as specified in vrrp_instance.
> >
> > Any help would be appreciated.
> >
> > Thanks
> > Ajit
> >
> >
> > **********************************************
> >
> > ! Configuration File for keepalived
> >
> > global_defs {
> > notification_email {
> > test@xxxxxxxx
> > }
> > notification_email_from test@xxxxxxxx
> > smtp_server 111.126.19.48
> > smtp_connect_timeout 30
> > lvs_id ba02_lvs
> > }
> > !
> > ! sync VG1 for www and juice service
> > !
> > vrrp_sync_group VG1 {
> > VI_1
> > VI_2
> > }
> > !
> > ! sync VG2 for cipe to jtc
> > !
> > vrrp_sync_group VG2 {
> > VI_3
> > VI_4
> > }
> > !
> > ! failover - bring up outside vip's for www and
> > juice
> > !
> > vrrp_instance VI_1 {
> > state BACKUP
> > interface eth0
> > virtual_router_id 61
> > priority 100
> > advert_int 1
> > authentication {
> > auth_type PASS
> > auth_pass 1111
> > }
> > virtual_ipaddress {
> > 111.126.19.42
> > 111.126.19.43
> > }
> > }
> >
> >
> > !
> > ! failover - bring up inside vip's for www and juice
> > !
> > vrrp_instance VI_2 {
> > state BACKUP
> > interface eth2
> > virtual_router_id 62
> > priority 100
> > advert_int 1
> > authentication {
> > auth_type PASS
> > auth_pass 1111
> > }
> > virtual_ipaddress {
> > 10.10.10.252
> > }
> > }
> >
> > !
> > ! bring up outside vip for cipe
> > !
> > vrrp_instance VI_3 {
> > state MASTER
> > interface eth0
> > virtual_router_id 63
> > priority 150
> > advert_int 1
> > authentication {
> > auth_type PASS
> > auth_pass 1111
> > }
> > virtual_ipaddress {
> > 111.126.19.44
> > }
> > }
> >
> > !
> > ! bring up inside vip for cipe
> > !
> > vrrp_instance VI_4 {
> > state MASTER
> > interface eth2
> > virtual_router_id 64
> > priority 150
> > advert_int 1
> > authentication {
> > auth_type PASS
> > auth_pass 1111
> > }
> > virtual_ipaddress {
> > 10.10.10.251
> > }
> > }
> > !
> > ! www1 service at port 80
> > !
> > virtual_server 111.126.19.42 80 {
> > delay_loop 3
> > lb_algo rr
> > lb_kind NAT
> > protocol TCP
> >
> > real_server 10.10.10.21 80 {
> > weight 1
> > TCP_CHECK {
> > connect_port 80
> > connect_timeout 3
> > }
> > }
> > real_server 10.10.10.22 80 {
> > weight 1
> > TCP_CHECK {
> > connect_port 80
> > connect_timeout 3
> > }
> > }
> > }
> >
> > !
> > ! www1 service at port 443
> > !
> > virtual_server 111.126.19.42 443 {
> > delay_loop 3
> > lb_algo rr
> > lb_kind NAT
> > protocol TCP
> > persistence_timeout 100
> >
> > real_server 10.10.10.21 443 {
> > weight 1
> > TCP_CHECK {
> > connect_port 443
> > connect_timeout 3
> > }
> > }
> > real_server 10.10.10.22 443 {
> > weight 1
> > TCP_CHECK {
> > connect_port 443
> > connect_timeout 3
> > }
> > }
> > }
> >
> > !
> > ! www2 service at port 80
> > !
> > virtual_server 111.126.19.43 80 {
> > delay_loop 3
> > lb_algo rr
> > lb_kind NAT
> > protocol TCP
> >
> > real_server 10.10.10.25 80 {
> > weight 1
> > TCP_CHECK {
> > connect_port 80
> > connect_timeout 3
> > }
> > }
> > real_server 10.10.10.26 80 {
> > weight 1
> > TCP_CHECK {
> > connect_port 80
> > connect_timeout 3
> > }
> > }
> > }
> >
> > !
> > ! www2 service at port 443
> > !
> > virtual_server 111.126.19.43 443 {
> > delay_loop 3
> > lb_algo rr
> > lb_kind NAT
> > protocol TCP
> > persistence_timeout 100
> >
> > real_server 10.10.10.25 443 {
> > weight 1
> > TCP_CHECK {
> > connect_port 443
> > connect_timeout 3
> > }
> > }
> > real_server 10.10.10.26 443 {
> > weight 1
> > TCP_CHECK {
> > connect_port 443
> > connect_timeout 3
> > }
> > }
> > }
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > The New Yahoo! Shopping - with improved product
> > search
> > http://shopping.yahoo.com
> > _______________________________________________
> > LinuxVirtualServer.org mailing list -
> lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> > Send requests to
> > lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> > or go to
> http://www.in-addr.de/mailman/listinfo/lvs-users
>
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Shopping - with improved product search
> http://shopping.yahoo.com
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
>
|
