Difference between revisions of "LVS/TUN"

From LVSKB
Jump to: navigation, search
m (See Also)
m
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
It stands for Linux Virtual Server via IP Tunneling, an IP load balancing technology implemented in LVS.  
+
It stands for Linux Virtual Server via IP Tunneling, an IP [[load balancing]] technology implemented in LVS.  
  
 
IP tunneling (IP encapsulation) is a technique to encapsulate IP
 
IP tunneling (IP encapsulation) is a technique to encapsulate IP
 
datagram within IP datagram, which allows datagrams destined for one
 
datagram within IP datagram, which allows datagrams destined for one
 
IP address to be wrapped and redirected to another IP address. This
 
IP address to be wrapped and redirected to another IP address. This
technique can be used to build a virtual server that the load balancer
+
technique can be used to build a virtual server that the [[load balancer]]
 
tunnels the request packets to the different servers, and the servers
 
tunnels the request packets to the different servers, and the servers
 
process the requests and return the results to the clients directly,
 
process the requests and return the results to the clients directly,
 
thus the service can still appear as a virtual service on a single IP
 
thus the service can still appear as a virtual service on a single IP
 
address.
 
address.
 +
 +
== Real Server ==
 +
 +
For ARP issue in the LVS/TUN 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]].
  
 
== Examples ==
 
== Examples ==

Latest revision as of 15:05, 22 October 2007

It stands for Linux Virtual Server via IP Tunneling, an IP load balancing technology implemented in LVS.

IP tunneling (IP encapsulation) is a technique to encapsulate IP datagram within IP datagram, which allows datagrams destined for one IP address to be wrapped and redirected to another IP address. This technique can be used to build a virtual server that the load balancer tunnels the request packets to the different servers, and the servers process the requests and return the results to the clients directly, thus the service can still appear as a virtual service on a single IP address.

Real Server

For ARP issue in the LVS/TUN 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.

Examples

See Also


LVS.png "LVS/TUN" is an IPVS related stub. You can help LVSKB by expanding it