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
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
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
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
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
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
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
LEARN ABOUT DEBIAN
rlm_ippool_tool
RLM_IPPOOL_TOOL(8) System Manager's Manual RLM_IPPOOL_TOOL(8)
NAME
rlm_ippool_tool - dump the contents of the FreeRadius ippool database files
SYNOPSIS
If an ipaddress is specified then that address is used to limit the actions or output.
rlm_ippool_tool [-a] [-c] [-o] [-v] session-db index-db [ipaddress]
Mark the entry nasIP/nasPort as having ipaddress
rlm_ippool_tool -n session-db index-db ipaddress nasIP nasPort
Update old format database to new.
rlm_ippool_tool -u session-db new-session-db
DESCRIPTION
rlm_ippool_tool dumps the contents of the FreeRADIUS ippool databases for analyses or for removal of active (stuck?) entries.
Or with the -n argument adds a usage entry to the FreeRADIUS ippool databases.
OPTIONS
-a Print all active entries.
-c Report number of active entries.
-r Remove active entries.
-v Verbose report of all entries.
-o Assume old database format (nas/port pair, not md5 output).
-n Mark the entry nasIP/nasPort as having ipaddress.
-u Update old format database to new.
EXAMPLES
Given the syntax in the FreeRadius radiusd.conf:
ippool myippool {
range-start = 192.168.1.0
range-stop = 192.168.1.255
[...]
session-db = ${raddbdir}/ip-pool.db
ip-index = ${raddbdir}/ip-index.db
}
To see the number of active entries in this pool, use:
$ rlm_ippool_tool -c ip-pool.db ip-index.db
13
To see all active entries in this pool, use:
$ rlm_ippool_tool -a ip-pool.db ip-index.db
192.168.1.5
192.168.1.82
192.168.1.244
192.168.1.57
192.168.1.120
192.168.1.27
[...]
To see all information about the active entries in the use, use:
$ rlm_ippool_tool -av ip-pool.db ip-index.db
NAS:172.16.1.1 port:0x2e8 - ipaddr:192.168.1.5 active:1 cli:0 num:1
NAS:172.16.1.1 port:0x17c - ipaddr:192.168.1.82 active:1 cli:0 num:1
NAS:172.16.1.1 port:0x106 - ipaddr:192.168.1.244 active:1 cli:0 num:1
NAS:172.16.1.1 port:0x157 - ipaddr:192.168.1.57 active:1 cli:0 num:1
NAS:172.16.1.1 port:0x2d8 - ipaddr:192.168.1.120 active:1 cli:0 num:1
NAS:172.16.1.1 port:0x162 - ipaddr:192.168.1.27 active:1 cli:0 num:1
[...]
To see only information of one entry, use:
$ rlm_ippool_tool -v ip-pool.db ip-index.db 192.168.1.1
NAS:172.16.1.1 port:0x90 - ipaddr:192.168.1.1 active:0 cli:0 num:0
To add an IP address usage entry, use:
$ rlm_ippool_tool -n ip-pool.db ip-index.db 192.168.1.1 172.16.1.1 0x90
rlm_ippool_tool: Allocating ip to nas/port: 172.16.1.1/144
rlm_ippool_tool: num: 1
rlm_ippool_tool: Allocated ip 192.168.1.1 to client on nas 172.16.1.1,port 144
SEE ALSO
radiusd(8)
AUTHORS
Currently part of the FreeRADIUS Project (http://www.freeradius.org) Originally by Edwin Groothuis, edwin@mavetju.org
(http://www.mavetju.org)
Mailing list details are at http://www.freeradius.org/
RLM_IPPOOL_TOOL(8)