Forum Discussion
adithyodw_18563
Nimbostratus
NimbostratusF5 Pool Members flapping issue
Dear All,
We are facing issue with monitoring of nodes in one of our virtual server pool, however when we check on the server side we didn’t found any discrepancy on server port side. Due to thi...
adithyodw_18563Nimbostratus
NimbostratusHi gagan, based on gui, im using tcp for health monitors for 44070, so i must change it to gateway_icmp? and why? thank you
Shaun_Simmons1Altostratus
ICMP can be used to quick-check the path to the server(s) are good. I use it when I know I have the LTM configured correctly but don't know if the network or server may be the issue.- adithyodw_18563hi gagan, based on gui 10.64.32.16 using monitoring icmp. should i change?
GaganD_191239If node is using icmp as its health check at node level then you don't need to change. But if its using tcp to monitor node at node level then yes please change it to icmp. ICMP is good enough health monitor at node level, all fancy monitors should be used at pool level to monitor health of application. Since by default tcp(or all health monitors in fact) does not specify destination port in the monitor config(its usually set to wildcard), it does not know which port to monitor, But when it is assigned to pool which has member listening to specific port(like 10.64.32.16:44070) in you case, it take the port number (44070) from pool member and use it in its monitoring. So it know what port to monitor. But when you assign the same monitor tcp to a node, which has no port number specified(and you actually cannot specify it), monitor does not know which port to monitor, so it can cause to problems.
