Forum Discussion
NimbostratusLTM and horizon view VDI connection
hello
Environment descriotion: We have a firewall (fortigate) configured with VIP which forwarding the traffic to LTM virtual server configured in performance mode and listening to all ports.
Problem description:
most of the end users we have are able to connect successfully to vdi servers with no problem and working fine. But some of them are able to authenticate succesfully with vdi server but after that when trying to connect to one of the PCs at the vdi server they get black screen. which is mostly something that had to do with the network/ports. again , not all of them , only some .
My question is : is there anything to check in ltm f5 machine ? any troubleshooting needed to be done in ltm ? since it is configured in performance mode and listening to all ports including pool members.
Have you reviewed the official deployment guide from F5 regarding VMware Horizon View? It's located here:
Deploying F5 with VMware View and Horizon View
Problems are related to the PCoIP traffic. In the deployment guide they have this problem covered:
Q: Why do I see a black screen after successfully authenticating and selecting a pool?
A: This is indicative of an issue with PCoIP traffic. Verify the BIG-IP system has a route to the user's Virtual Desktop, and UDP/TCP port 4172 are open. If you are using the BIG-IP system to natively proxy PCoIP, verify the BIG-IP system is running v11.4 or later with the most recent available hotfix and that your View environment is using version 5.2 or later. Verify your View client is one of the listed supported clients noted in the BIG-IP APM Client Compatibility Matrix manual for the version you are using, located at https://support.f5.com/kb/en-us/products/big-ip_apm.html. If you are not using the BIG-IP system to proxy PCoIP traffic, verify the client has a route to the user's Virtual Desktop.
I have seen this problem before but in that case it did not work at all. We solved it by disabling CMP on that particular VS:
K14358: Overview of Clustered Multiprocessing (11.3.0 and later)
I'm not saying you should try that first but in our case it worked.
youssef1Cumulonimbus
Hi,
philip has summed up the possible causes that can come from f5. but you tried to investigate client side?
you have several posts that speak about this subject where the problem comes from the client, here is one of the others
http://www.xtra-virtual.com/single-post/2018/02/11/Black-Screen-on-Horizon-View-Client-
if you have only a few users impacted. and that they are the same users, it would make sense to investigate customer side...
regards
PeteWhiteEmployee
"fortigate machine that is load balancing to another two vdi servers".
Are you using a SNAT pool? If so then the sessions from a client are coming from different SNAT IP addresses on the F5 side and any persistence on the Fortigate will break. Try changing to use Automap to see whether that fixes it. If it does then you need to keep the same SNAT pool member for each client, normally done by iRule.
