Bug ID 650164: iSession APM virtual server changes port if connection has forwarding virtual server with defined IP and wild card port

Last Modified: Feb 28, 2019

Bug Tracker

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 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.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

Opened: Mar 10, 2017
Severity: 3-Major

Symptoms

iSession does not use the correct port when connecting to a specific (not-wildcard), layered virtual server listening on all ports.

Impact

Connection is made using an unexpected port.

Conditions

-- Present forwarding virtual server after APM. -- A forwarding virtual server with a defined IP address and wildcard port.

Workaround

Use one of the following workarounds: -- Define a forwarding virtual server with a wildcard listener for IP address and wildcard port. -- Define a forwarding virtual server with a specific IP address and port.

Fix Information

None

Behavior Change