Forum Discussion
NimbostratusiApp for VMware View Config Issue?
Hi all, really new to F5 so forgive my noobness :)
F5 BIG-IP running 11.4.1 build 647. Loading balancing vmware view connections for a View 5.2 environment. Users are sporadically having an issue where they logon to their desktop, get a black screen, then immediately get disconnected. The error is a generic 'the desktop session has ended'. The only solution is to logoff the session in the View console. We did not have this issue prior to the F5 going in. There are 2 connection servers behind the F5, both look to be configured the same way. Looks like the iApp used was f5.vmware_view.v1.0.0rc7. Any particular configurations I can check?
Thanks all!
6 Replies
What version of Client is being used? The Deployment Guide for the View iApp notes an issue and fix on page 30 for 2.3 clients. There is also a newer version of the iApp noted on devcentral that might help.
JCK_171200All clients are running 5.4 client.
Thanks
I would install the latest (HF4) Hot Fix for 11.4.1. The release notes indicate a few View related fixes that might resolve the issue you described. Black screen indicates a PCoIP protocol issue, try running a TCP dump on the BIG-IP for tcp/udp 4172 from the BIG-IP to the virtual desktop to verify connection requests are making it form the BIG-IP to the virtual desktop. You should see a tcp 4172 connection directly after view client pool selection. Shortly after, you should see a stream of udp 4172 requests from BIG-IP to virtual desktop. Verify UDP port 4172 from the client to the BIG-IP is open on equipment between client and BIG-IP virtual server address.
- JCK_171200
We have HF4 installed already. This seems to be some kind of funky timeout issue. If the user desktop session is disconnected for an extended period of time, then they try to reconnect to it is when the issue seems to occur. Like th BIG-IP forgets which connection server the user was connected through. Are there any configurable timeout settings or anything like that?
Thanks all.
There is a note and workaround in the DG on the bottom of page 30 regarding persistence timeouts that seems to apply to the noted behavior.
- JCK_171200
Ok..thats something there. We have our global timeout in View basically disabled (999,9999 minutes). The BIG-IP was still defaulted to 3 minutes. I made it match the View settings and will test again. Fingers crossed!!
