Forum Discussion
charlestips_149
Nimbostratus
NimbostratusMonitors for Redudant Servers
I have an environment which has an external IP which routes through the F5 to two internal IPs 192.168.220.18 and 192.168.220.19 which is two different servers, a redundant pair.
I have an http monitor on the pool so that in theory if .18 becomes unresponsive it fails to the .19 server but this is not working.
Any ideas?
- The_BhattmanThis entirely depends on what you have used in your http monitor. Have you tried scaling the monitor back to TCP Health check to see if it can at least detect the port.
CB 
charlestips_149The problem is that is is not failing over, it sees both and they can work independently but when one fails it does not failover to the second.- charlestips_149One way of resolving this that I can think of is that we have put an html file on each of the servers in the redundant pair that gives a different result, like if you go to /webserver.html on one it says 08 and the other says 09.
Can this be used to create a monitor for failover to the other server in the redundant pair? - charlestips_149Actually, I did it with a host header monitor based on a file we have on the servers.
GET /page.htm HTTP/1.1\r\nHost: preproduction.sureclosetm.com\r\nConnection: close\r\n\r\n
Then set the receive string to the result I get from page.htm
The http monitor works great, just gotta figure out how to make one for https... 
hoolioCirrostratus
The HTTPS monitor should be the same exact send/receive strings if that page exists on the HTTPS instance. Just use a parent monitor of HTTPS instead of HTTP.
Aaron
