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
CLONE(8)							    NUT Manual								  CLONE(8)

NAME
clone - UPS driver clone NOTE
This man page only documents the specific features of the clone driver. For information about the core driver, see nutupsdrv(8). DESCRIPTION
This driver, which sits on top of another driver socket, allows users to group clients to a particular outlet of a device and deal with this output as if it was a normal UPS. EXTRA ARGUMENTS
This driver supports the following settings: load.off=command Recommended. Set the command on the "real" UPS driver that will be used to switch off the outlet. You need both load.off and load.on in order to power cycle the outlet. Otherwise, shutting down the clients powered by an outlet is a one way street (see IMPORTANT). load.on=command Recommended. Set the command on the "real" UPS driver that will be used to switch on the outlet. You need both load.off and load.on in order to power cycle the outlet. Otherwise, shutting down the clients powered by an outlet is a one way street (see IMPORTANT). load.status=value Recommended. Set the variable on the "real" UPS driver that will be used to indicate the outlet status (i.e. on/off). If not specified, the clone driver will attempt to keep track of the outlet status, but this is less reliable. offdelay=num Set the timer (in seconds) before the outlet is turned off after the shutdown condition (OB LB) for this outlet is met or a command to shutdown was issued. Defaults to 120 seconds. ondelay=num Set the timer (in seconds) for the outlet to switch on in case the power returns after the oulet has been switched off. Defaults to 30 seconds. mincharge=value Set the remaining battery level when the clone UPS switches to LB (percent). minruntime=value Set the remaining battery runtime when the clone UPS switches to LB (seconds). IMPLEMENTATION
The port specification in the ups.conf(5) reference the driver socket that the "real" UPS driver is using. For example: [realups] driver = usbhid-ups port = auto [clone-outlet-1] driver = clone port = usbhid-ups-realups load.on = outlet.1.load.on load.off = outlet.1.load.off load.status = outlet.1.status [...] IMPORTANT
Unlike a real UPS, you should not configure a upsmon master for this driver. When a upsmon master sees the OB LB flags and tells the upsd server it is OK to initiate the shutdown sequence, the server will latch the FSD status and it will not be possible to restart the systems connected without restarting the upsd server. This will be a problem if the power returns after the clone UPS initiated the shutdown sequence on it's outlet, but returns before the real UPS begins shutting down. The solution is in the clone driver, that will insert the FSD flag if needed without the help of a upsmon master. CAVEATS
The clone UPS will follow the status on the real UPS driver. You can only make the clone UPS shutdown earlier than the real UPS driver, not later. If the real UPS driver initiates a shutdown, the clone UPS driver will immediately follow. Be aware that the commands to shutdown/restart an outlet on the real UPS drivers are not affected, so if you tell the real UPS driver to shutdown the outlet of the clone UPS driver, your clients will lose power without warning. AUTHOR
Arjen de Korte <adkorte-guest@alioth.debian.org> SEE ALSO
upscmd(1), upsrw(1), ups.conf(5), nutupsdrv(8) Internet Resources: The NUT (Network UPS Tools) home page: http://www.networkupstools.org/ Network UPS Tools 05/21/2012 CLONE(8)
All times are GMT -4. The time now is 12:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy