Forum Discussion
Chris_Helms_103
Nimbostratus
NimbostratusNew to F5 - health checks
I have two pools of 3 webservers that I need to have the BigIP take in or out of service a pool at a time. My plan has been to use the health checks, similar to probes to scrape content that would change based on a database record.
http://server/healthcheck.do would return a result of one of these
a. inservice (default state & app sets record to this when value d is returned)
b. ready for out of service (SQL updates record based on schedule)
c. out of service (app sets record to this value when it get b)
d. ready for inservice (SQL updates record when replication is complete)
The BigIP would take the pool out of service if the content check returned anything other than "inservice".
Does this make sense? Is there a more elegant solution? Taking a pool out of service is to allow a backend data replication process to update the database specific to each pool. It will be managed by a MS SQL Server 2005 server.
- That's off-topic for this forum, but that would work.
Be careful to use unique strings, though, since both "inservice" and "ready for inservice" would match a recv string of "inservice". I recommend using a phrase for the recv string rather than a single word.
HTH
/deb
