Bug ID 422665: APM requires external IP address to be specified for PCoIP client to connect to via NAT

Last Modified: Apr 19, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6

Fixed In:
15.0.0

Opened: Jun 05, 2013
Severity: 3-Major

Symptoms

APM requires that you specify an externally visible IP address for PCoIP client to connect to when it differs from virtual server IP address. (You set the IP address using the 'view.proxy_addr' session variable.)

Impact

This configuration is non-obvious and can lead to confusion.

Conditions

VMware Horizon PCoIP client connects via a NAT (i.e., APM's externally visible IP address differs from the virtual server IP address).

Workaround

Set the IP address using the 'view.proxy_addr' session variable.

Fix Information

Now, for PCoIP clients, which support name resolution, APM does not require explicit configuration of an externally visible IP address via the 'view.proxy_addr' session variable. Note: VMware Horizon clients for most platforms (Windows, Mac, Android, and iOS) except Linux, support name resolution.

Behavior Change