Hi,I have two Big IP F5 in HA Active/Standby state. I have configured the internal interface of Big IP as follows,Big IP 1 : 10.10.10.2 (Non-floating)Big IP 2: 10.10.10.3 (Non-floating)Floating IP: 10.10.10.1I have configured a node for one application and applied health monitor(https).So which IP will initiate the health monitor for that node? Non floating IP or the Floating IP?In my case I see that the health monitoring traffic is initiated from the Non Floating IP i.e. from 10.10.10.2 and 10.10.10.3. Health monitoring traffic is not being initiated from the Floating IP i.e 10.10.10.1.Since the device are in HA the health monitoring traffic for nodes should be initiated from the Floating IP and not from the Non-floating IP, I guess.Am I missing something in HA configuration or is this the expected behaviour?

this is how it works. both nodes have to be able to determine for themselves if a poolmember is reachable. it makes sense to always use the non floating for this. else the health monitor IP would change with a failover.

Which IP initiates health monitoring of nodes when F5 are in HA?

Forum Discussion

Forum Discussion

SSO Login Update Coming to DevCentral

Kevin - June 2026 Featured F5er

Tyler - May 2026 Featured Member

Recent Discussions

UCS file migration on differing OS versions

qkview: revealing pool members & pools

ASM attack signatures not syncing between active and standby F5

Query on source IP preservation for syslog traffic through F5 virtual server

Hardware BIG-IP appliance reach EOSS, but the software version running on it not yet?

Related Content

F5 Insight for ADSP – Initial Setup in VMware

F5 Distributed Cloud - Regional Edge Health Monitoring Insights

Simplifying Application Health Monitoring with F5 BIG-IP

Proxy Protocol v2 Initiator

iRule based RADIUS Health Monitor Builder