Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP APM
Known Affected Versions:
12.1.0, 12.1.1, 12.1.2, 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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4
Fixed In:
15.0.0, 14.1.2.5, 14.0.1.1, 13.1.1.5, 12.1.5
Opened: Jun 16, 2016 Severity: 3-Major
When a virtual server configured to use a SNAT pool is also associated with APM (for example, when configured as a RDP gateway), the SNAT pool setting is not honored. Also SNAT configuration of 'None' does not work. It always works as if it is configured with Automap.
The VLAN Self IP address is used instead of the SNAT pool addresses.
SNAT pool configured. -- APM configured (one example is deploying the Horizon View iApp for APM).
First, follow the configuration details in K03113285: Overview of BIG-IP APM layered virtual servers :: https://support.f5.com/csp/article/K03113285, to ensure everything is configured properly. Then ensure that the appropriate SNAT pool is set on the new layered forwarding virtual sever. Note: This workaround does not work when using a pool of VMware vCenter Server (VCS) as configured by default with the iApp.
The system now honors the virtual server SNAT configuration.