Sponsored Content
Special Forums IP Networking Linux load balancer ping redirect to other interface Post 302775315 by hicksd8 on Monday 4th of March 2013 02:51:26 PM
Old 03-04-2013
I'm not an expert on this product but I might write a few things that might help.

With this form of load balancing (sometimes called clustering), each real node has a fixed ip address that doesn't ever move. These are the REAL ip addresses. There is a VIP (virtual ip address) that all the clients use that is the address which, in the event of a failure, switches from one real box to the other. The clients aren't aware of the real IP addresses, only the virtual one.

I also notice that Centos users often configure a 'director' service on a third separate machine but I don't believe this is mandatory.

Hope that helps. Perhaps a Centos expert will contribute to this thread.

Anyway, you need to configure a VIP. Search Google if you need help.

Pinging one of the real ip's will only ever get a response from that particular box.
 

6 More Discussions You Might Find Interesting

1. Programming

Load Balancer

Halo mates, I m going to write a load balancer with C. Does anybody know some good reference on this? Cheers, Elton (5 Replies)
Discussion started by: EltonSky
5 Replies

2. AIX

hacmp ip load balancer failover

Hi All, How do I failover on the ip load balancer (back and forth)? It involves first to load a new config on the passive ip. If success, load the new config on the ip active (which is now passive). Any idea, please. Thanks in advance. (0 Replies)
Discussion started by: itik
0 Replies

3. Red Hat

What is the Best Load Balancer for Linux?

Hi, What's the best load balancer for Linux (CentOS, SuSE) according to your personal experience? Linux Virtual Server (LVS) is a famous one, but their download site has not been updated since 2007. Their web and mailing list are so quiet. Is the Ultra Monkey project including LVS... (1 Reply)
Discussion started by: aixlover
1 Replies

4. UNIX for Advanced & Expert Users

piranha load balancer failover

we use piranha load balancer with two nodes even the primary node is running fine and up failover happend to secondary node this happend quite few times ehy node2 cannot talk to node1 what logs are to be checked and investigate why failover occured pulse: partner dead: activating... (0 Replies)
Discussion started by: robo
0 Replies

5. Linux

Server Load balancer

Hello Guys, Hope you all doing well . :) I was checking load balance command (uptime)on VM server and got below output. # uptime 07:08:40 up 52 min, 2 users,a load average: 0.45, 0.11, 0.03 A :How we can calculate load average? Thank you in advance !! Cheers:) Dont forget... (1 Reply)
Discussion started by: Nats
1 Replies

6. Virtualization and Cloud Computing

A load balancer for Nomachine NX

Hello, in case somebody has a NoMachine NX cluster, and is suffering from its dumb round-robin dispatcher, here is a solution: nxpub (NX Pluggable User Balancer). It should run on all LUnix OS. Scripts for install/uninstall are supplied. While tested with NX 3 (NX 3.5 is the latest), it might... (2 Replies)
Discussion started by: MadeInGermany
2 Replies
fair(7) 					       BSD Miscellaneous Information Manual						   fair(7)

NAME
fair -- simple TCP load balancing service DESCRIPTION
fair is a load balancer for TCP connections. It can be used to distribute incoming connections for SMTP, HTTP or any other TCP service to multiple hosts, distributing the load as evenly as possible. fair consists of two daemons. The carrousel is the front-end; it keeps track of back-end hosts and their status, and forwards incoming con- nections to the back-ends in such a way that the load is distributed fairly. The transponder runs on the back-end hosts, it registers with the carrousel and sends it status information. The TCP connections forwarded by the carrousel are not sent to the transponder daemons but are sent directly to the desired service running on the back-end host. Both daemons share a single configuration file. EXAMPLES
The following example shows how to set up fair to service HTTP connections and to distribute them over back-ends in the 192.168.1.0/24 sub- net. The configuration file /etc/fair.conf contains the following: WorkerService = http BalancerService = http AllowUDP = ^192.168.1.[0-9]+$ On www.example.com, the front-end server receiving the incoming HTTP connections, just run: carrousel On each of the back-ends run: transponder www.example.com SEE ALSO
carrousel(8), transponder(8), fair.conf(5) Debian GNU/Linux June 1, 2019 Debian GNU/Linux
All times are GMT -4. The time now is 12:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy