07-04-2009
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
9 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. 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
4. 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
5. 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
6. Solaris
hi, dear all
I get a problem "VCS ERROR V-16-2-13077 " on VCS 4.1 for Solaris 10.
I can not offline the host2 when the raid is bad.
I don't know the reason and how to offline host2 and switch to host1.
please help me, thank you!
the message of engine_A.log is :
... (2 Replies)
Discussion started by: ForgetChen
2 Replies
7. 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
8. UNIX for Dummies Questions & Answers
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... (1 Reply)
Discussion started by: sankarg304
1 Replies
9. 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 HPUX
cmdeleteconf
cmdeleteconf(1m) cmdeleteconf(1m)
NAME
cmdeleteconf - Delete either the cluster or the package configuration
SYNOPSIS
cmdeleteconf [-f] [-v] [-c cluster_name] [[-p package_name]...]
DESCRIPTION
cmdeleteconf deletes either the entire cluster configuration, including all its packages, or only the specified package configuration. If
neither cluster_name nor package_name is specified, cmdeleteconf will delete the local cluster's configuration and all its packages. If
the local node's cluster configuration is outdated, cmdeleteconf without any argument will only delete the local node's configuration. If
only the package_name is specified, the configuration of package_name in the local cluster is deleted. If both cluster_name and pack-
age_name are specified, the package must be configured in the cluster_name, and only the package package_name will be deleted. cmdelete-
conf with only cluster_name specified will delete the entire cluster configuration on all the nodes in the cluster, regardless of the con-
figuration version. The local cluster is the cluster that the node running the cmdeleteconf command belongs to.
Only a superuser, whose effective user ID is zero (see id(1) and su(1)), can delete the configuration.
To delete the cluster configuration, halt the cluster first. To delete a package configuration you must halt the package first, but you do
not need to halt the cluster (it may remain up or be brought down). To delete the package VxVM-CVM-pkg (HP-UX only), you must first delete
all packages with STORAGE_GROUP defined.
While deleting the cluster, if any of the cluster nodes are powered down, the user can choose to continue deleting the configuration. In
this case, the cluster configuration on the down node will remain in place and, therefore, be out of sync with the rest of the cluster. If
the powered-down node ever comes up, the user should execute the cmdeleteconf command with no argument on that node to clean up the config-
uration before doing any other Serviceguard command.
Options
cmdeleteconf supports the following options:
-f Force the deletion of either the cluster configuration or the package configuration.
-v Verbose output will be displayed.
-c cluster_name
Name of the cluster to delete. The cluster must be halted already, if intending to delete the cluster.
-p package_name
Name of an existing package to delete from the cluster. The package must be halted already. There should not be any
packages in the cluster with STORAGE_GROUP defined before having a package_name of VxVM-CVM-pkg (HP-UX only).
RETURN VALUE
Upon completion, cmdeleteconf returns one of the following values:
0 Successful completion.
1 Command failed.
EXAMPLES
The high availability environment contains the cluster, clusterA , and a package, pkg1.
To delete package pkg1 in clusterA, do the following:
cmdeleteconf -f -c clusterA -p pkg1
To delete the cluster clusterA and all its packages, do the following:
cmdeleteconf -f -c clusterA
AUTHOR
cmdeleteconf was developed by HP.
SEE ALSO
cmcheckconf(1m), cmapplyconf(1m), cmgetconf(1m), cmmakepkg(1m), cmquerycl(1m).
Requires Optional Serviceguard Software cmdeleteconf(1m)