I am not quite sure which release you are using but this should work.
A very simple config like the following:
server real rs101 192.168.1.101
port http
port http url "GET /index.html HTTP/1.1\r\nHost: www.whatever.com\r\n\r\n"
port 8080
!
!
server virtual vs200 20.20.1.200
predictor round
port http
bind http rs101 http rs101 8080
-> one real server with two daemons and one
virtual server using the predictor roundrobin is
going to result in a load balancing:
Real Servers Info
========================
State - ACT:active, ENB:enabled, FAL:failed, TST:test, SUS:suspect,
GDN:grace-dn, DIS:disabled, UNK:unknown, UNB:unbind,
AWU:await-unbind, AWD: await-shutdown
Name: rs101 State: Active IP:192.168.1.101: 1
Mac: 0010.a4c1.995a Weight: 0 MaxConn: 2000000
SrcNAT: not-cfg, not-op DstNAT: not-cfg, not-op Serv-Rsts: 0
Port St Ms CurConn
TotConn Rx-pkts Tx-pkts Rx-octet Tx-octet Reas
---- -- -- -------
------- ------- ------- -------- -------- ----
default UNB 0 0 0 0 0 0 0 0
http ACT 0 22 35 71 175 17893 13510 0
8080 ACT 0 22 34 68 170 17476 13124 0
Server Total 44 69 139 345 35369 26634 0
^
-> 22 sessions to port 80 and 22 to port 8080...
This is with release 10.2.01c.
R, Oliver
At 19:10 30.10.2008, Derek Maurer wrote:
That was my assumption; I suppose I should put
my feature request into Foundry ;-)
This limitation makes it awkward to manage load
balancing applications in a large hosting
environment. Having multiple unique IPs on each
server just adds to the complexity of a solution
when unique ports should be all that's required.
When we used to have Cisco CSS switches I was
able to load balance effectively across ports on
1 IP (and reuse real server ports in multiple
VIPs). I like these Foundry SI's for the
granularity of configuration, but other times I
wish some of the Cisco features were available.
I haven't checked the latest firmware features
in a while, any chance some of this was changed is the most current versions?
DRM
-----Original Message-----
From: Joffrey Agoutin [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 30, 2008 1:37 PM
To: Derek Maurer; [email protected]
Subject: RE: [f-nsp] Load balancing across sties on one real server
As far as I know, you can't load balance across
multiple sites running on the same real server.
You need to setup multiple IP addresses on the
real server (one for each site) to allow this.
Then, in your configuration, you'll have to
specify 1 real server per site (using its own IP address).
I'm not sure, but I didn't see an option in the
documentation to do this with only one IP.
Joffrey AGOUTIN
Administrateur Systèmes & Réseaux | NB
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Derek Maurer
Sent: jeudi 30 octobre 2008 05:44
To: [email protected]
Subject: [f-nsp] Load balancing across sties on one real server
I've noticed if I have multiple site running on
the same real server I can't balance the load
across them, , regardless of the predictor. The
first real server port bound in the virtual server always seems to gets
the connections.
Reading the documentation closely, I noticed the
predictor balances load across 'real
servers'. Do I really need to configure unique
IPs for each site on the same physical server (and matching 'real servers') in
order to load balance effectly across sites on one server?
DRM
_______________________________________________
foundry-nsp mailing list
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp
_______________________________________________
foundry-nsp mailing list
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp
_______________________________________________
foundry-nsp mailing list
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp
