LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: testlvs question

To: William Clements <whc2u@xxxxxxxxxxxxx>
Subject: Re: testlvs question
Cc: <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
From: Julian Anastasov <ja@xxxxxx>
Date: Tue, 6 Mar 2001 00:59:48 +0000 (GMT)
        Hello,

On Mon, 5 Mar 2001, William Clements wrote:

> >       Is there an ipchains -I input -s 10.0.0.0/24 -j DENY rule in
> > the real servers? I assume you try to test the throughput in the
> > director and not to flood your web services. The traffic can be
> > redirected to another place if you don't follow the instructions
> > to block it in the real servers. You have to describe your setup.
> >
>
> I'm not using ipchains anywhere.  I used "route" on the
> real webservers to drop the bogus route.

        OK

> > > Using show_traffic.sh I get the following:
> > >
> > > director:     ~ 1002 packets/sec
> > > webserver1:   ~ 50 packets/sec
> > > webserver2:   ~ 50 packets/sec
> > >
> > > (as per the show_traffic.sh default, all measurements are over
> > > a 10 second period of time)
> > > So, I'm wondering what happened to the "other" packets.
> > > Any thoughts?
> >
> >       It seems the packets are not scheduled. What shows telnet from
> > the client host to 192.168.1.250 ? ipvsadm -Ln ?
> >
>
> Output from ipvsadm -L -n:
>
> IP Virtual Server version 1.0.5 (size=4096)
> Prot LocalAddress:Port Scheduler Flags
>   -> RemoteAddress:Port          Forward Weight ActiveConn InActConn
> TCP  192.168.1.250:80 lc
>   -> 192.168.1.221:80            Route   1      0          0
>   -> 192.168.1.220:80            Route   1      0          0

        Hm, may be the packets are dropped in the director. May be
you have rp_filter=1 and no route to 10/8. What about adding in the
director:

ip route add default via some_gateway dev eth0
or just
ip route add 10/8 via the_same_gateway dev eth0

        The gateway can simply be the client host where you run
testlvs, i.e. the device where the requests come from if we don't want
to cause more troubles when using rp_filter.

        If you don't have route to the used spoofed source addresses,
which are from 10.0.0.0/8 by default, the rp_filter in the director
just drops them. This is the only difference I can see when using
testlvs and other L7 clients (ab, ptester, etc) which use normal
source addresses.

> Conectivity is not the issue.  I've also used "ab" and "ptester"
> simulate real traffic.  (Unfortunately the 10mb pathway I'm using quicky
> gets saturated if the return traffic is to large).
>
> Typical "ab" traffic:
>
> ab -n 10000 -c 100 http://192.168.1.250/test.html
>
> director:     ~ 6562 packets/sec
> webserver1:   ~ 3297 packets/sec
> webserver2:   ~ 3254 packets/sec
...

> Much Thanks
>
> Will


Regards

--
Julian Anastasov <ja@xxxxxx>



<Prev in Thread] Current Thread [Next in Thread>