Forum Discussion
Nimbostratusdefault https monitor vs custom https monitor on port 443.
Folks, would there be any difference when you use the F5 default https monitor vs a custom https monitor on port 443? We see that with the default https monitor the nodes moves status from up to down every 30 mins.
A custom https monitor on port 443 works fine.
3 Replies
Lee_SutcliffeNacreous
Well that depends - how customised is you monitor? I'd also be more concerned why the monitor is marking the pool member down. Rather than finding a monitor that makes things look ok, I would want to know why the default monitor marks it down. If you monitors are making something up which in actual fact are down, you're going to be sending clients to potentially failed pool members.
JGCumulonimbus
The default monitor uses HTTP/0.9, which is not supported by most applications nowadays.
Please post the content of your custom monitor.
I agree with MrPlastic, since the issue intermittent then default monitor seems works for you. You need to find out why the monitor is failing. Run the packet capture against suspected pool member during issue time and see the packet flow.
