Forum Discussion
SP_266134
Nimbostratus
NimbostratusF5 Pool monitors http traffic and node Offline (Enabled) - Pool member has been marked down by a monitor
Guys,
I have configured to nodes to have a http monitor. I can access the default port 80 http application form the server and also from my client. The moment I add these nodes to the pool. I don’t s...
TerrenceNimbostratus
NimbostratusI 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.
>tracepath -nn {ipaddress} The first entry will in most cases be the selfip in which monitor traffic will be originating from >curl -vv {ipaddress}
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
>telnet {ipaddress} 80 GET /
Again inspecting the output received from the server, it might shed some light on your issue.
