Forum Discussion
GTM Prober pools monitoring
Hi, I have three GTMs all throught the world. There are two in Australia and one in USA. I have setup my datacenters and prober pools. The USA DC uses the USA GTM in the prober pool.
I'm seeing in my GTM logs that for some pool members in USA, the Australia GTM will mark a pool member as down as though it is monitoring the USA member.
For example:
Pool /Common/mypool.com member 202_2_xxx_xxx-80 (ip:port=202.2.xxx.xxx:80) state change green --> red ( Monitor/Common/tcp from 103.7.xxx.xxx : state: timeout)
SO here, pool member 202.2.xxx.xxx is a server in the USA. 103.7.xxx.xxx is a GTM in Australia.
Why does the GTM in australia mark this pool member down? It shouldn't even be monitoring this pool as my prober pool is set to use only the USA GTM for devices in the USA DC.
Any thoughts here?
- JPV_131616Cirrus
are you using a sync group between all gtms?
all devices would monitor I would imagine in that case, as they need to know the status from everywhere to operate properly... what if one gtm goes down??... the other theoretical dns servers need to also respond with correct status ideally...
cheers
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