Comments on: One Arm, One Network, To Rule Them All http://lbdigest.com/2009/10/25/one-arm-one-network-to-rule-them-all/ Server Load Balancing Articles and News Fri, 17 Jun 2011 15:24:09 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Alex http://lbdigest.com/2009/10/25/one-arm-one-network-to-rule-them-all/comment-page-1/#comment-1108 Alex Tue, 27 Oct 2009 14:54:37 +0000 http://lbdigest.com/?p=425#comment-1108 Good article, although this setup adds an important single point of failure. Most people add an additional load-balancer for redundancy with a "floating" VIP. Good article, although this setup adds an important single point of failure. Most people add an additional load-balancer for redundancy with a “floating” VIP.

]]> By: Sean http://lbdigest.com/2009/10/25/one-arm-one-network-to-rule-them-all/comment-page-1/#comment-1104 Sean Mon, 26 Oct 2009 00:59:47 +0000 http://lbdigest.com/?p=425#comment-1104 Not sure if it's used as much, but direct server return (local triangulation - Radware, direct routing - Linux VS) can work in that situation, you just need to put loopbacks on all the servers with the IP of the VIP. In this mode, only the L2 header is rewritten, so the return packet doesn't need to go through the LB to come back. The disadvantage is that the LB only gets to peek into the SYN packet before it has to decide which server gets the connection, so no L7 intelligence! Sean Not sure if it’s used as much, but direct server return (local triangulation – Radware, direct routing – Linux VS) can work in that situation, you just need to put loopbacks on all the servers with the IP of the VIP. In this mode, only the L2 header is rewritten, so the return packet doesn’t need to go through the LB to come back. The disadvantage is that the LB only gets to peek into the SYN packet before it has to decide which server gets the connection, so no L7 intelligence!

Sean

]]>