LVS/DR - Revision history

Wensong at 15:36, 24 October 2007

2007-10-24T15:36:07Z

2007-05-28T15:40:48Z

‎Real Server

2006-10-27T06:08:43Z

‎Windows

2006-09-23T13:39:26Z

2006-08-02T13:22:12Z

2006-05-27T04:01:32Z

2006-01-23T13:56:14Z

2006-01-09T15:24:01Z

2005-07-15T16:34:01Z

2005-07-13T13:22:15Z

@@ Line 1: / Line 1: @@
-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.
+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 ([[real server]]s) are in a physical network.
 == Real Server ==
@@ Line 10: / Line 10: @@
 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 ==

← Older revision		Revision as of 15:40, 28 May 2007
Line 4:		Line 4:

	For ARP issue in the LVS/DR cluster, see the article [[ARP Issues in LVS/DR and LVS/TUN Clusters]].		For ARP issue in the LVS/DR cluster, see the article [[ARP Issues in LVS/DR and LVS/TUN Clusters]].
		+
		+	If real servers run UDP service, it is probably worth reading the article [[UDP service binding issue in LVS/DR and LVS/TUN]].

	=== Windows ===		=== Windows ===

@@ Line 7: / Line 7: @@
 === 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 ==

← Older revision		Revision as of 13:39, 23 September 2006
Line 1:		Line 1:
	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.		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.

	== See Also ==		== See Also ==

@@ Line 9: / Line 9: @@
 [[Category:IPVS]]
-[[Category:IP Load Balancing Technologies]]
+[[Category:IP Load Balancing Technologies|DR]]
 [[Category:Terms and Abbreviations]]

← Older revision		Revision as of 04:01, 27 May 2006
Line 10:		Line 10:
	[[Category:IPVS]]		[[Category:IPVS]]
	[[Category:IP Load Balancing Technologies]]		[[Category:IP Load Balancing Technologies]]
		+	[[Category:Terms and Abbreviations]]

← Older revision		Revision as of 15:24, 9 January 2006
Line 1:		Line 1:
	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.		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.
		+
		+	== See Also ==

	See more information about Linux Virtual Server via Direct Routing at http://www.linuxvirtualserver.org/VS-DRouting.html		See more information about Linux Virtual Server via Direct Routing at http://www.linuxvirtualserver.org/VS-DRouting.html

← Older revision		Revision as of 16:34, 15 July 2005
Line 3:		Line 3:
	See more information about Linux Virtual Server via Direct Routing at http://www.linuxvirtualserver.org/VS-DRouting.html		See more information about Linux Virtual Server via Direct Routing at http://www.linuxvirtualserver.org/VS-DRouting.html

		+	[[Category:IPVS]]
	[[Category:IP Load Balancing Technologies]]		[[Category:IP Load Balancing Technologies]]

← Older revision		Revision as of 13:22, 13 July 2005
Line 2:		Line 2:

	See more information about Linux Virtual Server via Direct Routing at http://www.linuxvirtualserver.org/VS-DRouting.html		See more information about Linux Virtual Server via Direct Routing at http://www.linuxvirtualserver.org/VS-DRouting.html
		+
		+	[[Category:IP Load Balancing Technologies]]