11-26-2012
Heartbeat network IP range in Clustering
I am trying to do the two node clustering with serviceguard package in redhat 5 and I am following this link http ://pbraun.nethence.com/doc/sysutils/mcsg.html
Here They are mentioning 10.1.1 for network use and 10.1.2 and 10.1.3 for HeartBeat use,
I have a doubt, How to make a heartbeat network, Is there any procedure,
Shall I use 192.168.0 for network use and 192.168.10 for HeartBeat use , But here network and Heartbeat IP range is comming under the same network,
Thanks for Reply,
10 More Discussions You Might Find Interesting
1. Programming
hello,
Can anyone please tell me how can i check the availability of the online user in a client-server environtment.
This is for a program where lakhs of client are connected to the server and the server has to check the availability of the every client in every minute.
So polling every client... (0 Replies)
Discussion started by: shushilmore
0 Replies
2. Linux
has anyone installed linux-heartbeat on Solaris 9??
If yes, which version???
which is the best compiler to build it?? cc, ucbcc, gcc??
what other packages are needed to build it besides m4, autoconf, automake and libtool??
what GNU tools are needed???
thanks a lot (0 Replies)
Discussion started by: eldiego
0 Replies
3. Solaris
we have a vcs cluster set up and noticed that they were showing one of the heart beat link qfe3 as DOWN. Both qfe2 and qfe3 were fine all along, btw if I were to push in/re-set the hb cable, do you know whether it will panic or cause anything to the system,? Its a DB critical prod nodes (3 Replies)
Discussion started by: incredible
3 Replies
4. UNIX for Advanced & Expert Users
hi guys
I hope this goes here
Have someone used Linux heartbeat to send email when the Slave server becomes the Master?
I've read I can configure the MailTo under
/etc/ha.d/resource.d
but I really don't know how to do it.
I basically need my primary server to send an email when it... (2 Replies)
Discussion started by: karlochacon
2 Replies
5. Cybersecurity
hi
i'm configuring linux heartbeat in my two redhat boxes
i have below few things to clarify
can i set up heartbeat between two different notworks? (e.g primary server IP is 192.168.x.x and secondary server IP is 10.48.X.X)
i got below error in my secondary server once primary is down
... (2 Replies)
Discussion started by: asela115
2 Replies
6. UNIX for Dummies Questions & Answers
hi,
I'm currently trying to configure Linux heartbeat on my two Linux servers(where SMPP service is running)
my two machines are in two different location with different notworks (primary is in 192.168.x.x and secondary is in 10.48.x.x network)
I want to know whether is it possible to... (0 Replies)
Discussion started by: asela115
0 Replies
7. AIX
Hello.
I have a cluster with two heartbeat networks.
Both are on separate VG.
Some one varyoned those Vg's on one node.
After that heartbeat network went down on both nodes.
I varyoffed those two Vg's
networks came back up
but cluster is still in UNSTABLE status and in hacmp.out... (1 Reply)
Discussion started by: phobus
1 Replies
8. AIX
Hi
I'm a little rusty with HACMP, but wanted to find out if it is possible to remove a disk heartbeat network from a running HACMP cluster.
Reason is, I need to migrate all the SAN disk, so the current heartbeat disk will be disappearing. Ideally, I'd like to avoid taking the cluster down to... (2 Replies)
Discussion started by: cmcbugg
2 Replies
9. UNIX for Advanced & Expert Users
Hi there,
anybody can help me get a manual or a website where LVS and Heartbeat for UBUNTU (please not for REDHAT ) is hosted.
Any help will be much appreciated.
neuvin (0 Replies)
Discussion started by: neuvinapp
0 Replies
10. Programming
Hello, I want to query something simple which works as a standalone sqlplus query perfectly:
Table statements:
ALTER TABLE MP$PATHLOADER.ISALIVE
DROP PRIMARY KEY CASCADE;
DROP TABLE MP$PATHLOADER.ISALIVE CASCADE CONSTRAINTS;
CREATE TABLE MP$PATHLOADER.ISALIVE
(
ISALIVE_PK ... (2 Replies)
Discussion started by: sdohn
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)