|
Joseph Mack PhD, High Performance Computing & Scientific Visualisation
LMIT, Supporting the EPA Research Triangle Park, NC 919-541-0007
Federal Contact - John B. Smith 919-541-1087 - smith.john@xxxxxxx
lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx wrote on 03/10/2005 12:47:13
PM:
> The only thing that doesn't work now is the "local node"
> feature (is this
> relevant for LVS-NAT?).
localnode is independant of the scheduler(s) ie it works with
LVS-NAT, -DR, -Tun
> I've tried both:
>
> ipvsadm -a -t 172.x.x.x:25 -r 127.0.0.1:25 -m -w 1
> and
> ipvsadm -a -t 172.x.x.x:25 -r 10.1.1.1:25 -m -w 1
>
> I also tried using this in LVS-DR and LVS-TUN
> configuration, but I could not get
> it to talk to the local node (the real server was fine).
> In all cases, the
> client responds with:
>
> Trying 172.x.x.x...
you are trying
# telnet $VIP 25
^^
aren't you?
> telnet: connect to address 172.x.x.x: Connection refused
> telnet: Unable to connect to remote host: Connection refused
this means that no demon is listening on port 25 on
the $VIP:25 (or that packets can't get through to the
VIP:port).
Joe
|
