04-05-2020
A small addon for active active - so traffic flows thru both haproxys.
You need 2 VIP address for keepalived, on one node first VIP is master, on another second VIP is master.
Both will be on one node in case of node failure.
Then, you add third entry on your DNS system (mymail.example.com) -> pointing to those two VIP addresses.
This is the record you 'attack' from outside with your clients.
Since both VIP IP addresses are always active, clients will be always be able to connect to both when DNS is queried.
Client attempts to make a connection to mymail.example.com ( one VIP is returned in RR fashion from the pool of two ) --> HAPROXY --> your mail server.
Setup sticky session in haproxy and make it listen on 0.0.0.0
Be sure to allow VRRP traffic between those two LB.
In case of failure, everything hicks wrote stands, clients connected to failed VIP will notice a short failover and reconnect to second node.
But only roughly 50% of those, since half of those went to another VIP using same DNS record.
Hope that helps
Regards
Peasant.
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
Xserver(1) General Commands Manual Xserver(1)
NAME
X - X Window System display server dispatcher
SYNOPSIS
X [ option ...]
DESCRIPTION
:
Hewlett-Packard supports two X servers on HP-UX platforms, the Xhp X server which supports HP VISUALIZE graphics devices and the Xf86 X
server which supports all other graphics devices. These X servers are delivered as /usr/bin/X11/Xhp and /usr/bin/X11/Xf86.
The X dispatcher determines which X server to launch based on the available graphics devices. The control file /etc/X11/Xstart can provide
additional guidance to the X dispatcher. The control file allows the user to specify which X server to start for given display connection
numbers. The only X servers supported by the X dispatcher are Xhp, Xf86 and Xvfb. If no Xstart file exists, the dispatcher loads the
appropriate X server for the graphics device in the system. HP-UX does not deliver the /etc/X11/Xstart file. This file can be created by
using the SAM/SMH utility.
OPTIONS
If the X dispatcher is invoked with no arguments, the display connection is assumed to be :0. The X dispatcher checks for display connec-
tion options and, if found, uses that display connection number when it checks the Xstart file. All other options are passed on to the X
server when it is started and it is the X server's responsibility to validate these options. Not all options may be supported on both X
servers; refer to Xhp(1) and Xf86(1) to verify supported options for each X server.
RETURN VALUE
None
Xstart EXAMPLES
The control file syntax is the X server to start followed by the display connection number. Valid entries take the form of:
Xhp :0 Start the Xhp X server on display connection 0
Xf86 :10 Start the Xf86 X server on display 10
/usr/bin/X11/Xhp :5 Start the Xhp X server on display connection 5
/usr/bin/X11/Xvfb :7 Start the X Virtual Framebuffer server on display connection 7
FILES
/etc/X11/Xstart Dispatcher control file.
/var/X11/Xserver/logs/Xstartup.N.log X dispatcher log file for display N.
SEE ALSO
X(1), Xhp(1), Xf86(1)
STANDARDS CONFORMANCE
See the appropriate section in Xhp(1) or Xf86(1).
Xserver(1)