Forum Discussion
GTM not detecting the service as up.
- Aug 29, 2019
You can't just have anything as the Prober Pool Member. It has to be the server for the GTM. Do these steps exactly:
- Create Server for the GTM. So the device that you sent this screenshot from, we'll pretend it's called f5gtm1.com. You'd create a server named f5gtm1. This server will be BIG-IP System (Single). You need to give it an Address, Translation, and Data Center. Leave Virtual Server Discover Disabled.
- Then create Prober Pool.
This could be due to a large number of reasons... Two of the more common reasons are:
- Port TCP 4353 is blocked on a Firewall from the GTM Self IP to the IP of the remote device
- Remote device's Device Certificate hasn't been imported on the GTM under DNS > GSLB > Servers > Trusted Server Certificates
You should see some error logs in System > Logs > GSLB that will point you in the right direction
Thanks Dan!!
port TCP 4353, I believe is the iQuery port which we should not be concerned here about. The reason is that all we are doing is adding Generic hosts to this DNS.
In System -> Logs --> GSLB we are not able to see any logs.
I do feel that there is some basic steps that we have not setup, just not able to understand what else could be needed.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com