F5 DNS Enhancements for DSC in BIG-IP v13
Prior to v13, F5 DNS assumes that all devices in a cluster have knowledge about all virtual servers, which makes virtual server auto-discovery not function properly. In this article, we’ll cover the ...
Updated Jun 06, 2023
Version 2.0
JRahm
Admin
Admin
dragonflymr
Cirrostratus
CirrostratusHi,
Great article. It's almost what I am looking for but I am still not sure about small details. Let's say I have two DC and stretched Active-Active cluster. How such cluster should be defined in GSLB?
Should I create two separate Server objects (for each node) to be able to assign each node to the correct DC or not really?
Goal is to use WideIP to return IP of VS from both DCs (during normal operation, Let's say based on RR). If one DC (or LTM) will fail TG will be migrated to remaining node (so I will have both VSs on the same node in one DC) but still IPs of both VS should be returned (if of course PM in failed DC are still marked UP). Another option is to make moved VS down at GSLB level (even if it's UP at LTM level) - not sure if possible?
Will singe Server object work?
Still it seems a bit not up to real topology - each node is in reality in separate DC, so it seems that more logical option is to create two Sever objects, each with one cluster node, then correct DC can be assigned to each Server (node) - but I am not sure if this is supported/correct way to configure GSLB?
Piotr