Load balance to node in the same DC where VIP is active

That isn't really an HA configuration, it is a DC failover design.

 

LTM HA requires that each LTM in the HA pair has the same view of the network, and treats all the pool member as equivalent. You want one pool member to be associated to one LTM in one DC, and the other pool member to be associated to the other LTM in the other DC. LTM HA cannot be configured to do this.

 

You also have the issue of moving an IP address (the virtual IP) from one DC to another - how are you planning to make that work if the DC's have different uplinks to the internet?

 

For a DC failover design, you would have a LTM (or LTM HA pair) and virtual in each DC, and use a F5 GTM/DNS to send traffic to whichever DC is preferred. If the GTM detects that a DC is down (pool member,virtual or upstream link failure), then it starts sending traffic using the wideIP to the other DC until service is restored.

 

I know it's a bit special setup, but that came as a requirement from the application team. It does not make much sense to me either, but I wanted to find out if something like that is even possible if I really have to implement it.

Thanks Farshadd for the tip, it is actually exactly what I need. I tried it and it works with this simple irule assigning one of two different pools:

when CLIENT_ACCEPTED {
    set f5 $static::tcl_platform(machine)
    if { $f5 equals "f5DC1.mydomain.com" } { 
        pool pool_APP_DC1_DC2
    } elseif { $f5 equals "f5DC2.mydomain.com" } {
        pool pool_APP_DC2_DC1
    } else {
        log local0. "Error: machine info invalid!"
        reject
    }
}

The pools will use priority group scheme:

pool_APP_DC1_DC2: server in DC1 higher priority than the server in DC2

pool_APP_DC2_DC1: server in DC2 higher priority than the server in DC1

With this setup I need only 1 VIP, the HA will be achieved because the VIP can still fail over to the other DC, and each pool will have the possibility to fail over to second pool member shall the higher priority member become unavailable. I agree this is not about balancing the load, but more about "same DC VIP to server stickyness" while keeping the HA in place.

I hope the DC's have a low-latency interconnect for HA. I suspect that you will encounter unforseen issues with this implementation.

The only other recommendation I can make:

Shift the static variable declaration to RULE_INIT for efficiency

when RULE_INIT {
    set f5 $static::tcl_platform(machine)
}
when CLIENT_ACCEPTED {
    if { $f5 equals "f5DC1.mydomain.com" } { 
        pool pool_APP_DC1_DC2
    } elseif { $f5 equals "f5DC2.mydomain.com" } {
        pool pool_APP_DC2_DC1
    } else {
        log local0. "Error: machine info invalid!"
        reject
    }
}