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
GRE(4)							   BSD Kernel Interfaces Manual 						    GRE(4)

NAME
gre -- encapsulating network device SYNOPSIS
To compile the driver into the kernel, place the following line in the kernel configuration file: device gre Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_gre_load="YES" DESCRIPTION
The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where they are decapsulated and further routed to their final destination. The ``tunnel'' appears to the inner datagrams as one hop. gre interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands. This driver corresponds to RFC 2784. Encapsulated datagrams are prepended an outer datagram and a GRE header. The GRE header specifies the type of the encapsulated datagram and thus allows for tunneling other protocols than IP. GRE mode is also the default tunnel mode on Cisco routers. gre also supports Cisco WCCP protocol, both version 1 and version 2. The gre interfaces support a number of additional parameters to the ifconfig(8): grekey Set the GRE key used for outgoing packets. A value of 0 disables the key option. enable_csum Enables checksum calculation for outgoing packets. enable_seq Enables use of sequence number field in the GRE header for outgoing packets. EXAMPLES
192.168.1.* --- Router A -------tunnel-------- Router B --- 192.168.2.* / / +------ the Internet ------+ Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal address 192.168.2.1, the following commands will configure the tunnel: On router A: ifconfig greN create ifconfig greN inet 192.168.1.1 192.168.2.1 ifconfig greN inet tunnel A B route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1 On router B: ifconfig greN create ifconfig greN inet 192.168.2.1 192.168.1.1 ifconfig greN inet tunnel B A route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1 NOTES
The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers. This may not be an optimal value, depending on the link between the two tunnel endpoints. It can be adjusted via ifconfig(8). For correct operation, the gre device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop. The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero. SEE ALSO
gif(4), inet(4), ip(4), me(4), netintro(4), protocols(5), ifconfig(8), sysctl(8) A description of GRE encapsulation can be found in RFC 2784 and RFC 2890. AUTHORS
Andrey V. Elsukov <ae@FreeBSD.org> Heiko W.Rupp <hwr@pilhuhn.de> BUGS
The current implementation uses the key only for outgoing packets. Incoming packets with a different key or without a key will be treated as if they would belong to this interface. The sequence number field also used only for outgoing packets. BSD
November 7, 2014 BSD
All times are GMT -4. The time now is 06:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy