A typical http probe is configured on an active serverfarm but somehow the probe is failing.
Upon investigation (show probe <> detail)..it is found out that the http probe is not just interogating port 80 but also port 443 on the rservers. This is very strange as port 443 was not configured in anyway (would have configure another https probe for it if it is needed..... but it's not)
Config and observation are as attached.
Any feedback is welcome.
The appliance has the port inheritance functionality.
So, it will try to auto-detect the port when none are configured under the probe itself.
You probably use yout serverfarm under a policy with a class-map listening to port 443.
The solution is to configure the port under the probe itself.