Forum Discussion

Steve_M__153836's avatar
Steve_M__153836
Icon for Nimbostratus rankNimbostratus
Jul 11, 2014

Odd Behavior of Monitor for Citrix XenApp

I have deployed the monitor for Citrix XenApp against two version 6.5 servers. I followed the instructions in the deployment guide to use the script from this page to create the monitor: https://devcentral.f5.com/wiki/tmsh.BIGIP-V11-Citrix-XenApp-Monitor.ashx. Creation is successful and when I apply the monitor to the pool the members are marked up. However, in testing with my Citrix admin, we found the monitor would not mark the members down. We disabled the application on the XenApp side, but the pool members did not get marked down. Has anyone experienced this before? Is a packet capture the only method to determine what is being returned from the XenApp servers?

 

4 Replies

  • Yes it does; exactly. My point of confusion is that the application will always exist, but if it is disabled or not functioning properly will the monitor be able to tell?
  • Greg_Crosby_319's avatar
    Greg_Crosby_319
    Historic F5 Account
    The XML broker maintains application availability and, from the xml brokers health inspection, presents the application to the user if the user is entitled and the application is available. The monitor is not verifying the specific application is available, but rather verifies the xml services which enumerate publish applications is healthy. I would take a tcpdump and look at the response being sent back to the BIG-IP, somehow the application name is in the response, otherwise the monitor would go down. For example, maybe your application name for your health monitor is notepad and your Citrix application servers have notepad and notepad++ and the user you specified is entitled to both. You disable notepad on the citrix server, however, notepad++ is still being returned in the list of available applications for the user. The receive string is still a match because "notepad" is within "notepad"++.
  • In the tcpdump it looks like my Citrix admin renamed the app during our testing, but the name still includes the original name...matching your scenario exactly. I'll have my Citrix admin rename it to something completely different and verify member state after that. Thank you for the background info though; good to understand that the monitor is checking the XML service more than the app itself.