Bug ID 698000: Connections may stop passing traffic after a route update

Last Modified: May 14, 2019

Bug Tracker

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

Known Affected Versions:
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, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.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

Fixed In:
14.0.0, 13.1.0.4, 12.1.3.2, 11.6.3

Opened: Dec 07, 2017
Severity: 3-Major
Related AskF5 Article:
K04473510

Symptoms

When a pool is used with a non-translating virtual server, routing updates may lead to an incorrect lookup of the nexthop for the connection.

Impact

Connections may fail after routing updates. New connections will not be affected.

Conditions

-- Pool on a non-translating virtual server. -- Routing update occurs.

Workaround

Use a route to direct traffic to the ultimate destination rather than using a pool to indicate the nexthop.

Fix Information

Routing updates no longer interrupts traffic to connections using a pool member to reach the nexthop.

Behavior Change