Our F5 checks the health.php page for a 200 status code. When a server has a credential manager down we are still sending traffic via the F5 to that server since health.php is still sending a 200. Is there a manual way to turn-off the health check? Or is there a more elegant way to deal with a server with credential manager down?
Hi John, when you say "Credential Manager down”, does that refer to the credential management database showing as inactive on the PAM Clustering page? Do users have a problem when they get redirected to one of these nodes? They should still work, any credential requests on them should be processed by a node with an active Credential Management database.