|
"Young C. Cho" wrote:
>
> Dear All,
>
> I am testing DR on kernel 2.2.14.
>
> My setting is
>
> (Client) -----------------------------(Director )
> ---------------------------( Real server 1 )
> any DIP: 172.26.20.111 (eth0) RIP :
> 172.26.20.112 (eth0)
> VIP: 172.26.20.110 (eth0:1) VIP :
> 172.26.20.110 (lo:0)
>
> At the real server 1, I configured the server according to
> http://www.linuxvirtualserver.org/arp.html.
>
> echo 1 > /proc/sys/net/ipv4/ip_forward
> ifconfig lo:0 172.26.20.110 netmask 255.255.255.255 broadcast 172.26.20.110 up
> route add -host 172.26.20.110 dev lo:0
> echo 1 > /proc/sys/net/ipv4/conf/all/hidden
> echo 1 > /proc/sys/net/ipv4/conf/lo/hidden
>
> The real server 1 does not respond the arp request.
> (arp problem is solved by hiding VIP.)
>
> But, I wanted to changed 172.26.20.xxx to 192.168.1.xxx :
>
> (Client) -----------------------------(Director )
> ---------------------------( Real server 1 )
> any DIP: 192.168.1.111 (eth0) RIP :
> 192.168.1.112 (eth0)
> VIP: 192.168.1.110 (eth0:1) VIP :
> 192.168.1.110 (lo:0)
>
> Also, at the real server 1, I configured
>
> echo 1 > /proc/sys/net/ipv4/ip_forward
> ifconfig lo:0 192.168.1.110 netmask 255.255.255.255 broadcast 192.168.1.110
> up
> route add -host 192.168.1.110 dev lo:0
> echo 1 > /proc/sys/net/ipv4/conf/all/hidden
> echo 1 > /proc/sys/net/ipv4/conf/lo/hidden
>
> At this configuration, The real server 1 "does" respond
> the arp request. (arp problem is not solved by hiding VIP.)
This test is tricky. If your client made an arp request after the
ifconfig command and before the echo 1 command, then then client
will have an arp entry for the VIP and you will be able to ping
the VIP on real-server1 till the arp cache expires (30secs-2mins).
Is it possible that this is what's happening?
Also how do you know that the real-server 1 did not respond in the
first case? Did you see the MAC address for the director, but not the
real-server? (just checking)
Joe
>
> As summary, I only change the subnet from 172.26.20.xxx ---> 192.168.1.xxx.
> I doubt there are some reason in the fact that IP of loopback device (dev =
> lo)
> is 172.0.0.1.
>
> Don't you have any same situation?
>
> Any comment, Thanks.
>
> Young C. Cho
>
> ----------------------------------------
> Young Cheol Cho, Ph. D.
>
> jyc@xxxxxxxxxxxxxx
> http://cisl.snu.ac.kr/~jyc
>
> Automation Systems Reseach Institute,
> Seoul National Univ.,
> Seoul, 151-742, Korea.
> Tel : +82-2-874-8256
> Fax: +82-2-974-8256
> ---------------------------------------
--
Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
contractor to the National Environmental Supercomputer Center,
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA
|
