Difference between revisions of "Using cURL to troubleshoot monitors"
From Tech-Wiki
| Line 22: | Line 22: | ||
-h for help | -h for help | ||
-v for verbosity | -v for verbosity | ||
| + | |||
| + | If different partitions are used, you might need to change the routing domain: | ||
| + | rdexec <route domain id> | ||
==External links== | ==External links== | ||
* [https://support.f5.com/csp/article/K12531 K12531: Troubleshooting health monitors] | * [https://support.f5.com/csp/article/K12531 K12531: Troubleshooting health monitors] | ||
* [https://support.f5.com/csp/article/K15408 K15408: Troubleshooting BIG-IP GTM monitors] | * [https://support.f5.com/csp/article/K15408 K15408: Troubleshooting BIG-IP GTM monitors] | ||
| + | * [https://support.f5.com/csp/article/K13472?sr=33700626 Userland applications in non-default route domains] | ||
Revision as of 13:43, 7 February 2019
cURL is a very useful tool when testing monitors
Example syntax for HTTP:
curl http://[ip][port]/[...]
Example syntax for HTTPS:
curl -k https://[ip][port]/[...] -k to ignore certificate issues
Example to pass a host header
curl --header 'Host: [host]' [METHOD]://[ip][port]/[...]
Additional useful option
-h for help -v for verbosity
If different partitions are used, you might need to change the routing domain:
rdexec <route domain id>