LTM and XenApp 5 Health Monitor

Have you checked the Deployment Guide and found the recommendations don't work?

 

 

Deploying the BIG-IP LTM v10 with Citrix Presentation Server 4.5 Creating the health monitors

 

http://www.f5.com/pdf/deployment-guides/citrix-presentation-server-ltm-v10-dg.pdf

 

 

If they don't work, I'd suggest opening a case with F5 Support as they'll want to know about the problem.

 

 

Aaron

Hello. I am having the same issue and just opened a case with F5. Trying to get a Citrix XenApp 5 environment working behind LTM v10 also. We tried using just standard tcp healthchecks and now pools show up green but we are having SSL connection issues. One thing we noticed is that Citrix may have moved the location of files noted in the section of the PDF "Configuring Citrix to retrieve the correct client IP address". I am hoping that this functionality was not removed due to the fact that Citrix competes with F5 on some platforms. Please post any info if you are successful in getting things working. Thanks. -Jim

Just an FYI. I am working on a XenApp 5.0 and TMOS Version 9.4.8 implementation. I do know for a fact that the files mentioned in the guide section labeled "Configuring Citrix to retrieve the correct client IP address" have changed. I believe I have now found the correct file and corresponding code that should be changed. I am going to test this in the morning hopefully. Once I have it implemented, then I will create a new post on that to share my findings with the community. Once I get to the point of creating monitors for it, I will post those to this thread.

 

 

I will try to post a health check for the Web front ends and the XML brokers.

Just finished the first part of the implementation. Here is a link to the tech tip:

 

 

http://devcentral.f5.com/Default.aspx?tabid=63&articleType=ArticleView&articleId=1082335

Forgot something, will repost full solution shortly.

I thought I had this one figured out, but I can't get the login to work because Citrix is looking for a variable called "SESSION_TOKEN" and for the life of me I don't know how to pass that into the monitor because changes every time.

 

 

SESSION_TOKEN=EFD0665920B78DED3EABA6296A822ABE&LoginType=Explicit&user=[your_username]&password=[your_password]&domain=[your_domin]

 

 

That should be the string to use as the receive string.. but with SESSION_TOKEN changing everytime? I am not sure how to pull this one off. A simple standard http monitor is easy enough to configure. Does anyone have any ideas?

Here is the source code from the login page. In Javascript they use the function getSessionToken to retrieve that variable :

 

 

 

Can you try a regex to look for any 32 hex character string?

 

 

SESSION_TOKEN=[A-Z0-9]{32}&LoginType=Explicit&user=your_username&password=your_password&domain=your_domain

 

 

Aaron

naladar:

 

 

Did you manage to figure out how to solve the SESSION_TOKEN problem?

 

I am having the same problem.

 

 

Thanks

Sorry for the delay, I am out of town at the moment and have limited internet access. I did try using regex to pull that session token out, but I didn't have any luck getting it to work. Unfortunately our XenApp 5.0 farm has been scrapped and we are now rolling out Citrix 6.0 in the next few weeks/month. Once I have a farm to run against I will try working with the monitor to get it going again. I will also ask around and see if F5 Networks might consider creating a implementation guide for XenApp 6.0. I think many of the techniques used for 6.0 monitors and implementation could probably be used in 5.0 - 6.0.