Re: Clustering and browsing

My impression is that the SLB is different than simple IP spraying.  It 
needs the additional IP address on the target server so that it can use it 
to talk to and see if a port is active.

For example, if I use your setup of:
SLB: 10.10.1.185
DWA Server #1: 10.10.1.186
DWA Server #2: 10.10.1.187
(which is what we did for simple round robin DNS)
but expand it to what we want. Our users would go to 185.  From 185 the 
SLB would check to see that port 80 was currently being served from 186 
before routing http traffic to 186.

Here's another example.  I have a domino server called GDI01.  It has
TCPIP_TcpIpAddress=0,10.10.1.145:1352
Now I'll actually do an ENDDOMSVR on it...
Now it's dead and there are no jobs in it.
>From my PC I can do a 

C:\Documents and Settings\rob>ping 10.10.1.145
Pinging 10.10.1.145 with 32 bytes of data:
Reply from 10.10.1.145: bytes=32 time=5ms TTL=63
Reply from 10.10.1.145: bytes=32 time<1ms TTL=63
Reply from 10.10.1.145: bytes=32 time<1ms TTL=63
Reply from 10.10.1.145: bytes=32 time<1ms TTL=63
Ping statistics for 10.10.1.145:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 5ms, Average = 1ms

Basically, the iSeries is handling the pings, not the domino server.

So a simple round robin dns, or ip sprayer, would say it's ok to route 
domino traffic to that even though it is dead as nails.

So, somehow, the SLB is using this other IP address to find out if the 
port 80 is actually hosted on 145 before it routes traffic to it.

Rob Berendt