Forum Discussion
Why cant a simple monitor (icmp, tcp-echo) be associated with a pool ?
Hello Mates,
I was reading across few docs and came to know simple monitors like (icmp) can not be associated with a pool, tried to understand why it can not be associated but no luck .
Please help
Regards, Sam
1 Reply
- StephanManthey
Nacreous
Hi Sam,
what documents you are referencing?
Only gateway_icmp can be assigned on pool level.
ICMP, TCP_ECHO and GATEWAY_ICMP monitors are service independent and don´t expect a listening service on the poolmember.
In case you have your poolmembers configured for port "0", you will need customized monitors with an alias port to be assigned to the pool. In case your poolmembers are configured with a fixed service port, you can use i.e. the build-in tcp, tcp_half_open, http, https monitors in default configuration. Their alias is set to "*" and they will be mapped according to pool member settings.
Thanks, Stephan
Edited: Thanks to Timo (+1) for correcting my mistake!
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