Forum Discussion
CirrusFQDN Node Configuration
MVPFirst, when using an FQDN you do not have any need to create the node manually or any pool member for that matter because the F5 will automatically create the appropriate node if it doesn't exist. Second, make sure that you modify the FQDN TTL value otherwise the F5 will not honor the TTL provided by the DNS server in question. Third, the F5 will always perform health monitors from the IP with the more specific route. Finally, are you sure the F5 is using it's management IP, as in the IP configured on the management interface of the F5 or are you referring to it's self IP on any given interface?
CirrusFrom what I can tell the Management IP is being used. This is what I see for the pool
I created the OPENINTEGRATIONHUB Node as a FQDN, then created the Pool and added the node to it.
Thanks,
Joe
Hi Joe,
Can you try using a TCP monitor instead of an HTTPS monitor?
If the member goes up, you’ll need to examine the HTTPS monitor. You may need to send an SNI extension, and it might become necessary to use an external monitor.
If the member remains down, there is a network access issue.
Additionally, the monitor traffic runs through the management interface, but data traffic does not pass through the management interface. A reset packet is generated. You must route the server-side traffic of the relevant virtual server through the data interface. This requires a data route.
