PCoIP not working as the re-write was giving the public IP
Clients unable to access Horizon since PCoIP communication fails.
Cause
When the xyz-Horizon Integration is configured using the guide, https://xyz.com/docs/22.1/deploy-xyz-for-load-balancing-uag-servers/, the traffic path is as follows: [Please note that xyz is referring to the organization's name)
The client initiates a request to Horizon FQDN on L7 TLS port 443.
Depending on the load balancing algorithm configured, 'xyz' picks a UAG server and sends a 307 Redirect to the client.
The client sends a new request which is sent to the desired UAG server. Once the authentication is complete, the UAG responds with the IP/FQDN to be used for secondary protocols communication.
NSX Advanced Load Balancer parses this response, replace the IP/FQDN and port XML tags with NSX Advanced Load Balancer FQDN and L4 Service port.
This XML replacement is done by the content-rewrite rules associated with the VS.
The issue is caused when these rules are modified or disorganized.
They can get out of order due tomultiple updates done on the VS configuration via CLI.
Resolution
We need to ensure that the content rewrite rules are in order.
If they are not, follow the steps below to fix them.
Remove the rules from the VS.
[admin:1234]: > configure virtualservice <UAG-L7-VS-Name>
[admin:1234]: > no content_rewrite
[admin:1234]: > save