Forum Discussion

MrO_211235's avatar
MrO_211235
Icon for Nimbostratus rankNimbostratus
Nov 02, 2015

APM w/VM Horizon View

Working on a deployment with BIG IP's and working to get APM setup. I have reached a point where I can't seem to get past, and I was curious of anyone else has seen similar... I've used the iApps for VMHorizon, Horizon optimized and also tried building this manually. I am setting up APM (11.6 with HF5) to SSL offload and balance internal traffic w/o PCoIP proxy. There are no security servers involved. Using the client, I can connect directly to the connection server/pools and load the desktop perfectly. Using the LTM, I can authenticate, but receive an "HTTP 500 error." Wireshark captures indicate the BIG IP isn't initiating to the connection server when the client is showing the error message, but the virtual server health check can establish to/from the broker and gets the intended response.

 

I enabled VDI debugs and see the following errors...

 

Oct 30 19:21:27 NET-DC01-LBIN01 debug vdi[6967]: 01490000: {51.C} <- HttpHeaders[4] Oct 30 19:21:27 NET-DC01-LBIN01 debug vdi[6967]: 01490000: {51.C} ConnectionClose=0 Oct 30 19:21:27 NET-DC01-LBIN01 debug vdi[6967]: 01490000: {51.C} <- AnyRef<20ApdResponseCompleted> Oct 30 19:21:27 NET-DC01-LBIN01 debug vdi[6967]: 01490000: {51.C} -> HttpMessageStarted Oct 30 19:21:27 NET-DC01-LBIN01 debug vdi[6967]: 01490000: {51.C} -> HttpRequest[GET / HTTP/1.1] Oct 30 19:21:27 NET-DC01-LBIN01 debug vdi[6967]: 01490000: {51.C} -> HttpHeaders[9] Oct 30 19:21:27 NET-DC01-LBIN01 debug vdi[6967]: 01490000: {51.C} ConnectionClose=0 Oct 30 19:21:27 NET-DC01-LBIN01 debug vdi[6967]: 01490000: {51.C} -> HttpMessageCompleted Oct 30 19:21:27 NET-DC01-LBIN01 info vdi[6967]: 01490000: {51.C} Connecting to the backend /Common/VMware-View_.app/VMware-View__pool_0 using resource /Common/VMware-View_.app/VMware-View__remote_desktop... Oct 30 19:21:27 NET-DC01-LBIN01 notice vdi[6967]: 01490000: {51.S} Operation '' failed, error: 'unspecified' Oct 30 19:21:27 NET-DC01-LBIN01 notice vdi[6967]: 01490000: {51.S} Error reported for an outgoing connection Oct 30 19:21:27 NET-DC01-LBIN01 info vdi[6967]: 01490000: {51.S} Error reported on initiated outgoing connection. Oct 30 19:21:27 NET-DC01-LBIN01 err vdi[6967]: 01490000: {51.S.07c97633} PersistentConnectCoro error system:111 'Connection refused' Oct 30 19:21:27 NET-DC01-LBIN01 err vdi[6967]: 01490000: {51.S.07c97633} Failed to handle View request: system:111: Connection refused Oct 30 19:21:27 NET-DC01-LBIN01 debug vdi[6967]: 01490000: {51.S.07c97633} <- HttpMessageStarted Oct 30 19:21:27 NET-DC01-LBIN01 debug vdi[6967]: 01490000: {51.S} <- HttpResponse[HTTP/1.1 500 Internal Server Error] Oct 30 19:21:27 NET-DC01-LBIN01 debug vdi[6967]: 01490000: {51.S} <- HttpHeaders[1] Oct 30 19:21:27 NET-DC01-LBIN01 debug vdi[6967]: 01490000: {51.S} ConnectionClose=0 Oct 30 19:21:27 NET-DC01-LBIN01 debug vdi[6967]: 01490000: {51.S} <- HttpMessageCompleted Oct 30 19:21:27 NET-DC01-LBIN01 debug vdi[6967]: 01490000: {51.C} -> StreamClosed Oct 30 19:21:27 NET-DC01-LBIN01 debug vdi[6967]: 01490000: {51.C} Shutdown Oct 30 19:21:27 NET-DC01-LBIN01 debug vdi[6967]: 01490000: {51.C} -> ~D

 

Any ideas?

 

3 Replies

  • Lucas_Thompson_'s avatar
    Lucas_Thompson_
    Historic F5 Account

    This is the smoking gun:

     

    ct 30 19:21:27 NET-DC01-LBIN01 err vdi[6967]: 01490000: {51.S.07c97633} Failed to handle View request: system:111: Connection refused

     

    APM's VDI plugin is trying to connect to the View server but it can't and it's reporting that the connection to the View server was refused for whatever reason.

     

    To continue troubleshooting, use tcpdump and look at the source/dest IP and dest port of the connection. It's probably a firewall or something blocking it.

     

  • Greg_Crosby_319's avatar
    Greg_Crosby_319
    Historic F5 Account

    Hi MrO,

     

    Seems like you want to use APM for authentication and are using the scenario noted in the DG on page 4, "BIG-IP APM/LTM with proxied PCoIP connections using Connection Servers only".

     

    Make sure the connection servers are using the settings noted on page 6, "Modifying the View implementation if using Connection Servers only". (uncheck all proxy settings)

     

    The error in the log indicates the horizon view remote desktop profile "VMware-View__remote_desktop..." is unable to communicate to pool View__pool_0. Could be that the remote desktop profile is not setup correctly and the BIG-IP is incorrectly communicating to connection server pool.

     

    Since you are using ssl offload and appear to be using iApp to configure your BIG-IP, verify you are using the latest horizon view iApp and is using the following settings:

     

    Do you want to deploy BIG-IP Access Policy Manager?: Yes

     

    How should the BIG-IP system handle encrypted traffic? (SSL offload)

     

    The iApp created (443) virtual server will have both a client and server ssl profile (even though it is ssl offload...) and the iApp produced remote desktop profile should have "Server Side SSL" option un-checked.

     

    If all this seems accurate, I would run tcpdump on the big-ip to diagnose why big-ip communication to the connection server pool is failing.

     

  • Contacted support and realized the VM View environment was running version 6.2 - for those that may run into this...11.6 HF6 is the first version that supports VM View 6.2. Released last Friday. All seems to be operable now. Cheers!!!