Unable to connect when health checks http or https request from loadbalancer to the Policy Server
search cancel

Unable to connect when health checks http or https request from loadbalancer to the Policy Server

book

Article ID: 431091

calendar_today

Updated On:

Products

SITEMINDER CA Single Sign-On

Issue/Introduction

Running Policy Server and trying to implement health check.

When trying to access the Policy Server at port 80 (http) or 443 (https), then the browser returns "Unable to connect" error message.

Trying to reach it using a browser at port 44444 or 44443, the browser shows the "The connection was reset" error message.

What are the officially supported mechanisms to implement an advanced or functional health check for Policy Server beyond simple TCP port verification?

Resolution

DX O2 is the tool to go to get a full monitoring of the SiteMinder environment, and more.

The simple TCP port verification is discouraged, it's not an officially supported mechanism, as it can lead to issues (1).

There are other official tools for monitoring such as SNMP, SNMP alerts, and OneView monitor (2).

Note also that the Policy Server doesn't use HTTP/HTTPS, but a proprietary protocol.

Broadcom offers an integrated monitoring system called DX O2 that goes far beyond detecting the service availability.

DX O2 allows as well to quickly identify the Web Agent with the application it protects (3).

DX O2 can be used to monitor databases, clouds, containers, virtualization, and many more (4)(5)(6).

Additional Information

  1. Policy Server health checks support from a load balancer

  2. Performance metrics monitoring tools for Policy Server and Agents

  3. Observability for SiteMinder

  4. Monitoring

  5. SiteMinder

  6. SiteMinder Dashboards