|
2008/5/30 Graeme Fowler <graeme@xxxxxxxxxxx>:
> Hi Paul
>
> On Fri, 2008-05-30 at 10:32 +0100, Paul Bowden wrote:
>> I also ran tcpdump -vv port 3306 on lb1 (which had the virtual ip) and
>> this is what I get when I telnet 192.168.1.243 3306
>
> Can you run that again, but this time on both of the realservers, per:
>
> tcpdump -qn host client-1
>
> This will give you both sides of the conversation as seen by the
> realserver - both the client connecting to the VIP, and the responses to
> the client (which the director doesn't necessarily see when using -DR).
>
> Graeme
Hi Graeme,
I'm not sure if you wanted me to run tcpdump -qn host client-1 on the
load balancers as well, but I ran it on lb1, lb2, sql1 and sql2 and
here are the results:
lb1 (which currently has the vip) is the only machine that mentions
anything to do with my attempted telnet:
lb1:
11:34:17.134990 IP 192.168.1.244.22 > 192.168.1.177.1268: tcp 116
11:34:17.135062 IP 192.168.1.244.22 > 192.168.1.177.1268: tcp 116
11:34:17.135611 IP 192.168.1.177.1268 > 192.168.1.244.22: tcp 0
11:34:19.538120 arp who-has 192.168.1.245 tell 192.168.1.177
11:34:35.708037 arp who-has 192.168.1.247 tell 192.168.1.177
11:34:51.845153 arp who-has 192.168.1.18 tell 192.168.1.177
11:34:59.362084 IP 192.168.1.177.3312 > 192.168.1.243.3306: tcp 0
11:34:59.362104 IP 192.168.1.243 > 192.168.1.177: ICMP 192.168.1.243
tcp port 3306 unreachable, length 56
11:35:02.352094 IP 192.168.1.177.3312 > 192.168.1.243.3306: tcp 0
11:35:02.352108 IP 192.168.1.243 > 192.168.1.177: ICMP 192.168.1.243
tcp port 3306 unreachable, length 56
11:35:04.353748 arp who-has 192.168.1.177 tell 192.168.1.244
11:35:04.353856 arp reply 192.168.1.177 is-at 00:30:1b:44:f4:af
11:35:08.387664 IP 192.168.1.177.3312 > 192.168.1.243.3306: tcp 0
11:35:08.387681 IP 192.168.1.243 > 192.168.1.177: ICMP 192.168.1.243
tcp port 3306 unreachable, length 56
11:35:29.700473 IP 192.168.1.177.1268 > 192.168.1.244.22: tcp 52
lb2:
11:34:11.773306 IP 192.168.1.245.22 > 192.168.1.177.1333: tcp 116
11:34:11.787721 IP 192.168.1.245.22 > 192.168.1.177.1333: tcp 116
11:34:11.773913 IP 192.168.1.177.1333 > 192.168.1.245.22: tcp 0
11:34:19.488973 arp who-has 192.168.1.247 tell 192.168.1.177
11:34:35.626040 arp who-has 192.168.1.18 tell 192.168.1.177
11:35:14.781049 IP 192.168.1.177.1333 > 192.168.1.245.22: tcp 52
sql1:
11:33:44.510460 IP 192.168.1.246.22 > 192.168.1.177.1369: tcp 116
11:33:44.510513 IP 192.168.1.246.22 > 192.168.1.177.1369: tcp 116
11:33:44.511097 IP 192.168.1.177.1369 > 192.168.1.246.22: tcp 0
11:33:46.646398 arp who-has 192.168.1.247 tell 192.168.1.177
11:34:02.783263 arp who-has 192.168.1.18 tell 192.168.1.177
11:34:42.863889 arp who-has 192.168.1.188 tell 192.168.1.177
11:34:43.427345 IP 192.168.1.177.1369 > 192.168.1.246.22: tcp 52
sql2:
11:30:05.055843 IP 192.168.1.247.22 > 192.168.1.177.1461: tcp 116
11:30:05.055918 IP 192.168.1.247.22 > 192.168.1.177.1461: tcp 116
11:30:05.056459 IP 192.168.1.177.1461 > 192.168.1.247.22: tcp 0
11:30:18.559928 arp who-has 192.168.1.18 tell 192.168.1.177
11:30:58.640735 arp who-has 192.168.1.188 tell 192.168.1.177
11:30:59.709793 IP 192.168.1.177.1461 > 192.168.1.247.22: tcp 52
Regards,
Paul
|
