Bug ID 488193: iRule nexthop is not considered after failover with IP forwarding virtual server.

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0

Opened: Nov 01, 2014

Severity: 3-Major

Related Article: K17010

Symptoms

The iRule nexthop selection is not considered after failover with IP forwarding virtual server.

Impact

Client connections disconnect after failover.

Conditions

This occurs when using the FastL4 profile in a high availability configuration.

Workaround

To work around this issue, have the nexthop as a member in a pool and use the iRule pool command.

Fix Information

iRule nexthop is now considered after failover with IP forwarding virtual server, so FastL4 forwarding virtual server connections no longer fail after a failover.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips