|
redirecting decoy wrote:
>
> Joe,
>
> > Is their a connection at the realserver (with
> > netstat -a)? - if so
> > the packet has got to the realserver.
>
> No, the connection never makes it to the real server.
> I have no idea why. I set everything up according to
> documentation.
I would imagine that the hardware's opinion on the matter
counts for something here :-)
> > Does the director show a connection from the client
> > (probably InActConn)? if so the packet has got to the ip_vs
> > code.
> Yes, it does now anyway. I made a small change to the
> host which the uml is running on. Simply had to
> change the default gw to correct device (i.e
> uml-bridge).
>
> > Is the routing from the realserver(s) to the client
> > directly to the client and not via the director?
> I am not sure. What would the best way to check be ?
`route`
or
`ip route show`
all packets from the realserver:VIP:port_being_lvs'ed should
not pass through the director on their way to the client
usually this is handled by the default gw
> It appears that I am unable to connect to the Real
> servers. It might be a routing problem, although all
> the realservers can ping the DIP, and vice versa.
lvs doesn't act at the same layer as ping, so ping can work,
but lvs is messing with the layer above and may not be setup
correctly.
The usual problem causing InActConn entries is incorrect routing
on the realserver.
> here is the routing tables for my Director (uml),
> RealServers, Uml-Host
these don't help me. I have no idea where these IPs are.
Joe
--
Joseph Mack PhD, High Performance Computing & Scientific Visualization
LMIT, Supporting the EPA Research Triangle Park, NC 919-541-0007
Federal Contact - John B. Smith 919-541-1087 - smith.johnb@xxxxxxx
|
