I have 5-pair of polyclt/polysrv on Linux machines.
The alias and networks for clt and srv as follows:
route add -net 10.101.0.0/22 gw 172.16.1.61 #clt01
route add -net 10.101.4.0/22 gw 172.16.1.62 #clt02
route add -net 10.101.8.0/22 gw 172.16.1.63 #clt03
route add -net 10.101.12.0/22 gw 172.16.1.64 #clt04
route add -net 10.101.16.0/22 gw 172.16.1.65 #clt05
route add -net 10.101.128.0/22 gw 172.16.1.191 #srv01
route add -net 10.101.132.0/22 gw 172.16.1.192 #srv02
route add -net 10.101.136.0/22 gw 172.16.1.193 #srv03
route add -net 10.101.140.0/22 gw 172.16.1.194 #srv04
route add -net 10.101.144.0/22 gw 172.16.1.195 #srv05
My version of PolyMix-4 workload file:
#include "benches.pg"
Bench TheBench = benchPolyMix4;
TheBench = {
client_side = {
addr_space = [ 'lo::10.101.0-123.1-250/22' ];
hosts = [ '172.16.1.61-65' ];
};
server_side = {
addr_space = [ 'lo::10.101.128-251.1-250:80/22' ];
hosts = [ '172.16.1.191-195' ];
};
};
TheBench.peak_req_rate = 500/sec;
rate FillRate = 50% * TheBench.peak_req_rate;
size ProxyCacheSize = 4GB;
DnsResolver Resolver;
Resolver.servers = [ '172.16.1.100:53' ];
#include "polymix-4-guts.pg"
I noticed that lo ip addresses generated by polyclt/polysrv
would out of range from gateway point of view. In my case,
srv01: lo:0 10.101.128.1, .... lo:124 10.101.128.125
srv02: lo:0 10.101.128.126, .... lo:124 10.101.128.250
srv03: lo:0 10.101.129.1, .... lo:124 10.101.129.125
srv04: lo:0 10.101.129.126, .... lo:124 10.101.129.250
srv05: lo:0 10.101.130.1, .... lo:124 10.101.130.125
Have any ways to force srv02 stays on 10.101.132.0 network,
srv03 stays on 10.101.136.0 network, ...
E. Hu
This archive was generated by hypermail 2b29 : Mon Feb 06 2006 - 12:00:21 MST