|
On Thu, Apr 18, 2002 at 08:22:41AM -0400, Joseph Mack mentioned:
> > Install a pre-configured director into the rack, connect the switch to
> > the director, take the uplink connection out of the switch, into the
> > director,
> hmm, I'm not sure what happened here (sleight of hand?).
> I've forgotten what little I knew about transparent bridging.
> How is transparent bridging involved here? What problem did it solve?
The director is configured to listen for the IPs of the real servers at
the internal side of the network bridge, and pass them on, with some
intelligence.
RS1 RS2 RS3
| | |
\--------------/
|
DR/Bridge
|
router
|
Clients
RS1=original webserver (ip 293.2.2.1/26)
RS2=new webserver (ip 293.2.2.2/26)
RS3=new webserver (ip 293.2.2.3/26)
DR =Director (ip 293.2.2.4/26)
router (ip 293.2.2.63/26 and 293.2.3.63/26)
Note the router is not on the same physical network as the realservers,
but is on the same logical network.
So, when a connection comes in for 293.2.2.1, the router sends out an ARP
request. The DR answers with it's own MAC, and transparently forwards all
connections on to RS1/RS2/RS3 depending on it's load balancing algorithm.
The real servers still have their gateway set to be the router. Very cool
idea. No idea how to do it.
Kate
--
_______________________________________
John Looney Chief Scientist
a n t e f a c t o t: +353 1 8586004
www.antefacto.com f: +353 1 8586014
|
