Forum Discussion
Kai_Wilke
Mar 15, 2019MVP
Hi Cathy,
if the problem persists, you may check the connectivity of the individual nodes via
curl
.
curl -vk https://172.217.168.227/
... combine the
curl
command with rdexec $rd_id
if the the backend system is only reachable via a given route domain.
rdexec 1 curl -vk https://172.217.168.227/
... if you need to perform a forensic analysis for your given case. Then "Unable to connect - for whatever reason" is all you can say to your client.
You would need to enable "Monitor Logging" for the LTM monitors to get much more detailed information. But keep in mind that "Monitor Logging" have to become enabled on each LTM cluster unit seperately and must be re-enabled after each reboot of your units...
K12531: Troubleshooting health monitors
https://support.f5.com/csp/article/K12531
Cheers, Kai