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
TGN(1) TGN(1)
NAME
tgn - a network traffic generator
SYNOPSIS
tgn [-V] [-v] [-l] [-s random seed] [-w PCAP filename] [-o output speaker] [-c packet count] [-h] [PDU definition]
DESCRIPTION
tgn is a network traffic generator. It is command-line interface (CLI) program that does the same thing as the send_network command of the
Network Expect framework. Refer to nexp(1) for additional details regarding the send_network command.
The only mandatory option is a PDU definition.
The -c switch allows to specify the number of packets to send. If -c is not provided then the number of packets to send is calculated
automatically based on the PDU definition.
-V causes tgn to print its version number and exit.
The -s flag allows to specify a random seed that will cause predicatibility of pseudo-random numbers generated by tgn during execution of a
script. In cases where tgn is used as a protocol fuzzer, this option is useful to be able to re-generate a specific test case.
-v increases the verbosity level. Additional information may be displayed when the verbosity level is higher.
The -l flag causes tgn to display all available network speakers and exit. See nexp(1) for a discussion of network speakers.
The -o flag allows to select a specific network speaker for output. Use the -l option to list available speakers. By default, the "ip"
speaker (kernel-routed IP packet delivery) is tried first and if it is not available, which can happen if tgn is not run with root
privileges, the "hex" speaker is used.
The PDU definition is a string that defines a PDU. It uses libpbuild PDU syntax.
EXAMPLES
shell# tgn -o eth0 "ip(dst = 192.168.1.1)/icmp-echo(id = 'random')"
shell# tgn "ip(src = 192.168.0.1, dst = <192.168.0.10, 192.168.0.11>,ttl = <1, 2>)/"
"tcp(src = 'random', dst = 22..25, window = 16384,syn, seq = 'random', ack-seq = 0)"
shell# tgn -w /tmp/cap -c 5 "ether()/ip(dst = 1.2.3.4++)/icmp-echo(seq = 0++)"
&& wireshark /tmp/cap
BUGS
tgn has not been ported to Microsoft Windows.
VERSION
This man page is correct for version 1.0 of tgn.
SEE ALSO
nexp-numspec(1), nexp-payload(1), nexp-ether(5), nexp-gre(5), nexp-ip(5), nexp-mpls(5), nexp(1)
AUTHOR
Network Expect was written by Eloy Paris <peloy@netexpect.org>. However, Network Expect borrows ideas from lots of Open Source tools like
Nemesis, Packit, hping, Expect, and Scapy. The Network Expect author is indebted to the authors of these tools for their contribution.
This man page was written by Eloy Paris.
09 September 2009 TGN(1)