Healthcheck Monitor for Sharepoint

What about a request for the page that the client is redirected to after the request to /? Also, it would be good to use an HTTP 1.1 formatted request so you can tell the web server that you won't be trying to re-use the TCP connection:

 

 

GET /default.aspx HTTP1.1\r\nHost: \r\nConnection: Close\r\n

 

 

The receive string could be 200 OK if the site doesn't require authentication for the default page. If the site requires authentication it gets a little more complicated. You could just check for a 401 response, but this doesn't tell you if the app is down and the web server is up. You can configure a stock HTTP monitor to use basic auth. But for NTLM you would need to use an external scripted monitor.

 

 

Aaron

My self also facing issues

 

Below is moniotr configurated on F5--

 

 

monitor mon_sharepooint_80 {

 

defaults from http

 

recv "pong"

 

send "GET /ping.html HTTP/1.1\nHost: sharepoint.xxx.com\nConnection: Close\n\n"

 

}

 

 

When i checked manullay from F5 getting error as "HTTP/1.1 401 Unauthorized" even tested provind useename &password on F5 monitor but still seeing sma issue.

 

 

PLease let us know how to resolve the issue

My self also facing issues

 

Below is moniotr configurated on F5--

 

 

monitor mon_sharepooint_80 {

 

defaults from http

 

recv "pong"

 

send "GET /ping.html HTTP/1.1\nHost: sharepoint.xxx.com\nConnection: Close\n\n"

 

}

 

 

When i checked manullay from F5 getting error as "HTTP/1.1 401 Unauthorized" even tested provind useename &password on F5 monitor but still seeing sma issue.

 

 

PLease let us know how to resolve the issue

We recently ran into a similar request to create a more intelligent health monitor which looks for a string of text from within sharepoint that required NTLM authentication. Here are a couple of items that might help depending on which version of F5 you are running. If you are running v11.1 or later the out-of-the-box HTTP monitors now support NTLM authentication so I would recommend that. If you are running something a little older, you may need to create a custom external monitor and leverage CURL so I have included a sample for it as well.

 

 

Notes:

 

1) X-FORMS_BASED_AUTH_ACCEPTED: f -- found to be required for Sharepoint after reading http://msdn.microsoft.com/en-us/library/hh124553%28v=office.14%29.aspx

 

2) username testuser@mydomain.com instead of the \testuser as suggested in http://support.f5.com/kb/en-us/solutions/public/2000/100/sol2167.html as the latter resulted in our test account becoming locked out

 

 

ltm monitor http sharepoint-NTLM {

 

defaults-from http

 

destination *:*

 

interval 30

 

password "Password01"

 

recv MyTestText

 

send "GET /portal/Pages/default.aspx HTTP/1.1\\r\\nX-FORMS_BASED_AUTH_ACCEPTED: f\\r\\nHost: sharepoint.mydomain.com"

 

time-until-up 0

 

timeout 91

 

username testuser@mydomain.com

 

}

 

 

 

Curl Samples that show how to test individual node IPs for a sharepoint site using Host-Headers:

 

curl --ntlm -k -v --header "X-FORMS_BASED_AUTH_ACCEPTED: f" --user 'testuser@mydomain.com:!Password01' http://10.10.10.10:80/portal/Pages/default.aspx -H "Host: sharepoint.mydomain.com"

 

 

curl --ntlm -k -v --header "X-FORMS_BASED_AUTH_ACCEPTED: f" --user 'testuser@mydomain.com:!Password01' http://10.10.10.11:80/portal/Pages/default.aspx -H "Host: sharepoint.mydomain.com"