With Citrix Netscaler 11.0.63 you can configure a StoreFront 3.0.1 specific monitor to check the backend services. Now when you configure the monitor you will basically fail for some reasons. Here is how to do it!

 

  1. Netscaler SIP must be able to communicate (80/443) with the StoreFront server and is not common in a restricted environment (Citrix, the monitor should use the SNIP!).
  2. You must enable the StoreFront monitor service on port 80/443! I use port 80 because it's insensitive data since it basically just shows if important StoreFront Windows services are up and running.

    Open PowerShell with admin rights on the StoreFront server. You can run the following as a PowerShell script:

    # Import StoreFront API Modules
    & "$Env:PROGRAMFILES\Citrix\Receiver StoreFront\Scripts\ImportModules.ps1"
    $ServiceURL = "http://localhost:80/StorefrontMonitor"
    Remove-DSServiceMonitorFeature
    Install-DSServiceMonitorFeature -ServiceUrl 
    $ServiceURL

    This will first remove the default service on port 8000 and then create a new one on port 80. You can check the service monitor by opening the URL: http://localhost/StorefrontMonitor/GetSFServicesStatus

    3. Propagate the changes to other servers in the StoreFront Group in case you are using a load balanced deployment.

Check your Netscaler StoreFront monitor and should be up and running.


Find all the details at Citrix eDocs: 
http://docs.citrix.com/en-us/storefront/3/integrate-with-netscaler-and-netscaler-gateway/load-balancing-with-netscaler.html


Personally that's not enough for me, because even with all services running you might get a "cannot complete your request". I will use in addition a pattern monitor that checks that the login screen shows up. 


Comments  

Tyler Miranda
# 0 RE: Netscaler 11.x monitoring of StoreFront 3.x servicesTyler Miranda 2017-09-05 21:35
Thomas, did you ever get the HTTP-ECV monitor to work correctly? I've spent the last couple of days trying to figure out a solution but with so much of storefront generated javascript, the simple GET request that the Netscaler does doesn't cut it. Wondering if you found another solution for it.
Reply
Thomas Kötzing
# 0 RE: Netscaler 11.x monitoring of StoreFront 3.x servicesThomas Kötzing 2017-09-06 03:04
Are you talking about the HTTP-ECV standard monitor or a custom HTTP-ECV monitor? The default should work out of the box with SF.
Reply
Tyler Miranda
# 0 RE: Netscaler 11.x monitoring of StoreFront 3.x servicesTyler Miranda 2017-09-06 03:24
I’m talking about monitoring for the “cannot complete your request” error. The built-in SF monitors don’t catch that error. I too also investigated using a custom http-ecv monitor in addition to the SF monitors but couldn’t get it to work.
Reply
Thomas Kötzing
# 0 RE: Netscaler 11.x monitoring of StoreFront 3.x servicesThomas Kötzing 2017-09-06 04:08
>“cannot complete your request” error
Is something you should fix and not monitor. Errors for that you find also in the SF eventlog
support.citrix.com/article/CTX207162
Reply
Tyler Miranda
# 0 RE: Netscaler 11.x monitoring of StoreFront 3.x servicesTyler Miranda 2017-09-06 04:24
I agree it should be fixed but things do happen. AV updates, port exhaustion, etc. I was simply asking since you specifically mentioned it in your article.
Reply
Thomas Kötzing
# 0 RE: Netscaler 11.x monitoring of StoreFront 3.x servicesThomas Kötzing 2017-09-06 05:05
Yes, I use the SF monitor as descibed and an https-evc es well but all of that has nothing to do with “cannot complete your request”.
Reply
Casey Kirst
# 0 RE: Netscaler 11.x monitoring of StoreFront 3.x servicesCasey Kirst 2017-09-06 13:36
Thomas, the last line of your article, you mentioned "I will use in addition a pattern monitor that checks that the login screen shows up." Can you explain this more? I'd be curious to know how you set this up. Thanks
Reply
Thomas Kötzing
# -1 RE: Netscaler 11.x monitoring of StoreFront 3.x servicesThomas Kötzing 2017-09-06 14:59
How to use HTTPS-ECV health check monitor on NetScaler
support.citrix.com/article/CTX205406
Reply

Add comment