[prev in list] [next in list] [prev in thread] [next in thread] 

List:       loadbalancing-l
Subject:    [load balancing] Re: Foundry DSR / web server config question.
From:       Steve Renner <srenner () idleshell ! net>
Date:       2002-05-31 1:54:52
[Download RAW message or body]

Well, I finally figured out the iplanet syntax -- was quite easy.  Just
add the following line for the 2nd ip to bind too in the obj.conf.

NameTrans fn="document-root" address="10.1.1.1" root="insert docroot here"

Where 10.1.1.1 would be the VIP for your loopback interface.  Then leave
the Address setting for the primary address in the magnus.conf and
everything works fine.

And well, what do you know, Tony's book specify's that you must set the
web server to bind on both those addesses.  I should refer to it more in
the future after all ;).


Steve

On Wed, 29 May 2002, Steve Renner wrote:

> I am pretty sure I know the answer to this question but wanted to bounce
> this off other brains to see if I am going down the right line or if
> anyone else has done this type of config.
>
> Have a foundry SI that is setup to do DSR in front of a web server (yes,
> there are multiples but thats not relevant to this question) that has
> multiple web services running for multiple vips:
>
> For example (using fake addresses):
>
> Foundry SI setup ...
>   REAL1 10.1.1.11
>     port http
>     port ssl
>   REAL2 10.1.1.12
>     port http
>     port ssl
>   REAL3 10.1.1.13
>     port http
>     port ssl
>
>   VIP1 192.168.1.11
>     port http
>     port http dsr
>     port ssl sticky
>     port ssl dsr
>     bind http real1 http
>     bind ssl real1 ssl
>   VIP2 192.168.1.12
>     port http
>     port http dsr
>     port ssl sticky
>     port ssl dsr
>     bind http real2 http
>     bind ssl real2 ssl
>   VIP3 192.168.1.13
>     port http
>     port http dsr
>     port ssl sticky
>     port ssl dsr
>     bind http real3 http
>     bind ssl real3 ssl
>
> OS Setup:
>
> lo0:1	192.168.1.11
> lo0:2	192.168.1.12
> lo0:3   192.168.1.13
>
> hme0	172.16.1.11	(Interface for backend to Apps/DB)
> qfe1	192.168.1.21	(Public IP to route back to client)
> qfe1:1	10.1.1.11	(Inside Virtual WEB Interfaces)
> qfe1:2	10.1.1.12
> qfe1:3	10.1.1.13
>
>
>
> IPLANET CONFIG:
>
> Each web service has its own instance and is bound to its own IP on port
> 80.
>
>
>
> Granted, its obvious that this wont work because the web service is not
> configured to bind on the loopback interfaces, but I cannot specific the
> web service to bind directly to the loopback interface because then the SI
> will never get the packets to it and I cannot find a way to make iPlanet
> bind to multiple IP's but not all.
>
> It appears that my only option is to make all the web services not specify
> an IP to bind to and just reside on a certain port, such as 81, 82, 83,
> etc.  But when I try to do this (by changing the real config and then the
> binds on the virtual) it doesn't seem to respond properly from the server.
>
> and of course, I have *inherited* this environment, so changing the
> overall setup of things is gonna be like pulling teeth, but I feel I have
> no options :).
>
>
> thanks,
>
> steve
>
>
>


____________________
The Load Balancing Mailing List
Unsubscribe:    mailto:majordomo@vegan.net?body=unsubscribe%20lb-l
Archive:        http://vegan.net/lb/archive
LBDigest:       http://lbdigest.com
MRTG with SLB:  http://vegan.net/MRTG
Hosted by:	http://www.tokkisystems.com

[prev in list] [next in list] [prev in thread] [next in thread]