Forum Discussion
Gary_T_31565
Nimbostratus
Nimbostratushttp monitor showing node up when down.
Hi,
I don't want to log this as a support job without sense checking my understanding.
On a web server I have two sites (10.10.10.10 and 20.20.20.20). Second one is using host headers.
These are in different pools both with http monitors on.
If i stop web sites using IIS the monitors alarm and traffic is stopped to both.
If i start 20.20.20.20 the BOTH monitors go green and I get traffic to 10.10.10.10 (but with 400s, bad requests)!
Luckily I trap 4xx errors and redirect using irules.
Is this expected behaviour?
taro_112311Are two sites executed on a single process?
What are the "Send String" and the "Receive String" settings of each http monitor?
Gary_T_31565Send String GET /
Receive String
ie the default.
So I guess the the monitor just checks port 80 and IIS responds regardless on ip used?- taro_112311You might have two options, though a multi amount contains the guess because information is insufficient.
1. The process of IIS is separated for 10.10.10.10 and for 20.20.20.20.
The monitor for 10.10.10.10 will come to remain downing, if only the IIS for 20.20.20.20 starts.
2. An appropriate character string is set to "Receive String" setting as a return value such as "200 OK". - Gary -
You should define a specific Receive string containing a string unique to a successful response. Without one, the HTTP monitor will match on any response, even an error page.
The easiest way to choose a receive string for an existing page is to "View Source" on it in your browser and find a phrase that will NOT appear on any error page or response. For example, if I wanted to run an HTTP monitor against www.f5.com, I could use the phrase
which appears in the meta headers for the page. If the server responds with an error page, it won't match & the pool member will be marked down.secure, fast, and available
/deb
