Difference between revisions of "LVS/DR"
m (→Windows) |
|||
| Line 7: | Line 7: | ||
=== Windows === | === Windows === | ||
| − | On Windows 2003 Server, the built-in firewall on interface should '''not''' be turned on, otherwise LVS/DR may not work, because the built-in firewall is too simple to configure, it will drop the packet for VIP automatically. | + | On Windows 2003 Server, the built-in firewall on interface should '''not''' be turned on, otherwise [[LVS/DR]] may not work, because the built-in firewall is too simple to configure, it will drop the packet for VIP automatically, then the whole [[LVS/DR]] cluster would not work. |
== See Also == | == See Also == | ||
Revision as of 06:08, 27 October 2006
It stands for Linux Virtual Server via Direct Routing, an IP load balancing technology implemented in LVS. It directly routes packets to backend server through rewriting MAC address of data frame with the MAC address of the selected backend server. It has the best scalability among all other methods because the overhead of rewriting MAC address is pretty low, but it requires that the load balancer and the backend servers are in a physical network.
Real Server
For ARP issue in the LVS/DR cluster, see the article ARP Issues in LVS/DR and LVS/TUN Clusters.
Windows
On Windows 2003 Server, the built-in firewall on interface should not be turned on, otherwise LVS/DR may not work, because the built-in firewall is too simple to configure, it will drop the packet for VIP automatically, then the whole LVS/DR cluster would not work.
See Also
See more information about Linux Virtual Server via Direct Routing at http://www.linuxvirtualserver.org/VS-DRouting.html
|
"LVS/DR" is an IPVS related stub. You can help LVSKB by expanding it |
