Perry_71428
Mar 11, 2010Nimbostratus
F5 Monitor Issue
Hi
All our websites are managed in a standard F5 Virtual Server / Pool / Node way.
We have health monitors running against the pools and nodes. These are set to run every 5 seconds. These are simple tcp port 80 monitors. They are not HTTP GETs.
When our website receives a new session request, it creates a session record in our database for later analysis, storing the ip of the request from the http x-forwarded-for attribute passed in by the F5.
Amongst the real traffic, I am seeing database records being created from the internal ip's of our F5 units every 5 seconds indicating that somewhere, the F5 itself is actually making calls direct to our website.
This must be coming from a monitor but for the life of me I cannot find the culprit.
Every pool is a simple TCP port 80 monitor and every node is a simple icmp monitor.
There is another monitor set up, lets call it monitorA, which does do a website GET which says it has some instances attached but when I review the pools & nodes listed, none of them list the monitorA as a healthcheck.
I have disabled these monitor instances, but still these records are being created in our database by our website. I cannot delete the monitor due to the instances existing.
Is this a case where the F5 needs to be rebooted to clear itself, as I cannot work out where these calls to the website are coming from.
Any ideas?
Thanks