health check
6 TopicsHTTP health check: Manual GET result versus what's seen in Fiddler
Scenario: Replace the generic http health check to a menu page with something specific. The issue is the page in question redirects to a login page on a different site before returning to (and actually displaying) that menu page. Using Fiddler I can see the html of the initial page before it redirects, however when I manually send a GET from the F5 for it I receive a '200 OK" along with <title>Page Not Found</title>. I was expecting to get back the same html I see in Fiddler. Is this due to the redirect futzing with the GET request? Has anyone run into this situation before? Thanks! Note: This is the GET I'm using: GET /pls/prod/twbkwbis.P_GenMenu?name=bmenu.P_MainMnu\r\nConnection: Close\r\n\r\n375Views0likes1CommentStumped by regular expression
Requirement: build a health Check to send an api url call to server and parse the return value for key indicators. URL: rldimedas1.tcbna.net/rest/apigateway/health/all Crafted Send String: GET /rest/apigateway/health/all HTTP/1.1\r\nHost: rldimedas1.tcbna.net\r\nConnection: Close\r\n\r\n User name and password required: DEVF5Inside / <password> Expected return to be parsed: { "status": "green", "elasticsearch": { "cluster_name": "DEV_EventDataStore", "status": "green", "number_of_nodes": "2", "number_of_data_nodes": "2", "timed_out": "false", "active_shards": "388", "initializing_shards": "0", "unassigned_shards": "0", "task_max_waiting_in_queue_millis": "0", "port_9240": "ok", "response_time_ms": "16" }, "is": { "status": "green", "diskspace": { "status": "up", "free": "99419619328", "inuse": "152539549696", "threshold": "25195916902", "total": "251959169024" }, "memory": { "status": "up", "freemem": "2668806528", "maxmem": "3817865216", "threshold": "368102604", "totalmem": "3681026048" }, "servicethread": { "status": "up", "avail": "286", "inuse": "14", "max": "300", "threshold": "30" }, "response_time_ms": "103" }, "terracotta": { "status": "green", "nodes": "2", "healthy_nodes": "2", "response_time_ms": "67" } } 3 Key Indicators of healthy Services: #1 "elasticsearch": { "cluster_name": "DEV_EventDataStore", "status": "green", #2 "is": { "status": "green", #3 "terracotta": { "status": "green", I would think it was possible to craft the received string parse to check for all 2 key indicators so I do not have to create 3 separate health checks. I have tried just checking for the first indication by following suggestion in DevCentral but is did not work: \"elasticsearch\": \{\"cluster_name\": \"DEV_EventDataStore\",\"status\": \"green\", This solution is complicated by all 3 indicators being the same syntax: "status": "green" I think there might be an issue with my GET string as well because the Monitor log only shows "200 OK" as the response from the server. When I change the receive string to only elasticsearch, it passes. Any Help Here?759Views0likes4CommentsF5 health check logs no response or bad response
Hello Guys, Would like to ask regarding the health check. so we have client wanted to know if our node wasnt able to reply or it did reply but a bad response. so this is the logs sample: 01070638:5: Pool /Common/ member /Common/server_name:443 monitor status down. [ /Common/: down; last error: /Common/: Unable to connect; No successful responses received before deadline. @2016/12/01 09:58:35. ] [ was up for 22hrs:39mins:24sec ] Thanks!837Views0likes1CommentF5 equivalent of Alteon's buddy helthchecks
Hi all, I'm in the process of migrating old Radware Alteon load balancers onto F5 kit. On the Alteons they have what's known as a "buddy health check". Basically what it does is monitor a second node, and if that goes down then the first node is marked as down too. For example, Server A is configured to have Server B as its buddy. If the health check for Server B fails, the load balancer will mark Server A as down. I'm aware this could be done using Priority Group Activation, however in this case Server A is being health checked on port 3000 whilst Server B is health checked on port 3001. Data for both is on port 7021. Is this setup achievable on an F5? Thanks!460Views0likes1CommentSharepoint HealthCheck not working
Hi, recently we updated our SP2010-Farm to SP2013 and our monitors stopped working. The monitors were http-monitors with the send string: GET /pages/default.aspx HTTP/1.1\r\nHost: \r\nConnection: Close\r\n\r\n The expected receive string was set to "X-SharePointHealthScore:", since this is something that only a running SP service would return. Now, since the upgrade we had to degrade all our monitors to normal tcp on port 443, but we would like to have these old monitors back in place. From the F5, it is possible to telnet to the node 10.10.10.101 via 443, but the GET-request from the monitor doesn't return anything and times out. But when I try curl, it seems to work: " curl -v -k -H "Host: ; https://10.10.10.101 " It returns the SSL-information etc. and also the SP-Parameters, which also contain the "X-SharepointHealthScore", which we are looking for. One thing that is to be mentioned is, that the server is using a self-signed certificate. Curl says "* SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed" But I'm not sure if this is just an issue of curl, or could this cause also the problems with the monitor? Also - normal traffic is working properly, with the F5 talking to the servers in the back end via HTTPS. Any idea is welcome :)214Views0likes1Comment