For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

anto1_213321's avatar
anto1_213321
Icon for Nimbostratus rankNimbostratus
Jul 29, 2015

health monitor issue

Hi all   We modified the health monitor option on a per-node basis, from default to None, for 10.10.7.100. A few minutes later, the active unit stated that a completely different node (other vlan,...
application delivery
LTM
TMOS
TMSH
Ed_Summers's avatar
Ed_Summers
Icon for Nimbostratus rankNimbostratus
Aug 06, 2015
I'm not really offering more than echoing Patrik's thoughts. The provided log indicates the node was marked down by a failure from an ICMP monitor. Your implementation may have changed, but default for the monitor is a 16-second timeout. Four minutes would be unusually long for an ICMP monitor timeout though verification of the monitor settings would confirm the timeout. Unless you have evidence or reason to suspect they are linked I'd agree they are unrelated to the monitor change you made.