Forum Discussion
kgaigl
Cirrocumulus
CirrocumulusLTM Monitor ServicePort
Hello, we've som new Pools with https-monitors (get some Pingservlet), and if I let the "Alias Service Port" unchanged, the Monitor fails. If I set the Port to the same Port as the Poolmember are s...
Kai_Wilke
MVP
MVPHi kgaigl,
When you create a Pool Member, you can set it ports to "* All Services".
In this case, the Pool-Member will inherit the DST port of the VS when forwarding to it. The VS could also be set to * All Services, which would allow you to setup a VS-many-to-many-Pool port mapping.
When working with such * All Services rule sets, then you have to keep in mind that the Health-Monitor wont know which port to monitor, so you have to specify a port at the Monitor-Level.
Only if you have specified a Port at your Pool-Member, the monitor will become able to inherit the Port of the Pool-Member via the default "* All services" option.
Cheers, Kai
kgaiglCirrocumulus
Cirrocumulus
Kai_Wilke wrote:Only if you have specified a Port at your Pool-Member, the monitor will become able to inherit the Port of the Pool-Member via the default "* All services" option.
Ok Thank you, but this last sentence is my Problem, I think this has worked all the time, and with new pool not
But to be sure I set the Alias Port, otherwise I could use same Monitor for different Pools
btw: version is 16.1.3.1
- Kai_Wilke
Did you set the Port on the pool level? And does the monitor not inherit its settings? Did you double checked your configuration?
Cheers, Kai