Forum Discussion
5 Replies
- SP_266134Nimbostratus
ICMP is working but not http monitor. from my desktop http: requests are resolving that means the server port 80 s not blocked and it is functioning correct. ?
- JinshuCirrus
Can you login to the F5 cmd and do a curl on http url? It should respond back with 200 OK.
curl -v http://abc.com
-Jinshu
- Daniel_EppersonEmployee
Please list the configuration in question. You mention configuring nodes to use an HTTP monitor, which could be a problem. The nodes are only an IP address, so you probably need to stick with ICMP monitor only on the node level.
Please see the configuration guide section "Monitor-to-node association" for more details on this.
- TerrenceNimbostratus
I always find the best path to verify that the F5 can indeed get to a pool member is by doing a curl from the terminal of the F5 itself. This will ensure proper routing, and will ensure that the F5 does indeed have access to the port specified. It might be taking an unexpected path, which will cause the traffic to be received from a random self ip.
From the verbose output, you should get a pretty good understanding of what is happening. Additionally because you are using the base http health monitor, rather than an HTTP/1.1 compatible one, you can see how the server will respond to the request with telnet from the F5
Again inspecting the output received from the server, it might shed some light on your issue.
- Goto_1973_36322Altocumulus
Hello, Did you find an answer? I have the same issue? Many thx