Monitoring ephemeral pool members & nodes

If an Ephemeral pool member goes down, does that failure trigger anything on the DNS / Node side? No, new DNS request is only done after TTL expires, or bigd is restarted.

What is the real life difference between Enabled and Disabled? Disable means the system will only use one IP from the DNS response. Enable, means the system will use all IPs in the response, and also delete nodes that are not present anymore in the response.

What would it mean for a node to auto populate, but a pool member using that node to NOT be set to do that? The auto populate option is only for nodes, as the FQDN only applies to nodes.

How does the node resolution internal work with the DNS Cache option in the system settings? The bigd process that is responsible for monitoring, is also responsible for the DNS queries for this functionality. It will cache the request, until the TTL expires, or the process is restarted.

See this solution for more information:

https://support.f5.com/csp/article/K47726919