Re: Backup Web Server

2002-11-25 Thread Steve Mickeler

#2 (vrrp) is a subset of #3 (LVS / keepalived / vrrp )

I have several boxes configured as master / backup routers with the VRRP
component of keepalived. You just need to configure keepalived to not use
LVS and then you have a clean and simple VRRP install.


On Mon, 25 Nov 2002, Jeremy Zawodny wrote:

> On Mon, Nov 25, 2002 at 02:17:22PM -0500, Steve Mickeler wrote:
> >
> > Theres a couple of ways you can do this.
> >
> > 1) round robin dns : 2 servers with their own IP's, each serving up the
> > website. If one goes down, you still get a 50% success rate.
> >
> > 2) VRRP via keepalived  - http://www.keepalived.org/ : 2 servers, 1 real
> > floating IP that is bound to the active server. If the active server dies,
> > the IP's are picked up by the standby server and keeps on going.
> >
> > 3) LVS ( Linux Virtual Server ) http://www.linuxvirtualserver.org/ : This
> > is the most involved setup but will also give you the most scalability and
> > availabilty by creating farms of local servers that the inbound requests
> > are balanced across. It can also do enhanced checks on the local servers
> > to make sure that only healthy nodes are answering requests.
>
> You make it sound as if #2 and #3 are disconnected.  But reading the
> web site for #2 makes it sound as if it only works *with* LVS.  Is
> that not true?
>
> Jeremy
> --
> Jeremy D. Zawodny |  Perl, Web, MySQL, Linux Magazine, Yahoo!
> <[EMAIL PROTECTED]>  |  http://jeremy.zawodny.com/
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>



[-] Steve Mickeler [ [EMAIL PROTECTED] ]

[|] Todays root password is brought to you by /dev/random

[+] 1024D/9AA80CDF = 4103 9E35 2713 D432 924F  3C2E A7B9 A0FE 9AA8 0CDF


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Backup Web Server

2002-11-25 Thread Steve Mickeler

Theres a couple of ways you can do this.

1) round robin dns : 2 servers with their own IP's, each serving up the
website. If one goes down, you still get a 50% success rate.

2) VRRP via keepalived  - http://www.keepalived.org/ : 2 servers, 1 real
floating IP that is bound to the active server. If the active server dies,
the IP's are picked up by the standby server and keeps on going.

3) LVS ( Linux Virtual Server ) http://www.linuxvirtualserver.org/ : This
is the most involved setup but will also give you the most scalability and
availabilty by creating farms of local servers that the inbound requests
are balanced across. It can also do enhanced checks on the local servers
to make sure that only healthy nodes are answering requests.



On Mon, 25 Nov 2002 [EMAIL PROTECTED] wrote:

>
>Can anyone pls tell me how to setup a Backup Web Server..meaning if the
> primary Web Server fails, it will  automatically go to a seperate Web
> Server.
>
>   ex.
>
>  Home User - www.abc.com
>
>   Server Unit 1 - www.abc.com : but if the unit bogs down
>  it will go to,
>
>   Server Unit 2 - www.abc.com
>
> Can this be possible?
>
> Rizal
>
> "If you think you play too much, play more"
>
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>



[-] Steve Mickeler [ [EMAIL PROTECTED] ]

[|] Todays root password is brought to you by /dev/random

[+] 1024D/9AA80CDF = 4103 9E35 2713 D432 924F  3C2E A7B9 A0FE 9AA8 0CDF


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: failing all vrrp interfaces.

2002-09-11 Thread Steve Mickeler

It appears that the vrrp IP is removed when a regular kill signal is
issued the the vrrpd PID. It was only when kill -9 was issued to the PID
that the IP would be left on the interface.

I've also decided to use keepalived (http://keepalived.sourceforge.net/)
since its vrrpd implemenation is quite nice.

I would highly suggest anyone looking into vrrp with linux take a look at
keepalived.

Cheers.

 On Wed, 11 Sep 2002, Philipp Schmidt wrote:

> On Mon, 2002-09-09 13:56:10 -0400, Steve Mickeler <[EMAIL PROTECTED]>
> wrote in message <[EMAIL PROTECTED]>:
> >
> > The issue I'm trying to tackle is dealing with multiple interfaces in
> > vrrpd. I need to make sure that all vrrpd daemons and aliases on the
> > failed server are brought down.
> >
> > One thing I noticed is that if you kill the the vrrpd PID's, the vrrp
> > virtual IP address is still aliased to the server that has its
> > vrrpd processes killed. if you do an "ip address ls" you can see the
> > virtual IP address bound to the interface.
> >
> > Any idea of how to drop the alias when the vrrpd daemon is killed ?
> >
>
> have a look on the "ip" utility (iproute2 package)
>
> AVE!
>   phils...
>
> --
>  PHILIPP SCHMIDT / phils - - + - - > [EMAIL PROTECTED]
>  ` - - > http://home.pages.de/~phils/
>  --> ONLINE fuer Berlin & BRB? IN-Berlin! ([EMAIL PROTECTED]) <--
>
> Lbh unir whfg ivbyngrq gur Qvtvgny Zvyraavhz Pbclevtug Npg ol oernxvat gur
> cebgrpgvba bs pbclevtugrq zngrevny.  Vs lbh ner abg n pvgvmra be erfvqrag bs
> gur HFN, lbh evfx orvat vzcevfbarq naq uryq jvgubhg onvy sbe hc gb gjb jrrxf
> hcba ragel gb gur HFN (c) Copyright 2001 by Hartmann Schaffer (signature only)
>
> :wq
>



[-] Steve Mickeler [ [EMAIL PROTECTED] ]

[|] Todays root password is brought to you by /dev/random

[+] 1024D/9AA80CDF = 4103 9E35 2713 D432 924F  3C2E A7B9 A0FE 9AA8 0CDF




failing all vrrp interfaces.

2002-09-09 Thread Steve Mickeler

The issue I'm trying to tackle is dealing with multiple interfaces in
vrrpd. I need to make sure that all vrrpd daemons and aliases on the
failed server are brought down.

One thing I noticed is that if you kill the the vrrpd PID's, the vrrp
virtual IP address is still aliased to the server that has its
vrrpd processes killed. if you do an "ip address ls" you can see the
virtual IP address bound to the interface.

Any idea of how to drop the alias when the vrrpd daemon is killed ?




Thanks.


[-] Steve Mickeler [ [EMAIL PROTECTED] ]

[|] Todays root password is brought to you by /dev/random

[+] 1024D/9AA80CDF = 4103 9E35 2713 D432 924F  3C2E A7B9 A0FE 9AA8 0CDF