F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

Sdutt_328171's avatar
Sdutt_328171
Icon for Nimbostratus rankNimbostratus
Nov 10, 2017

Self-IP from all F5 guests are sending GET requests to the web servers.

I have been working on an issue where pool members (web servers on port 80) is getting GET and HEAD messages from the self-IPs from a cluster and from floating IP. Even after I changed the Health Mon...
application delivery
LTM
Hannes_Rapp's avatar
Hannes_Rapp
Icon for Nimbostratus rankNimbostratus
Nov 10, 2017

500 per 10 seconds is not realistic. That would be 0.02 second interval in between the HTTP health check requests to a single pool member. Interval this short would cause each pool member to flip available/unavailable even in ideal LAN conditions.

 

What you're seeing is not traffic that originates from F5 BigIP. It's traffic that F5 sends to pool members after normal balancing/routing procedure. That traffic originates from elsewhere. Is one or more of your Virtual Servers configured to use SNAT automap or SNAT Pool feature? That would explain a packet capture and/or server logs where BigIP's SelfIP is seen as the client.