Bug ID 760950: Incorrect advertised next-hop in BGP for a traffic group in Active-Active deployment

Last Modified: Apr 20, 2022

Bug Tracker

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

Known Affected Versions:
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.4,, 12.1.5,,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,

Fixed In:
15.0.0,, 13.1.5,

Opened: Mar 11, 2019
Severity: 3-Major


The advertised next-hop is a floating-IP of the active traffic-group on a peer BIG-IP system, although it should be the floating-IP of the traffic-group active on the current BIG-IP system. Note: A previous bug had this same symptom, but was due to a different root cause.


An incorrect next-hop in BGP is advertised for a traffic group in Active-Active deployment. Traffic for relevant advertised routes might go to a standby device.


-- In a BIG-IP high availability (HA) configuration. -- The HA configuration is Active-Active topology. -- There are multiple traffic-groups, in which each device is active for one traffic-group.


Configure the floating address of a traffic group as the next-hop in its route-map.

Fix Information

The advertised next-hop in BGP is now the smallest floating-IP active on the current BIG-IP system.

Behavior Change