Heartbeat configuring in Redhat

Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Heartbeat configuring in Redhat
# 1  
Old 10-21-2010
Data Heartbeat configuring in Redhat


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 configure heartbeat between two such different networks (what i found by surfing internet is the way of configuring in same network)

if possible, can i configure to listen to my primary server IP instead of having a secondary IP in primary server (since my SMPP service is running with my primary server's IP)

Please someone advice on this

Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Red Hat

configuring MYsql db on redhat cluster

Hello, can someone please suggest me in configuring the mysql db on redhat cluster, I have few questions. 1. where do I have to configure heart beat links, and is there any file in the redhat cluster that we update it to use these ipaddress and these interface on the node. 2. I am configuring... (0 Replies)
Discussion started by: bobby320
0 Replies

2. 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

3. IP Networking

Configuring DNS Server in Linux Redhat

Can someone help with a detail step-by-step oh how to configure DNS server on Linux Server. - I need to have 3 IP addresses map to a single hostname. for clients I'm a Linux rookie. Thanks Oscar (1 Reply)
Discussion started by: FrankOscar
1 Replies

4. AIX

Heartbeat network down

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

5. Cybersecurity

Heartbeat configuring issue

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. Solaris

VCS heartbeat

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

7. UNIX for Advanced & Expert Users

Linux heartbeat on redhat 4:node dead

Hi. I have started heartbeat on two redhat servers. Using eth0. Before I start heartbeat I can ping the two server to each other. Once I start heartbeat both the server become active as they both have warnings that the other node is dead. Also I am not able to ping each other. After stopping... (1 Reply)
Discussion started by: amrita garg
1 Replies

8. Red Hat

Problem with configuring host name in Redhat Linux 5

Hi All when I give the command, $ ping <hostname> I get the following error ping: unknown host <hostname> I have checked in the following files, /etc/sysconfig/network /etc/hosts /etc/resolv.conf /etc/nsswitch.conf Every where in these files host name and IP address are given... (2 Replies)
Discussion started by: nagapradeep
2 Replies

9. Linux

linux-heartbeat on Solaris 9

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

10. Programming

checking the heartbeat of the online user

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
Login or Register to Ask a Question
CL_STATUS(1)							   User commands						      CL_STATUS(1)

cl_status - Check status of the High-Availability Linux (Linux-HA) subsystem SYNOPSIS
cl_status sub-command options parameters DESCRIPTION
cl_status is used to check the status of the High-Availability Linux subsystem. SUPPORTED SUB-COMMANDS hbstatus Indicate if heartbeat is running on the local system. listnodes List the nodes in the cluster. nodetype ping|normal List the nodes of the given type. Note Ping nodes are obsolete in Pacemaker cluster, having been replaced with the pingd resource agent. listhblinks node List the network interfaces used as heartbeat links. node should be specified as listed in the ha.cf(5) file for the cluster. hblinkstatus node link Show the status of a heartbeat link. node should be specified as listed in the ha.cf(5) file for the cluster. link should be as per the output of the listhblinks subcommand. clientstatus node client [timeout] Show the status of heartbeat clients. node and client should be specified as listed in the ha.cf(5) file for the cluster. Timeout is in milliseconds, the default is 100ms. rscstatus Show the status of cluster resources. Status will be one of: local, foreign, all or none. Note This option is deprecated, it is obsolete in Pacemaker clusters. parameter -p parameter Retrieve the value of cluster parameters. The parameters may be one of the following: apiauth, auto_failback, baud, debug, debugfile, deadping, deadtime, hbversion, hopfudge, initdead, keepalive, logfacility, logfile, msgfmt, nice_failback, node, normalpoll, stonith, udpport, warntime, watchdog. Note Some of these options are deprecated; see ha.cf(5) OPTIONS
The following options are supported by heartbeat: -m Make the output more human readable. The default output should be easier for scripts to parse. Available with all commands. -p List only 'ping' nodes. Available with listnodes sub-command. Note Ping nodes are obsolete in Pacemaker cluster, having been replaced with the pingd resource agent. -n List only 'normal' nodes. Available with listnodes sub-command. SEE ALSO
heartbeat(8), ha.cf(5), authkeys(5) AUTHORS
Alan Robertson <alanr@unix.sh> cl_status Juan Pedro Paredes Caballero <juampe@retemail.es> man page Simon Horman <horms@verge.net.au> man page Florian Haas <florian.haas@linbit.com> man page Heartbeat 3.0.5 24 Nov 2009 CL_STATUS(1)

Featured Tech Videos