Bug ID 553776: BGP may advertise default route with bad parameters

Last Modified: Apr 28, 2025

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

Known Affected Versions:
11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 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, 11.6.3, 11.6.3.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.3.2

Opened: Oct 21, 2015

Severity: 3-Major

Related Article: K03365920

Symptoms

If a BGP neighbor is configured with 'default originate,' the nexthop advertised for the default route may be incorrect.

Impact

The default route advertised via BGP is not acceptable to peers until the BGP session is cleared.

Conditions

Dynamic routing using BGP configured, BGP neighbor configured with 'default originate'.

Workaround

In imish, run the command: clear ip bgp <affected neighbor address>.

Fix Information

BGP now always includes the correct nexthop on default route advertisements.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips