|
>
> > ok, I set up the hidden dummy0 thing on the RS's with the VIP netmask
> > 255.255.255.255.
> > I can ping everyone but the director now in that net anyway....the
> > directory cannot ping the outside world interfaces of the real servers
> > because they route the reply to their own dummy device :P
>
> There is something wrong in your setup, you can't define
> hidden and non-hidden addresses on the dummy interface.
huh? I must not have been clear because that makes no sence to me.
dummy0 is set as noarp VIP on real servers.
director has two routes to real servers, the world net which it has the VIP
as its IP, and the LAN which it uses private IPs to talk with the real
servers.
The real servers can talk to each other and the router on the world net and
everyone talks on the LAN.
The real server can ping the VIP but have no arp entry for it. The
directory cannot ping either RS and has an (incomplete) arp entry for them
after.
Pings go in and out of all machines on all interfaces with that one
exception....obviously the RS's are pinging their own VIP on the dummy and
responding to that iface when the director attempts to ping.
route does not show the dummy iface.
BTW this is direct routing.....
> You have to
> show all your addresses and routes on the director and on the tested
> real servers.
ok....how about just one RS for now...the problem is on both so should be
findable with less text to the list....
Dir---------
eth0 Link encap:Ethernet HWaddr 00:D0:70:01:40:2C
inet addr:192.168.5.1 Bcast:192.168.5.255 Mask:255.255.255.0
eth1 Link encap:Ethernet HWaddr 00:D0:70:01:40:F9
inet addr:63.225.190.129 Bcast:63.255.255.255
Mask:255.255.255.248
Destination Gateway Genmask Flags Metric Ref Use
Iface
63.225.190.128 0.0.0.0 255.255.255.248 U 0 0 0
eth1
192.168.5.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 63.225.190.134 0.0.0.0 UG 0 0 0
eth1
Address HWtype HWaddress Flags Mask
Iface
joe.cluster ether 00:A0:C9:89:24:D3 C
eth0
bob.cluster ether 00:C0:4F:AC:44:07 C
eth0
route.masks.org ether 00:E0:D0:13:CB:2F C
eth1
63.225.190.130 ether 08:00:07:7F:56:A2 C
eth1 <- me masq
-----------
RS1-------
dummy0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:63.225.190.129 Bcast:63.255.255.255
Mask:255.255.255.255
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
eth0 Link encap:Ethernet HWaddr 00:A0:C9:89:24:D3
inet addr:192.168.5.2 Bcast:192.168.5.255 Mask:255.255.255.0
eth1 Link encap:Ethernet HWaddr 00:D0:B7:1A:BD:AC
inet addr:63.225.190.131 Bcast:63.255.255.255
Mask:255.255.255.248
Destination Gateway Genmask Flags Metric Ref Use
Iface
63.225.190.128 0.0.0.0 255.255.255.248 U 0 0 0
eth1
192.168.5.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0
eth2
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 63.225.190.134 0.0.0.0 UG 0 0 0
eth1
Address HWtype HWaddress Flags Mask
Iface
blow.cluster ether 00:A0:C9:36:96:00 C
eth2 <- private ifaces
brain.cluster ether 00:D0:70:01:40:2C C
eth0
unused.cluster ether 00:E0:D0:13:CB:2F C
eth1 <- router (hosts entry is bent)
machttp.masks.org ether 08:00:07:7F:56:A2 C
eth1 <- mail server used to be something else
from director....
ping -v 63.225.190.131
PING 63.225.190.131 (63.225.190.131): 56 data bytes
--- 63.225.190.131 ping statistics ---
10 packets transmitted, 0 packets received, 100% packet loss
new arp entry....
63.225.190.131 (incomplete)
eth1
from rs1....
ping -v 63.225.190.129
PING 63.225.190.129 (63.225.190.129): 56 data bytes
64 bytes from 63.225.190.129: Echo Request
64 bytes from 63.225.190.129: icmp_seq=0 ttl=255 time=1190.8 ms
64 bytes from 63.225.190.129: Echo Request
64 bytes from 63.225.190.129: icmp_seq=1 ttl=255 time=217.6 ms
64 bytes from 63.225.190.129: Echo Request
64 bytes from 63.225.190.129: icmp_seq=2 ttl=255 time=43.8 ms
--- 63.225.190.129 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 43.8/484.0/1190.8 ms
no new arp entries....nothing for 63.225.190.129.
> > how do I fix that? I was using fping to verify that the outside
> > interface was indeed up from the directory and killing that rs in the
> > admin if it wasn't....now I can't check it seems.
>
> The ping connectivity can fail for many possible reasons.
> Check the rp_filter device flags too.
0 on all devices and all servers.
|
