Hey all.
After a recent upgrade to 6.0.0 from 5.1, we're looking at getting HTML Blast connections functioning. We're routing our PCoIP connections through an A10 load balancer. Now I'm not the networking person that set this up but from my understanding we have a VIP setup for port 443 for both our connection servers. With A10's help, we setup a second VIP with both connection servers for port 8443. Load balanced connections to https://myfriendlyname.domain.com work half the time. The time's they don't work you can get to the landing page, login, choose pool, and then page cannot be displayed or could not resolve proxy in Chrome. If you go to server #2 directly by going to https://server_name it works fine. If you go to server #1 by going to https://server_name/ it does not work. Both in Horizon View Admin>Servers>Connection Servers>Edit>Blast External URL are https://myfriendlyname.domain.com/:8443. If you change that to the individual server, server #1 will always work. As will server #2. So I figure it's not a VMware thing, but an A10 thing. I know that an initiated connection on port 443 has to be the same server generating the connection on port 8443, otherwise it will drop. I've checked with our networking team and verified that sticky sessions are enabled. We've gone more than a few rounds with A10 and they've not encountered HTLM Blast before. I have seen a couple workarounds for F5, but nothing for A10.
Does anyone have any experience with getting this working with A10?
Thanks.
Another update. We enabled server persistence on the VIP and that solved the issue.
An update on this. We've discovered with more testing that it's sticky sessions that could be causing this to fail. We have 2 connection servers in that VIP. When the connection is made the first time to #1 it works. If the user disconnects and ends up on #2 for the 443 portion of the connection, the A10 is using sticky sessions to force the redirected connection to 8443 to #1 again. Since VMware requires the connection to be the same server on 443 and 8443, it fails. I'll post more when we hear back from A10.
Another update. We enabled server persistence on the VIP and that solved the issue.