Health monitor to mark pool member up when a ping FAILS (inverse ping health check)

Thanks for the response.

Are you saying that I should create the above script in a separate file as /usr/bin/monitors/custom_monitor.bash instead of uploading it as a custom monitor in the file section? If so, how do I call it then, and is the argument that I specify in the external monitor the IP address to ping? I want to ping a totally external address to see if it responds-NOT ping the actual pool member itself.

The reason for this is that I only want the pool/VS to be active if the external IP stops responding to ping, because that IP is tied to a remote site, and this VS needs to become active for that site if the IP stops responding.

I'm still a bit confused-when I run my script manually, I get no script output unless the IP does not to ping-that to me means what you said-that the monitor should be marked as down as long as the IP responds as there is no output.