Excerpts from Rich Megginson's message of Mon Sep 27 10:31:53 -0400 2010:
> Ok. Please file a bug for this issue.
Will do.
> Are you using a load balancer or failover device?
We are using LVS to load balance HTTP requests, but LDAP is not loadbalanced.
However, we have an internal backend network which we use to service
LDAP replication. Some characteristic configuration:
eth1 Link encap:Ethernet HWaddr AC:DE:48:00:20:02
inet addr:172.21.0.228 Bcast:172.21.255.255 Mask:255.255.0.0
inet6 addr: fe80::aede:48ff:fe00:2002/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:82813649 errors:0 dropped:0 overruns:0 frame:0
TX packets:63692738 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:78380787428 (72.9 GiB) TX bytes:8426941129 (7.8 GiB)
Interrupt:15
and
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
18.181.0.57 172.21.0.57 255.255.255.255 UGH 0 0 0 eth1
18.181.0.56 172.21.0.56 255.255.255.255 UGH 0 0 0 eth1
18.181.0.237 172.21.0.237 255.255.255.255 UGH 0 0 0 eth1
18.181.0.235 172.21.0.235 255.255.255.255 UGH 0 0 0 eth1
18.181.0.234 172.21.0.234 255.255.255.255 UGH 0 0 0 eth1
18.181.0.47 172.21.0.47 255.255.255.255 UGH 0 0 0 eth1
18.181.0.167 172.21.0.167 255.255.255.255 UGH 0 0 0 eth1
18.181.0.228 172.21.0.228 255.255.255.255 UGH 0 0 0 eth1
18.181.0.53 172.21.0.53 255.255.255.255 UGH 0 0 0 eth1
18.181.0.52 172.21.0.52 255.255.255.255 UGH 0 0 0 eth1
18.181.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1003 0 0 eth1
172.21.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
0.0.0.0 18.181.0.1 0.0.0.0 UG 0 0 0 eth0
So requests that are transmitted to, say, 'better-mousetrap.mit.edu' are
routed over eth1 to gateway 172.21.0.57, which is better mousetrap.
Cheers,
Edward
