Forum Discussion
Question Regarding BIG-IP GSLB Prober Pool Behavior
I'm experiencing an issue with BIG-IP GSLB and would appreciate any insights from the community.
I have two data centers that are part of a synchronization group. Within this group, there's a Prober pool set up with a round-robin strategy, which includes two members: gtm1 and gtm2, each belonging to one of the data centers. A virtual service is referencing this Prober pool.
While analyzing the traffic on gtm1 by capturing packets, I noticed that I'm also able to capture packets sent from gtm2 to the monitor's destination IP in gtm1 device. Is this behavior due to some specific mechanism within BIG-IP GSLB, or it just indicate a misconfiguration in my network setup?
Any advice or explanations would be greatly appreciated.
Thank you in advance for your assistance.
1 Reply
Take a look at this description: https://my.f5.com/manage/s/article/K08433560
I think you are seeing the prober traffic because you have created a prober pool, by default it will by itself decide which device to choose to do the probing.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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