Ha mailserver, is possible active/active with "constant" connection? Post: 303045628

Sponsored Content

Top Forums UNIX for Advanced & Expert Users Ha mailserver, is possible active/active with "constant" connection? Post 303045628 by hicksd8 on Saturday 4th of April 2020 02:09:53 PM

04-04-2020

Moderator

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.

hicksd8

View Public Profile for hicksd8

Find all posts by hicksd8

6 More Discussions You Might Find Interesting

1. Windows & DOS: Issues & Discussions

Windows Active Network Connection Override

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

2. AIX

Question about HACMP for active-active mode

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

3. Solaris

Link based Active Active IPMP

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

4. Shell Programming and Scripting

Extract text between two specified "constant" texts using awk

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

5. Linux

active mode ftp connection from 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...

6. Shell Programming and Scripting

How do I calculate total number of active and non active hosts?

#!/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

LEARN ABOUT HPUX

cmhaltnode

cmhaltnode(1m)															    cmhaltnode(1m)

NAME

       cmhaltnode - halt a node in a high availability cluster

SYNOPSIS

       cmhaltnode [-f] [-v] [-t] [node_name...]

DESCRIPTION

       cmhaltnode causes a node to halt its cluster daemon and remove itself from the existing cluster.

       To halt cluster on the node, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the cluster configu-
       ration file. See access policy in cmquerycl.

       When cmhaltnode is run on a node, the cluster daemon is halted and, optionally, all packages that were running on that node  are  moved	to
       other nodes if possible.

       If node_name is not specified, the cluster daemon running on the local node will be halted and removed from the existing cluster.

       If  you issue this command while a cluster is still in the process of forming, the command will fail with the message "Unable to connect to
       daemon."  If this happens, wait for the cluster to form successfully, then issue the command again.

   Options
       cmhaltnode supports the following options:

	      -f	Force the node to halt even if there are packages or group members running on it.  The group members on the node  will	be
			terminated.   The halt scripts for all packages running on the node will be run; based on priority or dependency relation-
			ships, this may affect packages on other nodes. In other words, packages on other nodes may either start or halt based	on
			this  package halting.	If the package configuration and current cluster membership permit, and if the package halt script
			succeeds, the packages will be started on other nodes.	Without this option, if packages are running on  the  given  node,
			the command will fail.	If a package fails to halt, the node halt will also fail.

	      -v	Verbose output will be displayed.

	      -t	Test  only.  Provide  an assessment of the package placement without affecting the current state of the nodes or packages.
			This option validates the node's eligibility with respect to the package dependencies as well as the external dependencies
			such as EMS resources, package subnets, and storage before predicting any package placement decisions. If there is a pack-
			age in maintenance mode running on the nodes being halted, the package will always be halted and not failover  to  another
			node; the report will not display an assessment for that package.

	      node_name...
			The name of the node(s) to halt.

RETURN VALUE

       cmhaltnode returns the following value:

	       0   Successful completion.
	       1   Command failed.

EXAMPLES

       Halt the cluster daemon on two other nodes:

	      cmhaltnode node2 node3

AUTHOR

       cmhaltnode was developed by HP.

SEE ALSO

       cmquerycl(1m), cmhaltcl(1m), cmruncl(1m), cmrunnode(1m), cmviewcl(1m), cmeval(1m).

						      Requires Optional Serviceguard Software					    cmhaltnode(1m)