Forum Discussion
Reg health Monitor
Hi folks,
when we are applying https health monitor its marking the pool member down,but when we are applying TCP_443 its not marking.
What might be the issue ? why its happening ?
Anuj
1 Reply
- Vijay_E
Cirrus
TCP_443 is just performing a 3-way handshake on port 443. HTTPS performs 3-way handshake followed by SSL handshake. If TCP_443 works, it is fair to conclude that route to the pool member exists and the pool member has port 443 listening. If HTTPS is failing, I would check to make sure if there are any issues with the cert utilized.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com