Forum Discussion
codyjohn
Nimbostratus
NimbostratusReference a pool name inside of an associated external monitor?
We have many similar pools, one per customer, with different ip:port combinations assigned to each of them. The pools are each named with a unique identifier for each customer, something like:
...
kunjan_118660
Cumulonimbus
CumulonimbusHow about using RestAPI to list the members in each pool_${customer}? Then loop thru the members in each pool using curl to fetch page and check for the customer string.
codyjohnAre you suggesting we have an external script that performs this? If so, how would we then mark a node as down if we don't find "${customer}" in the curl payload? Another API call? We are trying to implement a failsafe mechanism to ensure that the application server and the F5 are in agreement on what customer instance should be served by a particular ip:port combination, and that we never have an app node in the wrong customer pool. We have thousands of pools per F5 pair and want to figure out a simple and native (if possible) solution that can catch stuff quickly.
