Bug ID 448630: Cannot access TCP virtual server if VDI profile is attached but Access profile is not

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
11.4.0, 11.4.1, 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.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

Fixed In:
11.6.0

Opened: Feb 11, 2014
Severity: 4-Minor

Symptoms

Cannot access TCP virtual server. RST from BIG-IP.

Impact

Cannot access TCP virtual server.

Conditions

On TCP virtual server VDI profile is specified but Access profile is not

Workaround

Configure Access profile.

Fix Information

The VDI profile now depends on access profile for TCP virtual servers. Administrators will see a configuration error if they try to attach a VDI profile without having an access profile.

Behavior Change