|
On Fri, Oct 03, 2003 at 02:45:55PM +0800, Oliver wrote:
> I think mon is only for monitoring lvs... keepalived is good... but i'm
> using ipvsadm right now.
To clarify, mon, keepalived, ldirectord, etc... are high level tools for
managing LVS. ipvsadm is a low level tool for directly manipulating LVS.
The problem you describe below has nothing to do with any of these
tools, it is a question of how LVS should be configured..
> but my problem if how can i configure both
> external and internal VIP into one port. let's say i'll use ftp;
> redirected to a backup server once ftp server is down. i did on my
> ipvsadm conf like
>
> ipvsadm -A -t external_vip:21 -s wrr
> ipvsadm -a -t external_vip:21 -r 192.168.1.11 -g -w 1
> ipvsadm -a -t external_vip:21 -r 192.168.1.12 -g -w 1
>
> In this scenario, my ftp users from outside network can connect into my
> backup-ftp (192.168.1.12)
> once my ftp server is down but users from inside my LAN cannot. what's the
> best way to configure
> ipvsadm so that users from my internal lan can also connect thru it? Let's
> say internal LAN's
> ip is 10.0.0.0/255.255.0.0... can i add something like
Why can't lan users connect to the external_vip? Off the top of my
head, if you are using LVS-DR, which you are this should work fine.
> ipvsadm -A -t internal_vip:21 -s wrr
> ipvsadm -a -t internal_vip:21 -r 192.168.1.11 -g -w 1
> ipvsadm -a -t internal_vip:21 -r 192.168.1.12 -g -w 1
>
> into my original ipvsadm config?
That should work too.
--
Horms
|
