Bug ID 569356: BGP ECMP learned routes may use incorrect VLAN for nexthop

Last Modified: May 14, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(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.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, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4

Fixed In:
12.1.0, 11.6.1 HF1, 11.5.4 HF2

Opened: Jan 22, 2016
Severity: 3-Major
Related AskF5 Article:
K91428939

Symptoms

Border Gateway Protocol (BGP) with Equal Cost Multipath (ECMP) may result in learned routes that use an incorrect nexthop Virtual Local Area Network (VLAN). As a result of this issue, you may encounter one or more of the following symptoms: The system may randomly send the traffic using the incorrect nexthop.

Impact

The traffic randomly gets sent using the incorrect nexthop.

Conditions

-- BIG-IP configuration with two or more VLANs configured with IPv6 global addresses. -- BGP with ECMP is peered with an active IPv6 BGP neighbor. -- BGP is configured with max-paths.

Workaround

None.

Fix Information

Routes learned from the peer now have the correct nexthop VLANs.

Behavior Change