Forum Discussion
Using the iapp for sharepoint:
Hi,
I have used the iApp f5.microsoft_sharepoint_2010 to configure access to a Sharepoint 2013 server and I've followed the corresponding deployment guide.
Now the health monitor does not become green. Its configuration is displayed in the screenshot. Is there an error?
From the big-ip device's command line I can connect to port 443 of the sharepoint server.
How can I track down the problem further?
Regards,
Alexander
14 Replies
- nathe
Cirrocumulus
Alexander, my first thought would be to use a basic HTTPS monitor. If this works then it points to some setting in the monitor above. Have you connected via curl using the same Send string and does this work or not?
N
- JG
Cumulonimbus
I think you need to remove the last pair of "\r\n". This pair denotes an empty line that separated http headers and body. The header for authentication using your username and passowrd must be included in the header part.
- JG
Cumulonimbus
And you need to have a receive string defined as well.
- Alexander_01_13
Nimbostratus
Resuming the actual state.
- When I execute the following from the command line of the big-ip:
I get acurl --verbose -k -i https://sharepoint.publicdomain.de/sites/test\r\nConnection: Close\r\n --ntlm -u username:password
and a whole html page. OKHTTP/1.1 200 OK - The monitor is configured as displayed in the picture:
So, where is the error in the health monitor?
Regards, Alexander
- nathe
Cirrocumulus
Just one thing - you don't necessarily need anything in the receive string so try removing this and see. If you have a blank receive string then it will accept anything it gets back. Ideally you would want a receive string to mean things are ok, e.g. HTTP/1.1 200 OK or some text that's on the page. Anyway, remove this and see. N
- When I execute the following from the command line of the big-ip:
- Alexander_01_13
Nimbostratus
It doesn't matter if I fill in the above regular expression or not. The monitor stays red anyway. Just filled it in to follow the suggestion from Jie.
- nathe
Cirrocumulus
OK, without knowing your LTM version I've tried to create the Send String I'd use for this. Do either of these work (depending on LTM version and the actual host name)?
10.2.x / 11
GET /sites/test HTTP/1.1\r\nHost: sharepoint.domain.com\r\nConnection: Close\r\n\r\n
9.4.x, 9.6.x, 10.0.x, 10.1.x
GET /sites/test HTTP/1.1\r\nHost: sharepoint.domain.com\r\nConnection: Close
- Alexander_01_13
Nimbostratus
Version is 11.4
Found some typos in my string, corrected them and the monitor is still red.
The actual connection string:
GET /sites/test HTTP/1.1\r\nHost: sharepoint.domain.de\r\nConnection: Close\r\n\r\n- mikeshimkus_111Historic F5 AccountIf this is an authenticated monitor, you should remove the Connection: Close header. The NTLM handshake will fail if LTM closes the connection in the middle of it. Also, trying using just the user name in the User Name field, instead of the UPN..."user" instead of "user@mscrmd", for example.
- nathe
Cirrocumulus
Mike, I reckon that may be it. Hopefully so. Must admit to not checking whether authentication was being set, even though it's all nicely detailed here:http://support.f5.com/kb/en-us/solutions/public/2000/100/sol2167.html
- nathe
Cirrocumulus
The syntax looks good. Perhaps it's best to refer you to this doc, if you haven't already seen it: https://devcentral.f5.com/wiki/AdvDesignConfig.TroubleshootingLtmMonitors.ashx
N
- Alexander_01_13
Nimbostratus
Turning on debugging, I get the following /var/log/bigdlog entries. The interesting part is in the middle.
What does error=5 mean?
2013-09-13 16:36:01.752568: ID 108 :(_do_ping): time to ping, now=1379082961.114839 [ addr=::ffff:172.17.37.173:443 mon=/Common/crmdemo_sp.app/crmdemo_sp_https_monitor fd=-1 pend=0 conn=0 up_intvl=30 dn_intvl=30 timeout=91 time_until_up=0 immed=0 next_ping=1379082961.070839 last_ping=1379082931.077839 deadline=1379082965.582839 snd_cnt=114 rcv_cnt=0 ] 2013-09-13 16:36:01.752594: ID 108 :(_send_active_service_ping): pinging [ addr=::ffff:172.17.37.173:443 srcaddr=none ] 2013-09-13 16:36:01.752605: ID 108 :(_connect_to_service): creating new socket (rd0) [ addr=::ffff:172.17.37.173:443 ] 2013-09-13 16:36:01.752654: ID 108 :(_connect_to_service): connect: Operation now in progress [ addr=::ffff:172.17.37.173:443 srcaddr=::ffff:172.17.17.2%0:43074 ] 2013-09-13 16:36:01.756842: ID 108 :(_main_loop): wfd selected [ addr=::ffff:172.17.37.173:443 srcaddr=::ffff:172.17.17.2%0:43074 fd=10 pend=1 conn=1 ] 2013-09-13 16:36:01.756856: ID 108 :(_send_active_service_ping): pinging [ addr=::ffff:172.17.37.173:443 srcaddr=::ffff:172.17.17.2%0:43074 ] 2013-09-13 16:36:01.756872: ID 108 :(_send_active_service_ping): writing [ addr=::ffff:172.17.37.173:443 srcaddr=::ffff:172.17.17.2%0:43074 ] send=GET /sites/test HTTP/1.1\x0d\x0aHost: sharepoint.domain.de\x0d\x0aConnection: Close\x0d\x0a\x0d\x0aAuthorization: Basic d2ViZXJhQG1zY3JtZGVtby5wcmk6ZGJkZGhrcC4x\x0d\x0a\x0d\x0a 2013-09-13 16:36:01.762803: ID 108 :(_main_loop): rfd selected [ addr=::ffff:172.17.37.173:443 srcaddr=::ffff:172.17.17.2%0:43074 fd=10 pend=0 conn=0 ] 2013-09-13 16:36:01.762827: ID 108 :(_recv_active_service_ping): reading [ addr=::ffff:172.17.37.173:443 srcaddr=::ffff:172.17.17.2%0:43074 ] 2013-09-13 16:36:01.762840: ID 108 :(_send_active_service_ping): pinging [ addr=::ffff:172.17.37.173:443 srcaddr=::ffff:172.17.17.2%0:43074 ] 2013-09-13 16:36:01.762851: ID 108 :(_send_active_service_ping): writing [ addr=::ffff:172.17.37.173:443 srcaddr=::ffff:172.17.17.2%0:43074 ] send=GET /sites/test HTTP/1.1\x0d\x0aHost: sharepoint.domain.de\x0d\x0aConnection: Close\x0d\x0a\x0d\x0aAuthorization: Basic d2ViZXJhQG1zY3JtZGVtby5wcmk6ZGJkZGhrcC4x\x0d\x0a\x0d\x0a2013-09-13 16:36:01.762895: ID 108 :SSL_write() returns -1, error=5 [ srcaddr=::ffff:172.17.17.2%0:43074 ] 2013-09-13 16:36:01.762915: ID 108 :(_ssl_shutdown_service): shutting down, return ssl false [ addr=::ffff:172.17.37.173:443 srcaddr=::ffff:172.17.17.2%0:43074 mon=/Common/crmdemo_sp.app/crmdemo_sp_https_monitor fd=10 ] 2013-09-13 16:36:01.762934: ID 108 :(_send_active_service_ping): unable to connect; giving up [ addr=::ffff:172.17.37.173:443 srcaddr=::ffff:172.17.17.2%0:43074 ]2013-09-13 16:36:01.762947: ID 108 :(_ssl_shutdown_service): shutting down, return ssl true [ addr=::ffff:172.17.37.173:443 srcaddr=::ffff:172.17.17.2%0:43074 mon=/Common/crmdemo_sp.app/crmdemo_sp_https_monitor fd=10 ] 2013-09-13 16:36:01.762966: ID 108 :(_ssl_shutdown_service): shutting down, return ssl true [ addr=::ffff:172.17.37.173:443 srcaddr=none mon=/Common/crmdemo_sp.app/crmdemo_sp_https_monitor fd=-1 ] - Alexander_01_13
Nimbostratus
Hey there,
I cannot say exactly what I have changed, but the sharepoint now is available and the problem seems to be solved.
The problem probably had to to with SSL encryption or the self-signed certificate. After I changed the binding (Port, Certificate etc.) and changed it back, unexpectedly the monitor became green.
Thanks to all for helping! I've learned a lot :-)
Regards,
Alexandner
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com