|
Try using the proper net mask, ms networking gets confused otherwise...
also untick the options for Microsoft Networking & File & Print sharing.
And on the advanced tab set the priority to 254
You shouldn't need to delete the routes
AJ Lemke wrote:
Hello all,
I have a question concerning real servers.
We have a 2 director LVS that load balances for 2 squid boxes in
acceleration mode and a Windows 2000 box. We can send requests all day
long to the squid boxes and the respond flawlessly but we seem to be
unable to get the Windows box to respond to our requests.
I have added a Microsoft loopback adapter to the box and given that
adapter the corresponding VIP, which happens to be xx.xx.191.5, the x's
are there to protect the innocent. I have given it a Netmask of
255.0.0.0, which is in the how-to. This box does nothing but server
https: for a client's website.
In another part of the how-to it says to do a route delete <VIP's
Network> <VIP Mask>. We have tried to do this numerous times but
everytime it tells us "The specified route cannot be found".
Do any of you know of a good way to see if the packets are getting
through?
Or if by looking at the information I have provided see anything that
could or should be done different let me know.
Thanks for your help
AJ
PS: Here is some information.
Windows box:
Ethernet: xx.xx.191.60
Subnet: 255.255.255.0
Gateway xx.xx.191.1
Loopback: xx.xx.191.1
Subnet: 255.0.0.0
Gateway:
Routes:
C:\route print
========================================================================
===
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000004 ...00 40 05 31 11 XX ...... Intel DC21140 PCI Fast Ethernet
Adapter
0x2000002 ...02 00 4c 4f 4f XX ...... MS LoopBack Driver
========================================================================
===
========================================================================
===
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 xx.xx.191.1 xx.xx.191.60
1
xx.0.0.0 255.0.0.0 xx.xx.191.5 xx.xx.191.5
1
xx.xx.191.0 255.255.255.0 xx.xx.191.60 xx.xx.191.60
1
xx.xx.191.5 255.255.255.255 127.0.0.1 127.0.0.1
1
xx.xx.191.60 255.255.255.255 127.0.0.1 127.0.0.1
1
xx.255.255.255 255.255.255.255 xx.xx.191.5 xx.xx.191.5
1
xx.255.255.255 255.255.255.255 xx.xx.191.60 xx.xx.191.60
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
224.0.0.0 224.0.0.0 xx.xx.191.5 xx.xx.191.5
1
224.0.0.0 224.0.0.0 xx.xx.191.60 xx.xx.191.60
1
255.255.255.255 255.255.255.255 xx.xx.191.60 xx.xx.191.60
1
Default Gateway: xxx.xxx.191.1
========================================================================
===
Persistent Routes:
None
LVS:
Director 1:
Eth0: xx.xx.191.2
Subnet: 255.255.255.0
Gateway xx.xx.191.1
Director 2:
Eth0: xx.xx.191.3
Subnet: 255.255.255.0
Gateway xx.xx.191.1
Virtual IP's
Eth0:1: xx.xx.191.4 Cached Squid site
Eth0:2: xx.xx.191.5 Load balances HTTPS:
Eth0:3: xx.xx.191.6 Cached Squid site
Ldirectord Config sample
# HTTPS Virtual Service
virtual=xx.xx.191.5:443
fallback=127.0.0.1:443
real=xx.xx.191.60:443 gate
service=https
checktype=connect
request="index.asp"
receive="HTTPS Test"
scheduler=wlc
persistent=600
protocol=tcp
quiescent = no
IPVSADM -L output
IP Virtual Server version 1.0.4 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP xx.xx.191.6:http lblc persistent 10
-> xx.xx.191.200:http Route 1 0 0
TCP xx.xx.191.4 lblc persistent 360
-> x.xx.191.200:http Route 1 0 0
TCP xx.xx.191.5:http lblc persistent 360
-> xx.xx.191.200:http Route 1 0 0
TCP xx.xx.191.5:https wlc persistent 600
-> xx.xx.191.60:https Route 1 0 0
Again thank you for your help.
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://www.in-addr.de/mailman/listinfo/lvs-users
--
Regards,
Malcolm Turnbull.
Crocus.co.uk Ltd
01344 629629
http://www.crocus.co.uk/
| 