GTM - Topology load balancing failover when one pool is down
I am looking for a solution to the problem that has been raised several times, but I do not find a confirmed solution. The situation I am in is described in the following post: GTM Topology across pools issue when one of the po... - DevCentral (f5.com)
We have two topology records with the same source, but different destination pools, with different wights:
- SRC: Region X => DEST: Pool A, wieght 200
- SRC: Region X => DEST: Pool B, Wieght 20
When Pool A is down the Topology load balancing for the Wide IP still selects Pool A which is down, and no IP is returned to the client.
If the topology load balancing selection mechanism, is not going to take in the status of the destination pool and just stop on first match in its selection mechanism, then why have "Wieght" at all. I do no believe disabling "longest match" would help as this just affects the order the topology rules are searched, it woudl still stop with the first match.
The often mentioned solution is to use a single pool with Global Availability load balancing, as mentioned in the post: GTM and Topology - DevCentral (f5.com).
The problem I have is that Pool A and Pool B are pools with mulitple generic host servers. I cannot have a pool with all generic host in it as we want to memebers in each Pool are Active/Active and not Active/ Backup