Operational Defect Database
BugZero found this defect 164 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
F5 | 1403869
CONNFLOW_FLAG_DOUBLE_LB flows might route traffic to a stale next hop
Last update date:
5/15/2024
Affected products:
BIG-IP
BIG-IP TMOS
Affected releases:
14.1.0
14.1.0.1
14.1.0.2
14.1.0.3
14.1.0.5
14.1.0.6
14.1.2
14.1.2.1
14.1.2.2
14.1.2.3
14.1.2.4
14.1.2.5
Fixed releases:
No fixed releases provided.
Description:
Severity: 3-Major ... Symptoms ... Pool members configured with IP encapsulation or any type of flow using CONNFLOW_FLAG_DOUBLE_LB flag might take some time to refresh its nexthops. ... Impact ... The connection is using the old, invalid next hop for a few seconds. ... Conditions ... BIG-IP receives an ECMP route towards a server over two different BGP peers and the server is a pool member with IPIP encapsulation enabled. ... One of the BGP peers goes down and the route gets removed immediately, but BIG-IP is still forwarding traffic to this peer for the next few seconds, even though tmm.inline_route_update is enabled. ... Workaround ... None
