|
NT can be a pain in the backside when its routing table gets confused :-)
In my experience setting the metric to 254 solves 95% of issues.
Using the registry to set the mask to 255.255.255.255 does the other 5%
Seems to happen more often in NT style domains or servers with multiple
NICs.
Any NT realserver with a problem is easy to spot as it won't work in DR
full stop, and the routing table will be incorrect.
Regards,
Malcolm Turnbull.
Loadbalancer.org Limited
+44 (0)7715 770523
http://www.loadbalancer.org/
" When a single point of failure is not an option"
Why not try our online demonstration
<http://www.loadbalancer.org/demo.html> ? Or get answers to common
questions <http://www.loadbalancer.org/fud.html> ?
lstep@xxxxxxxxxxxx wrote:
Hello,
I'm trying to understand why do one set the metric of the localhost interface
to 254 (according to the doc found on
http://wiki.linuxquestions.org/wiki/LVS_with_HA_for_Win2k_Terminal_Servers)
when configuring a W2K realserver's loopback in a Direct Routing mode?
If I don't do this what problem(s) may I get?
Thanks,
Luc
_______________________________________________
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
| 