|
Leo wrote:
> BTW:I had try to ping VIP(192.168.0.11) from client,But I got response, it's
> not normal?
it is normal
> C:\Documents and Settings\Administrator>ping 192.168.0.11
you are pinging the VIP from a machine with the VIP, you should
get a reply. This doesn't tell you whether the VIP responds to
ARP requests.
> Pinging 192.168.0.11 with 32 bytes of data:
> (RIP:192.168.0.103 VIP:192.168.0.11) You can see VIP:192.168.0.11 's
> netmask is 255.255.255.255
>
> ***************************************************************************
> C:\Documents and Settings\Administrator>route print
> ===========================================================================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x9000002 ...02 00 4c 4f 4f 50 ...... MS LoopBack Driver
> 0xa000004 ...00 b0 d0 5f 5b c2 ...... 3Com EtherLink PCI
> ===========================================================================
> ===========================================================================
> Active Routes:
> Network Destination Netmask Gateway Interface Metric
> 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.103 1
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> 192.168.0.0 255.255.255.0 192.168.0.103 192.168.0.103 1
> 192.168.0.11 255.255.255.255 127.0.0.1 127.0.0.1 1
> 192.168.0.103 255.255.255.255 127.0.0.1 127.0.0.1 1
> 192.168.0.255 255.255.255.255 192.168.0.11 192.168.0.11 1
> 192.168.0.255 255.255.255.255 192.168.0.103 192.168.0.103 1
> 224.0.0.0 224.0.0.0 192.168.0.11 192.168.0.11 1
> 224.0.0.0 224.0.0.0 192.168.0.103 192.168.0.103 1
> 255.255.255.255 255.255.255.255 192.168.0.11 192.168.0.11 1
> Default Gateway: 192.168.0.1
I assume the default gw is not on the director?
> 18 packets captured
> 18 packets received by filter
> 0 packets dropped by kernel
you were trying to connect from the client at this time?
> C:\Leo>
>
> =================================================================
> Dump from director(RIP:192.168.0.102)
>
> [root@localhost root]# tcpdump -n -i eth0 -i eth0:0 "host not 192.168.0.1 and
> host not 192.168.0.111"
> tcpdump: listening on eth0:0
is this the NIC with the VIP?
> 05:23:38.223182 arp who-has 192.168.0.108 tell 192.168.0.102
> 05:23:39.222925 arp who-has 192.168.0.108 tell 192.168.0.102
> 05:23:40.222983 arp who-has 192.168.0.108 tell 192.168.0.102
> 05:23:47.551300 192.168.0.104.3558 > 192.168.0.102.http: S
> 2122540016:2122540016(0) win 65535 <mss 1460,nop,nop,sackOK> (DF)
is this your client trying to connect to x.x.x.102?
If so why isn't it trying to connect to the VIP?
Again, rather than having us go through all of this again,
can you work through the examples in the mini-HOWTO first?
Thanks Joe
--
Joseph Mack PhD, High Performance Computing & Scientific Visualization
LMIT, Supporting the EPA Research Triangle Park, NC 919-541-0007
Federal Contact - John B. Smith 919-541-1087 - smith.johnb@xxxxxxx
|
