Bug ID 524960: 'forward' command does not work if virtual server has attached pool

Last Modified: Jul 13, 2024

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
11.5.0, 11.5.1, 11.5.1 HF1, 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.1 HF10, 11.5.1 HF11, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8

Fixed In:
12.0.0, 11.6.1, 11.5.4

Opened: May 25, 2015

Severity: 3-Major

Related Article: K17434

Symptoms

The iRule 'forward' command does not result in connections being routed to the proper destination if the virtual server has an attached pool.

Impact

Connections are routed to pool member instead of destination determined by network routes.

Conditions

Virtual server with: - Pool. - iRule that issues 'forward' commands.

Workaround

Remove pool assigned to virtual server and select the pool using an iRule with a 'pool' command when 'forward' command is not issued.

Fix Information

'forward' command releases previously selected pool member to enabled connection to be routed based on packet destination, as expected.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips