Forum Discussion
L4L7_53191
Jun 12, 2009Nimbostratus
Matt: there could be a bunch of stuff affecting your health monitors. You mention that you're new to the f5 world, so I'll walk through some steps that may (hopefully) help you track it down. This is all done via the command line on your BigIP, since the BigIP is the client for health checks.
1) Ensure basic connectivity via ping.
2) If basic connectivity is good, telnet to your server port you defined for your pool members. For example, let's say I've got a server (192.168.100.10) listening on port 8080 and I want to be sure we're talking ok:
config telnet 192.168.100.10 8080
Trying 192.168.100.10...
Connected to 192.168.100.10.
Escape character is '^]'.
If you connect, you'll see something like the output above. If you do, this is a good sign - the server is listening on the port you've configured in the pool. Now type "GET" and hit enter two times. Hopefully you'll see output.
If all of this works, you're getting close so don't give up!
For more (and higher quality) information on tracking this type of issue down refer to SOL3224 on ask.f5.com. Pay particular attention to their note about HTTP version mismatch, which I've run into dozens of times over the years.
-Matt