Forum Discussion
CirrusFQDN Node Configuration
We have always used IP address for Node creation, but have a new need to deploy a FQDN node on our LTM's.
I created it and noticed that an auto generated node was created with an IP address from DNS within the Common Partition as well as the one I created. I see that one that was created is Green but the one in the Common is monitor failed, therefore the Pool is down. I created a specific https monitor and applied it to the pool (also tried the https one from Common) but neither worked. Our logging shows that the F5 is reaching out to the node IP address via the management IP, is this expected? Again this is my first time using FQDN for a node and I am confused on the results/behavior that I am seeing. Any assistance or guidance would be greatly appreciated.
Thanks,
Joe
2 Replies
- Paulius
MVP
First, 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?
jomedusaFrom 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
