Local Director 417 in cluster situation

[htidore]

Hi,

I have a LD 417 to forward packets to 2 servers (A&B running redhat cluster suite). The IP address of server A and B are 10.10.10.1 and 10.10.10.2 respectively. The virtual ip for server A and B is 10.10.10.3.

Since the 2 servers are clusters, only 1 server will be running a service at a time. The service runs at port 5000.

My questions:

1. LD 417 will need to route packets to the server which is running the service. How does LD 417 determines that the service is running at server A instead of B ? Is there any command such as keepalive ? what mechanism does LD 417 use ?

2. If I set the bind as follow:

bind 10.10.10.3:5000:0:tcp 10.10.10.3:5000:0:tcp

How can I divert all other packets going to vip 10.10.10.3 to another server (10.10.10.11) ?

Thanks for the help ?

[Gilles Dufour]

the LD uses inband health monitoring.

It forwards client traffic to server and if the LD does not see a response from the server, it consider it as dead [there are thresholds associated with this].

localdirector(config)# threshold ?

usage: threshold

There is also probes that can be generated but it is limited to dns and http.

localdirector(config)# pro?

probe

probeconfig

probedns

probehttp

If you want to redirect other traffic to another address, you first need to create a vserver to catch this traffic, a real server to receive the traffic an d then bind the 2 togethers.

Gilles.

[htidore]

Please confirm if the following bind is correct. The purpose is port 80 goes to 10.10.10.1 and all other ports goes to 10.10.10.2:

bind 10.10.10.3:80:0:tcp 10.10.10.1:0:0:tcp

bind 10.10.10.3:0:0:tcp 10.10.10.2:0:0:tcp

Will the LD ALWAYS route port 80 packets to 10.10.10.1 ?

[Gilles Dufour]

yes, that's correct.

Should work like this.

Gilles