Difference between revisions of "ARP Issues in LVS/DR and LVS/TUN Clusters"
From LVSKB
m |
|||
| Line 1: | Line 1: | ||
== Problems == | == Problems == | ||
| + | |||
| + | In the [[LVS/DR]] and [[LVS/TUN]] clusters, we can see that the [[VIP]] address is shared by [[load balancer]] and all [[real server]]s. In order to make the [[LVS/DR]] and [[LVS/TUN]] clusters work, [[load balancer]] should broadcast the [[VIP]] address to accept incoming packets for virtual service, the [[real server]]s only use the [[VIP]] address to process the packets for [[VIP]] locally. | ||
== Solutions == | == Solutions == | ||
Revision as of 14:56, 2 September 2006
Problems
In the LVS/DR and LVS/TUN clusters, we can see that the VIP address is shared by load balancer and all real servers. In order to make the LVS/DR and LVS/TUN clusters work, load balancer should broadcast the VIP address to accept incoming packets for virtual service, the real servers only use the VIP address to process the packets for VIP locally.
Solutions
- arptables
- The arp_announce/arp_ignore approach
- The hidden patch
- The redirect approach
- The policy routing approach
- The noarp module
