Forum Discussion

fasteddye's avatar
fasteddye
Icon for Nimbostratus rankNimbostratus
Mar 01, 2013

F5 10 LTM APM with XenApp CloudGateway

We have F5 LTM 10.4.2 HF3 that is currently Load Balancing Citrix Web Interface servers. Our group that handles the Citrix environment is looking at Citrix Cloud Gateway (StoreFront) since the Secure Gateway product is EOL in 2015. We do not currently have APM so I understand that will be needed. I am unclear as to the LTM version required for this setup. Is LTM 11 required for the Cloud Gateway integration? I read that iApp became available in LTM 11 and see there are deployment guides for that. I was unable to find anything on deployment of Cloud Gateway with LTM 10 so I have a feeling it is not supported. Any other advice or items to look at for this setup would be greatly appreciated. I have done some reading on the subject but I am trying to get a better idea of what may be needed on the F5 side.

 

Thanks.

 

citrix
partner
  • fasteddye's avatar
    fasteddye
    Icon for Nimbostratus rankNimbostratus
    Mar 21, 2013

    Created http profile as recommended but with the Virtual Server using this profile, the storefront web interface does not resolve (cannot display page).

     

    As far as the xml broker health monitor, I am still unable to get that to wokr. The citrix group has gotten their side of things squared away so with the Pool not using any kind of health monitor we are presented a list of available apps when logging into storefront. Any good ways to debug or test the xml broker health monitor?

     

  • Greg_Crosby_319's avatar
    Greg_Crosby_319
    Historic F5 Account
    Mar 21, 2013
    I would start by trying out the script that is posted on Devcentral to recreate your xml monitor; a link with instructions on how to use the script are located on page 31 of our iApp deployment guide: http://www.f5.com/pdf/deployment-guides/xenapp-xendesktop-iapp-dg.pdf. The refererenced script should work fine on v10.

     

     

    Hopefully that resolves the issue, if not then the best way to see why the post is not working is to capture traffic on your server to see how the server is responding to the xml monitor post.