"User-Agent: Mozilla" - no defaults) EXITSTATUS (set to 0 to make the monitor always mark te pool members as up it's fairly useless, but hey.
#F5 https vpn monitor code
defaults to 'GET') URI ("the part after the hostname" - defaults to '/') HTTPSTATUS (the status code you want to receive from the server - defaults to '200') HOSTNAME (the hostname to be used for SNI and the Host Header - defaults to the IP of the node being targetted) TARGETIP and TARGETPORT (same functionality as the 'alias' fields in the original monitors - defaults to the IP of the node being targetted and port 443) DEBUG (set to 0 for nothing, set to 1 for logs in /var/log/ltm - defaults to '0') RECEIVESTRING (the string that needs to be present in the server response - default is empty, so not checked) HEADERX (replace the X by a number between 1 and 50, the value for this is a valid HTTP header line, i.e. Add the monitor to a pool and you are good to go. Add your specific variables (explanation below). Create a monitor of type 'External' and select the script from the picklist under 'External Program'. Import it under 'System' > 'File Management' > 'External Monitor Program File List'.
Here's a few quick steps to get you started:Äownload the script from this article (it's posted on pastebin:, listed below and added as attachment). In comes a litle script, that will do exactly that. Those monitors do not yet support SNI, as they have no means of specifying the hostname you want to use for SNI. So you have your F5, with its HTTPS monitors. A typical IIS8.5 will do this, even with the 'Require SNI' checkbox unchecked. It comes down to "if you don't tell me what you want, I'll give you a default website or even simply reset the connection". You may or may not already have encountered a webserver that requires the SNI (Server Name Indication) extension in order to know which website it needs to serve you.