04-04-2020
You problem is with network timeout settings; either the cluster or the clients.
Manually shutting down one of the cluster nodes may not give you the same result as a true CPU/power/whatever failure because the cluster software suite will probably see you do that. It would be better to simply pull out the RJ45 network connection to one of them simulating a network connection failure.
Anyway, the point is that a cluster failover takes time. During this time the virtual ip address is switched from one node to the other. Depending on the cluster suite this will take seconds/minutes. The fact that the client will reconnect to the surviving cluster node after you restart it proves that, had it waited long enough, it would have been able to reconnect on its own.
So the solution is to either (1) configure the cluster to failover faster, or (2) increase the timeout that clients will wait before giving up. That means that a new connection to the virtual ip address can be made before the configured timeout period ends.
6 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
Hi All,
I use two Network Connections at work: Wireless and LAN.
Wireless network has no limitations, but LAN internet has a web filter.
I start a download using my Wireless conn. (At this point, LAN is disabled)
But when I activate my LAN connection my download stops immediately.
LAN... (4 Replies)
Discussion started by: kalavkalav
4 Replies
2. AIX
Hi all,
I am new to HACMP. So sorry for the newie question. But I did search the forum and it seems that no one asks this before.
So if a 2-node cluster runs in active-active mode (and the same application), what is the benefit of using HACMP ?
If it runs in active-stanby, it is easy to... (9 Replies)
Discussion started by: qiulang
9 Replies
3. Solaris
Hi,
I need to configure 4 ip address (same subnet and mask) in one ipmp group (two interfaces) in an active active formation (link based). Can some one provide the steps or a tutorial link.
Thanks (2 Replies)
Discussion started by: Mack1982
2 Replies
4. Shell Programming and Scripting
Hi All,
From the title you may know that this question has been asked several times and I have done lot of Googling on this.
I have a Wikipedia dump file in XML format. All the contents are in one XML file i.e. all different topics have been put in one XML file. Now I need to separate them and... (1 Reply)
Discussion started by: shoaibjameel123
1 Replies
5. Linux
Hi,
We have one java client which connects to a windows server through ftp in active mode and gets files. When we run this client on hp-ux, it is able to transfer 100k files. But when we run the same client on Linux server it is able to transfer only 200 files at max and it is hanging there... (1 Reply)
Discussion started by: urspradeep330
1 Replies
6. Shell Programming and Scripting
#!/bin/bash
for digit in $(seq 1 10)
do
if ping -c1 -w2 192.168.1.$digit &> /dev/null
then
echo "192.168.1.$digit is UP"
else
echo "192.168.1.$digit is DOWN"
fi
done (3 Replies)
Discussion started by: fusetrips
3 Replies
cmdo(1m) cmdo(1m)
NAME
cmdo - Execute process on multiple remote Serviceguard nodes.
SYNOPSIS
cmdo [[-n node_name]...] [-t timeout] command
DESCRIPTION
cmdo will execute a process on a multiple remote Serviceguard nodes and return any output or return value.
cmdo is limited in several ways. cmdo is best suited for situations where other remote execution facilities are not available. For a more
full featured tool for remote execution within a cluster, see cexec(1m) provided by Distributed Systems Administration Utilities.
To use this command, the local user must have the root access role on each of the involved nodes. For more information on Serviceguard
access control policies, see the manual, Managing Serviceguard.
To use the cmdo command without specifying -n options, the local node must be configured into a Serviceguard cluster. If no -n options are
specified, the command will be executed on all available nodes in the cluster.
The command will be executed in an environment which matches the local node. All environment variables defined locally will be available
on the remote node.
Output from stderr and stdout for the remote process will be combined and delivered in one transmission. This command should not be used
for interactive commands or commands which will return large quantities of output. Output from each node will be displayed sequentially as
the operation is executed on each remote node.
Input via stdin is not supported.
Killing the cmdo process does not stop any remote executions of the command. cmdo should not be used on any command which may hang without
specifying a timeout value.
Options And Arguments
-t timeout
Kill the executed command if it does not exit within the specified timeout (in seconds)
-n node_name
Serviceguard node to execute command on. If no -n options are specified, all the nodes configured in the cluster are used.
command
Command to execute on remote node. May be quoted.
RETURN VALUE
cmdo returns the following values:
0 Successful completed on all nodes.
>0 Command failed on one or more nodes with the specified exit value.
EXAMPLES
Execute an 'ls' in a remote directory on all nodes within the cluster.
cmdo ls /tmp
Execute an 'ls' in a remote directory on two nodes not configured within a Serviceguard cluster.
cmdo -n node1 -n node2 ls /tmp
AUTHOR
cmdo was developed by HP.
SEE ALSO
cexec(1m), cmcp(1m), cmexec(1m), cmsync(1m), cmquerycl(1m), cmviewcl(1m)
Requires Optional Serviceguard Software cmdo(1m)