Forum Discussion
I'm going to test this scenario, I've already created the following config further below.
Would this mean that I need to change my Pool Priorities to make both Servers "priority-group 1" rather than 2 & 1?
I guess with this setup the 1st server A that listens gets the 1st connection and all subsequent connections, when server A breaks then server B takes all connections, when Server A comes back on line, old/new connections still remain with Server B....this is what I want only 1 server processing client traffic....however, I need to make sure when both servers start up Monday morning, health checks kick-in that all connections go to Server A firstly not Server B....what I'm asking is does that mean Server A needs to be started firstly, wait for the 1st client connection before its acts for all clients connections. I can't allow Server B to take connections unless Server A dies.
Monday morning, always has to be Server A.
Thanks.
(Active)(/Common)(tmos) list ltm rule "FIX"
ltm rule FIX {
when CLIENT_ACCEPTED {
persist uie 1
}
}
(Active)(/Common)(tmos) list ltm persistence
ltm persistence global-settings { }
ltm persistence universal FIX {
app-service none
defaults-from universal
rule FIX
timeout 3600
}
(Active)(/Common)(tmos) list ltm pool "FIX-19003"
ltm pool FIX-19003 {
load-balancing-mode least-connections-member
members {
fixomln1d01.zit.commerzbank.com:19003 {
address 10.167.20.20
priority-group 1
session monitor-enabled
state up
}
fixomln1d03.zit.commerzbank.com:19003 {
address 10.167.20.11
priority-group 2
session monitor-enabled
state up
}
}
min-active-members 1
monitor FIX
}