Re: code+run (SG Cluster)

Subject: Re: code+run
Author: tung	June 5, 2001 at 01:46:03
in reply to: Re: code+run* posted by Ilker G on June 5, 2001 at 00:41:09*

> Hmm... Ok. I have changed..
>
> client1 (200.200.200.30) ---> sgcluster machine (group
> ip:200.200.200.137) --> backend web server (ip:192.168.1.1)
>
> When client1 wants a HTTP request to 200.200.200.137, i
> cant get any response from backend server.
>
> Some clues: 1 - sgcluster machine can ping to backend
> server. 2 - client1 can ping to sgcluster's public ip
> (200.200.200.214). 3 - client1 can NOT ping to sgcluster's
> group ip (137).
>
> My sg.conf:
>
> temporary_ip="10.0.0.1" # ip before start sg
> temporary_gw="10.0.0.253" # gateway before start sg
>
> public_interface="fxp0" private_interface="xl0"
>
> public_ip="200.200.200.214" default_gw="200.200.200.253"
> private_ip="192.168.1.253"
>
> group_ip="200.200.200.137"
>
> # map real servers to server group natd_parameter="
>
> -redirect_address 192.168.1.1 200.200.200.137
> -redirect_address 192.168.1.2 200.200.200.137
>
> " # init command sent to sgctrld init_command=" set g
> 200.200.200.137:0 s 192.168.1.1:0 weight 10 set g
> 200.200.200.137:0 s 192.168.1.2:0 weight 5
>
> "

Hi, Ilker!

The configuration looks good. I guess the problem is that
the backend servers didn't set the SG private
IP(192.168.1.253) as their default gateway. So when a
client access comes to SG and is delivered to one of the
backend servers, the server doesn't know where to response
it back.

Hope to see you good news...

tung

Follow Ups:

Re: code+run Ilker G 16:00:41 6/5/2001 (0)

Post Followup

Name:
E-Mail:
Subject:
> > Hmm... Ok. I have changed.. > > > > client1 (200.200.200.30) ---> sgcluster machine (group > > ip:200.200.200.137) --> backend web server (ip:192.168.1.1) > > > > When client1 wants a HTTP request to 200.200.200.137, i > > cant get any response from backend server. > > > > Some clues: 1 - sgcluster machine can ping to backend > > server. 2 - client1 can ping to sgcluster's public ip > > (200.200.200.214). 3 - client1 can NOT ping to sgcluster's > > group ip (137). > > > > My sg.conf: > > > > temporary_ip="10.0.0.1" # ip before start sg > > temporary_gw="10.0.0.253" # gateway before start sg > > > > public_interface="fxp0" private_interface="xl0" > > > > public_ip="200.200.200.214" default_gw="200.200.200.253" > > private_ip="192.168.1.253" > > > > group_ip="200.200.200.137" > > > > # map real servers to server group natd_parameter=" > > > > -redirect_address 192.168.1.1 200.200.200.137 > > -redirect_address 192.168.1.2 200.200.200.137 > > > > " # init command sent to sgctrld init_command=" set g > > 200.200.200.137:0 s 192.168.1.1:0 weight 10 set g > > 200.200.200.137:0 s 192.168.1.2:0 weight 5 > > > > " > > Hi, Ilker! > > The configuration looks good. I guess the problem is that > the backend servers didn't set the SG private > IP(192.168.1.253) as their default gateway. So when a > client access comes to SG and is delivered to one of the > backend servers, the server doesn't know where to response > it back. > > Hope to see you good news... > > tung
Optional link URL:
Link title:
Optional image URL: