SEPM Monitor to verify Mgmgt Server is Available
We set up a monitor in F5 global traffic manager (DNS) load balancer so that if one of our SEPM servers has an issue where it cannot deliver updates to the SEP clients, the load-balancer won't hand out that server's IP in DNS responses.
I set up the following health monitor in the F5 load balancer:
The above URL returns an HTTP 400 Bad Request error. The above URL is listed in the SEP11 Administration Guid in the Troubleshooting communication problems section.
Next I set up the following health monitor::8014/reporting/index.php">
This URL does return a login page for reporting. However, I am told by our server mgmt team that this login page continues to successfully return even when the SEPM service is disabled on the server.
My question is this:
What URL or other "object" is the best indicator that the SEP and it's services are up and avilable so the clients will be able to get their AV and Firewall policy updates?
I see the clients heartbeat to the first URL and so this URL seems to be the best candidate to use as the health check in the load-balancer. Is this the best one, or is there some other check that can be made to verify that clients can connect and they can successfully retrieve content updates? If this is the best URL to check, then why does it not work as specified in the Admin guide? Are there any other health checks (URLs) I can try, such as the POSTs that appear to be register transactions when new clients connect to the SEPM?
Our server mgmt team thinks we need to set up a dual monitor, one to check that clients can connect to the IIS web service running on TCP port 8014, and one to check that the TOMCat web server is running on TCP port 8443. I would prefer a single health check that is the most appropriate.