01-24-2014
Make sure you are pining the Persistent IP and NOT the Service IP, because Service IP will jump between the nodes, whereas persistent IP is hard bounded to the node.
You can check the cluster services, and the cluster state, and write a wrapper script to send an email if any of those goes south.
And ofcourse taking into consideration all the valuable suggestions given by forum members.
This User Gave Thanks to ibmtech For This Post:
8 More Discussions You Might Find Interesting
1. High Performance Computing
Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris.
More... (0 Replies)
Discussion started by: Linux Bot
0 Replies
2. High Performance Computing
Dear All,
Can anyone explain about Pros and Cons of SUN and Veritas Cluster ?
Any comparison chart is highly appreciated.
Regards,
RAA (4 Replies)
Discussion started by: RAA
4 Replies
3. Solaris
I folks,
season's greetings.
Hope you had a good festive season.
I've got 2 related problems on the same Sun Cluster 3.2.2 Apache 2.0.63 cluster:
clsetup error: ERROR: Failed to get connection to node localhost
SunOS... (0 Replies)
Discussion started by: cluster
0 Replies
4. Solaris
Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC.
Am thinking how to migrate to sun cluster setup instead.
My plan as follows leave the existing vcs intact as a fallback plan.
Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies
5. UNIX for Dummies Questions & Answers
hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies
6. Solaris
Hello experts -
I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts.
(1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over)
(2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies
7. Red Hat
Hi,
We are having many RedHat linux Server with Cluster facility for availability of service like HTTPD / MySQL.
We face some issue while some issue related to power disturbance / fluctuation or Network failure. There is two Cluster Node configured in... (0 Replies)
Discussion started by: hirenkmistry
0 Replies
8. Shell Programming and Scripting
Hi
I am using perl to ping a list of nodes - with script below :
$p = Net::Ping->new("icmp");
if ($p->ping($host,1)){
print "$host is alive.\n";
}
else {
print "$host is unreacheable.\n";
}
$p->close();... (4 Replies)
Discussion started by: tavanagh
4 Replies
LEARN ABOUT CENTOS
crm_node
PACEMAKER(8) System Administration Utilities PACEMAKER(8)
NAME
Pacemaker - Part of the Pacemaker cluster resource manager
SYNOPSIS
crm_node command [options]
DESCRIPTION
crm_node - Tool for displaying low-level node information
OPTIONS
-?, --help
This text
-$, --version
Version information
-V, --verbose
Increase debug output
-Q, --quiet
Essential output only
Stack:
-A, --openais
Only try connecting to an OpenAIS-based cluster
-H, --heartbeat
Only try connecting to a Heartbeat-based cluster
Commands:
-n, --name
Display the name used by the cluster for this node
-N, --name-for-id=value
Display the name used by the cluster for the node with the specified id
-e, --epoch
Display the epoch during which this node joined the cluster
-q, --quorum
Display a 1 if our partition has quorum, 0 if not
-l, --list
Display all known members (past and present) of this cluster (Not available for heartbeat clusters)
-p, --partition
Display the members of this partition
-i, --cluster-id
Display this node's cluster id
-R, --remove=value
(Advanced) Remove the (stopped) node with the specified name from Pacemaker's configuration and caches
In the case of Heartbeat, CMAN and Corosync 2.0, requires that the node has already been removed from the underlying cluster
Additional Options:
-f, --force
AUTHOR
Written by Andrew Beekhof
REPORTING BUGS
Report bugs to pacemaker@oss.clusterlabs.org
Pacemaker 1.1.10-29.el7 June 2014 PACEMAKER(8)