HTTP Health Monitor in Receive Strings with Regular Expressions
Hello Community, I need to monitor http servers with regular expressions in the http receive strings. If receive string exact match with "Healthy" word then F5 send the requests to the servers. list ltm monitor http Healthy { adaptive disabled defaults-from http destination 10.0.1.20:http interval 5 ip-dscp 0 recv \bHealthy\b recv-disable none send "GET / HTTP/1.1\r\nHost: 10.0.1.20\r\nConnection: Close\r\n\r\n" time-until-up 0 timeout 16 } Server up and running and regex is fine but pool members are down. I need some help in this topic. Thank You / Best Regards
Monitor question: 302 after login on Solarwinds Orion
I'm trying to write a health monitor (LTM 11.4.1 HF2) for the Solarwinds Orion web interface where I'm passing login credentials in the URI portion of the GET which looks like this: GET /Orion/Login.aspx?AccountID=username&Password=password Upon success of that, the IIS server sends back a 302 redirecting to another URI (/Orion/SummaryView.aspx?ViewID=1). My health monitor doesn't seem to work no matter what receive string I look for. If I have it look for content in the second URI, it fails. If I have it look for "Object moved" in the first URI, it fails. My send string looks like this: GET /Orion/Login.aspx?AccountID=username&Password=password HTTP/1.1\nHost: hostname.fqdn\r\nConnection: close\r\n\r\n If anyone has any experience with Solarwinds (or similar 302 redirects after login) send and receive string monitors, I'd certainly appreciate any pointers. Thanks in advance, RoyDoes tcp wait recycle function on disabled pool nodes?
Hi, I have some app devs who are taking down their nodes automatically when deploying new code. The idea is they take a node down, verify no connections to the server, deploy code and bring the node up. Rinse and repeat for each node in the LTM pool. They're running into prolonged connections after disabling the pool node. We've tried setting action on service down to "Reselect", but that doesn't seem to work. No persistence is used on the VIP but connections continue to persist to the disabled node. The one thing I'm assuming but haven't been able to backup with credible confirmation is that the TCP profile using tcp wait recycle isn't a culprit. I'm assuming that the F5 won't recycle connections in a time-wait state if the node is in a disabled state, but I don't see any documentation stating this is the case. Am I correct in my assumption? Or can the tcp wait recycle need to be disabled for this to work properly so that the F5 is keeping a connection open allowing new connections to reuse a connection that was in time-wait? I'm assuming the client or server is keeping this connection open, but want to make sure this isn't the F5 somehow responsible for keeping the connection open.
Prevent HTTP monitor from sending TCP RST when receive string arrives
I learned something today! I never knew that HTTP monitors may send a TCP RST as soon as they see the receive string they're watching for. See: https://support.f5.com/kb/en-us/solutions/public/9000/800/sol9812.html Unfortunately, a couple of our real servers do copious logging when that happens, and the application team would like to prevent that behavior. Is there any way to cause the HTTP monitor to always read to completion the response? I don't want to keep-alive/pipeline (even if that's possible with a monitor - sounds counterintuitive) because I want each call's success/failure to be a reflection of what a new client connection would encounter. thx!
