Forum Discussion
How to verify HTTPS monitor via CLI with version 10.x and Route Domains
I sometimes have the requirement to verify the reason of a red HTTPS monitor via CLI.
I know already this command:
openssl s_client -connect :443
But this doesn't seem to work correctly with Route Domains. Since version 11.x I know the two commands rdsh and rdexec, but this is not possible in version 10.x. If I try it with the following command:
openssl s_client -connect 2620:0000:0C10:F501:0000:0008:8A23:C0E0:443
I'm getting this error:
getaddrinfo: Servname not supported for ai_socktype
connect:errno=0
Any idea how I can easily verify the response of my configured HTTPS-request to verify what's the issue of the red monitor?
Thank you!
Ciao Stefan 🙂
Curl works with route domains in v10. openssl my work also... I format my IPv6 address differently.
curl -vk https://2620:0000:0C10:F501:0000:000$rd:$node_ipThis example uses RD 1 with ip 10.10.10.10
curl -vk https://2620:0000:0C10:F501:0000:0001:10.10.10.10
2 Replies
- joek_44162
Altostratus
Curl works with route domains in v10. openssl my work also... I format my IPv6 address differently.
curl -vk https://2620:0000:0C10:F501:0000:000$rd:$node_ipThis example uses RD 1 with ip 10.10.10.10
curl -vk https://2620:0000:0C10:F501:0000:0001:10.10.10.10 - Stefan_Klotz
Cumulonimbus
Hi Joek,
thank you very much, that's working!!! Also nice to know, that it's possible to easily append the original IPv4 address within the IPv6 notation.
Ciao Stefan :)
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