06-19-2009 05:53 PM
Dear all,
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.
Solved! Go to Solution.
06-22-2009 12:37 AM
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.
Gilles.
06-22-2009 12:37 AM
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.
Gilles.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide